Back to Browse

Aep MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Full-CRUD server for AEP, Journey Optimizer and CJA. 61 tools from one OAuth credential.

About

Full-CRUD server for AEP, Journey Optimizer and CJA. 61 tools from one OAuth credential.

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-architected MCP server for Adobe Experience Platform with strong security controls. The code implements comprehensive write guards, proper credential handling via environment variables, and granular permission scoping. Minor code quality observations exist around error handling and logging, but no security vulnerabilities were identified. Permissions are appropriate for the server's purpose as a full-featured AEP integration tool. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue.

3 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

What You'll Need

Set these up before or after installing:

Adobe I/O client ID from an OAuth Server-to-Server credential in the Adobe Developer Console.Optional

Environment variable: AEP_CLIENT_ID

Adobe I/O client secret paired with AEP_CLIENT_ID.Required

Environment variable: AEP_CLIENT_SECRET

Adobe IMS organization ID, in the form xxxxxxxxx@AdobeOrg.Optional

Environment variable: AEP_ORG_ID

AEP sandbox to scope every call to. Defaults to 'prod'. Use a development sandbox to enable write operations.Optional

Environment variable: AEP_SANDBOX_NAME

Write posture: 'read-only' (no mutation anywhere), 'safe' (default — writes only in sandboxes Adobe classifies as development), or 'production' (writes anywhere). Reads are never restricted.Optional

Environment variable: AEP_MODE

Pino log level. Logs go to stderr; stdout is reserved for the MCP JSON-RPC stream.Optional

Environment variable: LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-focusgts-aep": {
      "env": {
        "AEP_MODE": "your-aep-mode-here",
        "LOG_LEVEL": "your-log-level-here",
        "AEP_ORG_ID": "your-aep-org-id-here",
        "AEP_CLIENT_ID": "your-aep-client-id-here",
        "AEP_SANDBOX_NAME": "your-aep-sandbox-name-here",
        "AEP_CLIENT_SECRET": "your-aep-client-secret-here"
      },
      "args": [
        "-y",
        "@focusgts/aep-mcp-server"
      ],
      "command": "npx"
    }
  }
}

Reviews

No reviews yet

Be the first to review this server!