
Akamai CDN
io.github.desty2kPublished by GitHub account desty2kv0.2.1Updated Nov 3, 2026
Read-only MCP server for Akamai CDN — properties, EdgeWorkers, DNS, network lists
Overview
Akamai CDN's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Akamai CDN in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readonly-mcp-akamai
[CI] [codecov] [PyPI] [Python] [License: MIT]
A read-only Model Context Protocol (MCP) server that lets AI agents explore an Akamai account: CDN properties and their rule trees, EdgeWorker code, Edge DNS zones, network lists, CP codes, and error references. 16 tools, all of them reads.
Quick start
With uv installed, there is nothing else to install:
uvx downloads the package into a cached, isolated environment and runs it.
Python 3.11 or newer.
Read-only by design. Every call this server makes reads. It uses
GET, plus onePOSTto Akamai's error translator, which takes an error reference and returns what it means without changing anything. The client refuses aPOSTto any other path before sending it, and a test checks that. It cannot create, modify, delete, activate, deactivate, or purge anything. Give the API client read-only access as a second line of defense: see Credentials. Read the post about this server and why I build read-only MCP servers.
Credentials
Create an API client in Akamai Control Center under Identity & Access Management → API clients. Grant read-only access, where the API offers it, to the APIs the tools use:
The client's host, client_token, client_secret and access_token map to
the four AKAMAI_* variables below.
Tools
Properties (CDN configurations)
DNS
EdgeWorkers (serverless functions)
Network Lists
Utility
Install
Not needed for the Quick start, which runs it with uvx.
Docker
-i keeps stdin open for the default stdio transport.
Configuration
All settings are environment variables with the AKAMAI_ prefix.
The http and sse transports have no authentication: anyone who can reach
the port can read the Akamai account with the configured credentials. They
listen on 127.0.0.1 by default. Setting AKAMAI_HTTP_HOST to any other
address logs a warning at startup. The Docker image sets
AKAMAI_HTTP_HOST=0.0.0.0 so a published port works; publish it on loopback
only:
MCP client configuration
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on
macOS, %APPDATA%\Claude\ on Windows):
Claude Code
See Quick start.
How it compares
As of November 2026. Akamai's own MCP servers under akamai-developers cover other products: Akamai Cloud (Linode, also read-only), Akamai Functions, and the documentation. None of them reads Property Manager, EdgeWorkers, Edge DNS, or Network Lists. Check the projects themselves before relying on this.
Example questions
An agent with this server can answer:
- "Find the CDN property for api.example.com and show me its caching rules"
- "What version is currently deployed to production for the main website?"
- "Show me all DNS records for example.com"
- "What EdgeWorkers are configured? Show me the code for the request router"
- "Search for all uses of
setResponseHeaderin EdgeWorker 42" - "What IPs are in the blocklist network list?"
- "Translate this Akamai error: 9.6f64d440.1318965461.2f2b078"
- "List all CP codes for the main contract"
Development
License
MIT — see LICENSE.
Source: README.md at commit ed1bff1
Tools
0Version history
2- v0.2.1LatestNov 3, 2026
- v0.1.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
