com.focusgts/aep

⚡ Do it in three lines

claude mcp add aep \
  -e AEP_CLIENT_ID=... -e AEP_CLIENT_SECRET=... \
  -e AEP_ORG_ID=...@AdobeOrg -e AEP_SANDBOX_NAME=your-dev-sandbox \
  -- npx -y @focusgts/aep-mcp-server

Then just ask your agent:

"Create a schema with the Demographic Details field group, then a dataset on it." "Ingest this NDJSON file and tell me when the batch lands." "Build an audience of customers who bought twice this quarter and activate it." "Delete every record for this email address — dry run first."

Writes are off until you ask for them, and safe mode only unlocks sandboxes Adobe classifies as development.

The loop that makes it different

flowchart LR
  A["📐 Compose<br/>schema from field groups"] --> B["🗂️ Create<br/>dataset"]
  B --> C["📥 Ingest<br/>batch · upload · complete"]
  C --> D["🎯 Activate<br/>segment → destination"]
  D --> E["🧹 Govern<br/>erasure · expiration · quota"]
  E -. "re-audit the tenant" .-> A

Adobe's first-party gateway can tell you what's in your Experience Platform tenant. It cannot create a dataset, land a batch, activate an audience, or submit an erasure. This does — and does it behind a guard that fails closed.

🧠 How it works

flowchart LR
  A["AI agent<br/>(Claude · Cursor · Copilot)"] -- MCP / stdio --> B["aep-mcp-server<br/>51 tools"]
  B --> W{{"write guard<br/>fail-closed"}}
  W --> C["Schema Registry<br/>+ Catalog"]
  W --> D["Batch Ingestion"]
  W --> E["Profiles · Segments<br/>Destinations"]
  W --> G["Data Lifecycle<br/>+ Privacy"]
  C --> F["Your AEP sandbox"]
  D --> F
  E --> F
  G --> F

The agent calls tools; the server talks to live Adobe APIs over OAuth Server-to-Server. The write guard sits in the HTTP client, not in each tool, so all 51 inherit it and none can forget it. Blocked calls never reach Adobe.

🛡️ Safe by default

Three postures. Reads are never restricted in any mode.

**How safe decides

... View full README on GitHub