Aep MCP Server

Aep is an MCP integration. Full-CRUD server for AEP, Journey Optimizer and CJA. 61 tools from one OAuth credential.

Packages and local setup

The published npm package is @focusgts/aep-mcp-server, version 0.11.1. Its declared MCP transport is stdio.

The package declares AEP_CLIENT_ID (required): Adobe I/O client ID from an OAuth Server-to-Server credential in the Adobe Developer Console.; AEP_CLIENT_SECRET (required): Adobe I/O client secret paired with AEP_CLIENT_ID.; AEP_ORG_ID (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.11.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.