Aep MCP Server

What the code does

We read the source, 1 h ago · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        # setup-node's `registry-url` writes an .npmrc containing an auth-token

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add aep -- npx -y @focusgts/aep-mcp-server

{
  "mcpServers": {
    "aep": {
      "args": [
        "-y",
        "@focusgts/aep-mcp-server"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.aep]
command = "npx"
args = ["-y", "@focusgts/aep-mcp-server"]

{
  "mcpServers": {
    "aep": {
      "args": [
        "-y",
        "@focusgts/aep-mcp-server"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "aep": {
      "args": [
        "-y",
        "@focusgts/aep-mcp-server"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: AEP_CLIENT_ID (Adobe I/O client ID from an OAuth Server-to-Server credential in the Adobe Developer Console.), AEP_CLIENT_SECRET (Adobe I/O client secret paired with AEP_CLIENT_ID.), AEP_ORG_ID (Adobe IMS organization ID, in the form xxxxxxxxx@AdobeOrg.), AEP_SANDBOX_NAME (AEP sandbox to scope every call to. Defaults to 'prod'. Use a development sandbox to enable write operations.), AEP_MODE (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.), LOG_LEVEL (Pino log level. Logs go to stderr; stdout is reserved for the MCP JSON-RPC stream.). The author declared them in the registry entry; get the values from the project itself.