Adobe MCP Servers built and shipped by Focus GTS

Why this exists

Focus GTS doesn't just staff Adobe builds. We ship the AI infrastructure on top of them.

Most Adobe staffing firms hand you a resume and walk away. We build the tools our placements use, and we open-source them so the rest of the Adobe ecosystem benefits.

Model Context Protocol is the standard Anthropic introduced for connecting AI clients to external tools and data. When Claude, Cursor, ChatGPT Desktop, or GitHub Copilot need to actually do something — not just talk about it — an MCP server is what makes that possible. The AI gets a list of typed tools, calls the ones it needs, and gets structured results back.

Adobe ships first-party MCPs for a small number of its products, mostly read-only beta releases with narrow tool surfaces. The rest of Adobe Experience Cloud has no MCP coverage at all. That gap is what Focus GTS is filling. We started with the three layers our customers ask about most — Adobe Experience Platform, Adobe Firefly Services, and Edge Delivery Services — and we're actively building more as Adobe ships new surfaces and our customers hit new gaps.

All three servers are on npm. All three install with a single command. All three run locally as stdio processes — nothing in our infrastructure, no telemetry phoning home, no rate limits. EDS MCP and Firefly Services MCP and AEP MCP are all Apache 2.0 open source. The repos live on GitHub alongside the rest of our open-source Adobe tooling, including EDS Score, the free Edge Delivery Services audit we run for the community.

Package 2 · Adobe Experience Platform

AEP MCP Server

The first full-featured Model Context Protocol server for Adobe Experience Platform. Twenty-three tools across schemas, datasets, identities, profiles, segments, sources, destinations, and Query Service — full read and write, working pagination, and structured error codes.

claude mcp add aep \
  -e AEP_CLIENT_ID=your-client-id \
  -e AEP_CLIENT_SECRET=your-client-secret \
  -e AEP_ORG_ID=your-ims-org \
  -e AEP_SANDBOX_NAME=prod \
  -- npx @focusgts/aep-mcp-server

{
  "mcpServers": {
    "aep": {
      "command": "npx",
      "args": ["@focusgts/aep-mcp-server"],
      "env": {
        "AEP_CLIENT_ID": "your-client-id",
        "AEP_CLIENT_SECRET": "your-client-secret",
        "AEP_ORG_ID": "your-ims-org",
        "AEP_SANDBOX_NAME": "prod"
      }
    }
  }
}

{
  "servers": {
    "aep": {
      "command": "npx",
      "args": ["@focusgts/aep-mcp-server"],
      "env": {
        "AEP_CLIENT_ID": "your-client-id",
        "AEP_CLIENT_SECRET": "your-client-secret",
        "AEP_ORG_ID": "your-ims-org",
        "AEP_SANDBOX_NAME": "prod"
      }
    }
  }
}

Honest comparison

AEP MCP Server vs Adobe's own MCP releases

Adobe has shipped a small handful of read-only beta MCP servers. None of them target Adobe Experience Platform itself. Here's the apples-to-apples breakdown.

Who this is for

Built for Adobe engineering teams, not for demos

Both servers are designed for teams that already run Adobe in production and want their AI client to do more than write boilerplate.

• AEM and EDS engineers who want Claude or Cursor to publish, audit, and report on Edge Delivery Services sites without context-switching to aem.live dashboards.
• Adobe Experience Platform architects who need an AI assistant that can read schemas, inspect datasets, run SQL against the data lake, and create segments — not just describe how those operations work in theory.
• RTCDP and journey teams coordinating profile, identity, and segment work across multiple sandboxes — with sandbox auto-scoping baked into every tool call.
• Adobe Solution Partners and integrators who want a vetted MCP layer to embed in customer engagements rather than building one from scratch.
• Adobe customers exploring AI agents who need to prove out a workflow on real data without spinning up a hosted service or signing a data-processing agreement with another vendor.

Focus GTS is an Adobe Silver Solution Partner and has placed 500+ Adobe specialists at Fortune 100 companies since 2018. Our staffing relationships are why we know which Adobe workflows are worth wrapping in an MCP and which ones are not. When you hire us for Adobe + AI staffing or Navigator — our managed Adobe service — you get engineers who know these MCP servers cold because we built them.

Related Focus GTS work

The broader Adobe + AI portfolio

MCP servers are one slice of what Focus GTS ships into the Adobe ecosystem. The rest of the portfolio is here.

• EDS Score — Free Adobe Edge Delivery Services audit tool. Scans any URL against EDS-specific criteria (Core Web Vitals, plain-HTML structure, config validity, redirect health) and returns a grade plus a punch list.
• Adobe + AI staffing — Senior engineers placed at the intersection of Adobe Experience Cloud and modern AI tooling: MCP, Claude, Cursor, Firefly Services, GenStudio, Brand Concierge, Adobe LLM Optimizer.
• Adobe expertise — The full Focus GTS Adobe practice: AEM, AEM as a Cloud Service, Adobe Analytics, Customer Journey Analytics, Adobe Target, Real-Time CDP, Marketo, Workfront.
• Navigator — Adobe Experience Cloud managed service. Senior Adobe engineers at a fixed monthly rate. No SOWs, no MSA renewals, no overhead.