readonly-mcp-akamai
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AKAMAI_HOST | Yes | Akamai API hostname (e.g., akab-xxxx.luna.akamaiapis.net) | |
| AKAMAI_HTTP_PORT | No | Port for HTTP/SSE transport | 8080 |
| AKAMAI_LOG_LEVEL | No | Log level: DEBUG, INFO, WARNING, ERROR | INFO |
| AKAMAI_TRANSPORT | No | Transport: stdio, http, or sse | stdio |
| AKAMAI_LOG_FORMAT | No | Log format: json or text | json |
| AKAMAI_ACCESS_TOKEN | Yes | EdgeGrid access token | |
| AKAMAI_CLIENT_TOKEN | Yes | EdgeGrid client token | |
| AKAMAI_CLIENT_SECRET | Yes | EdgeGrid client secret | |
| AKAMAI_INDEX_REFRESH_INTERVAL | No | Property index refresh interval in seconds | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_propertiesA | Search CDN properties by name. Returns matching properties with version numbers, staging/production versions, and group/contract IDs. Example questions:
|
| get_property_detailsA | Get property versions, hostnames, and activation status for staging and production networks. Example questions:
|
| get_property_rulesA | Get the rule tree for a property version. Returns the CDN configuration as nested rules with match criteria and behaviors: caching, origin settings, headers, redirects, and edge logic. Example questions:
|
| get_property_activationsA | Get activation history for a property. Returns which versions were deployed to staging and production, when, and by whom. Example questions:
|
| list_dns_zonesA | List DNS zones. Returns zone names, types, and activation state. Example questions:
|
| search_dns_recordsA | Get DNS records for a zone. Returns record names, types, TTLs, and values. Example questions:
|
| list_edgeworkersA | List all EdgeWorkers with names and group associations. Example questions:
|
| list_edgeworker_versionsA | List versions for an EdgeWorker. Returns version identifiers, creation dates, and checksums. Example questions:
|
| get_edgeworker_filesA | List files in an EdgeWorker version's code bundle. Returns file paths, sizes, and line counts. Example questions:
|
| get_edgeworker_fileA | Read a file from an EdgeWorker code bundle. Returns numbered source lines. Example questions:
|
| search_edgeworker_codeA | Search across all files in an EdgeWorker code bundle using a regex pattern. Returns matching file paths, line numbers, and content. Example questions:
|
| search_network_listsA | Search network lists by name. Network lists are collections of IP addresses, CIDR blocks, or country codes used for access control. Example questions:
|
| get_network_listA | Get the full contents of a network list. Returns metadata and every IP, CIDR, or country code entry. Example questions:
|
| list_groupsA | List account groups in the Akamai hierarchy. Returns group names, IDs, parent relationships, and associated contract IDs. Example questions:
|
| list_cp_codesA | List CP codes for a contract and group. CP codes are numeric identifiers used for billing, reporting, and content segmentation. Example questions:
|
| translate_error_codeA | Translate an Akamai error reference code into human-readable details. Returns HTTP response code, client/server IPs, origin info, failure reason, and WAF details. Example questions:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct resource or operation: property, CP code, DNS, EdgeWorker, network list, error code. No two tools overlap in purpose, making selection unambiguous.
All tools follow a consistent verb_noun pattern: get_ for single items, list_ for collections, search_ for filtered lookups, translate_ for a specific translation. The naming is predictable and clear.
With 16 tools covering major Akamai resources (properties, DNS, EdgeWorkers, network lists, CP codes, error codes), the count is well-scoped for a read-only server. Each tool adds distinct value.
The tool surface covers the core read-only needs for Akamai CDN management. Minor gaps exist (e.g., property variables, security settings), but the essential resources are addressed.