Akamai CDN MCP

An MCP server, built on Zuplo, that exposes two Akamai CDN APIs as tools for MCP clients such as Claude Desktop: Fast Purge (CCU v3) for cache purging by URL, and Property Manager (PAPI v1) for read-only viewing of property configs, rule trees, and activation status.

Unlike a passthrough-token gateway, this project holds Akamai EdgeGrid credentials server-side and computes a fresh HMAC-SHA256 signature for every request. MCP clients supply no credentials of their own — anyone who can reach this gateway's /mcp endpoint can purge cache and read property configs on the configured account, so treat the deployed URL itself as sensitive.

Tools exposed

No Property Manager write/activation endpoints are exposed by design.

Related MCP server: readonly-mcp-akamai

Project structure

Deploy your own copy

This repo is meant to be forked and deployed to your own Zuplo account — your Akamai EdgeGrid credentials live in whichever Zuplo project runs this gateway, so it should be one you control.

1. Fork this repository.

2. In the Zuplo portal, create a new project and connect it to your fork.

3. Under Settings > Environment Variables, set these as secrets, for whichever environment you're deploying (Working Copy / Preview / Production don't share values):

   • EDGERC_CLIENT_TOKEN

   • EDGERC_CLIENT_SECRET

   • EDGERC_ACCESS_TOKEN

   • EDGERC_HOST (bare hostname, no scheme)

4. Deploy the environment from the portal, and redeploy any time you change an env var — changes don't take effect until redeployed. Note the deployed URL; your MCP endpoint is https://<your-project>.zuplo.app/mcp.

Connect from Claude Desktop

Since auth is server-side, no per-client header is needed:

{
  "mcpServers": {
    "akamai-cdn": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://<your-project>.zuplo.app/mcp"]
    }
  }
}

Restart Claude Desktop after editing claude_desktop_config.json.

Local development

npm install
npm run dev

Starts the gateway at http://localhost:9000 (route designer at :9100). Requires Node.js >= 24 for the Zuplo CLI.

Before testing through /mcp, smoke-test signing directly against a CCU or PAPI route (e.g. curl -X POST localhost:9000/invalidate/url/staging -d '{"objects":["https://example.com/test"]}') with real credentials in a local .env, to isolate signing bugs from MCP-protocol issues. Then verify the full tools/call path via mcp-remote or Claude Desktop before trusting a deploy — a signing bug that passes direct-route tests can still surface only when called through the actual MCP client.

Always test network=staging and invalidate-by-url before ever exercising network=production or delete-by-url.

Extending

All routing lives in config/routes.oas.json. To expose another CCU or PAPI operation as an MCP tool:

1. Add it as a new OpenAPI path/operation with a unique operationId, an x-zuplo-route.handler of urlForwardHandler pointed at the matching baseUrl (https://${env.EDGERC_HOST}/ccu/v3 or .../papi/v1 — note the ${env.VAR} syntax, not $env(VAR), is required specifically inside baseUrl), the matching edgegrid-signing-{ccu,papi}-inbound policy, and x-zuplo-route.mcp.type: "tool".

2. Add a matching { "file": "./config/routes.oas.json", "id": "<operationId>" } entry to the /mcp route's mcpServerHandler operations array.

See Akamai's CCU v3 and PAPI v1 API references for other available operations.

Guardrails not (yet) implemented

• No confirm-before-purge policy. Tool descriptions ask the calling model to confirm destructive purges with the user, but nothing server-side enforces it. A sibling project's equivalent guardrail passed every direct/local test but broke unexplainably through Claude Desktop, so this is deferred until EdgeGrid signing itself has been verified stable end-to-end in production.

• No IP address restriction or other inbound/outbound policy on /mcp. Out of scope for now per an explicit decision; revisit if the deployed URL needs to be shared narrowly.