mcp-connector-for-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-xxx.luna.akamaiapis.net) | |
| AKAMAI_ACCESS_TOKEN | Yes | Akamai EdgeGrid access token | |
| AKAMAI_CLIENT_TOKEN | Yes | Akamai EdgeGrid client token | |
| AKAMAI_CLIENT_SECRET | Yes | Akamai EdgeGrid client secret | |
| AKAMAI_ACCOUNT_SWITCH_KEY | No | Account switch key for multi-account setups |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translate_error_stringA | Translates an Akamai error reference code (e.g. "9.6f64d440.1318965461.2f2b078") into human-readable error details including logs, HTTP status codes, and request/response metadata. This is an async operation that polls until complete. |
| curl_from_edgeA | Fetches a URL from an Akamai edge server, returning full HTTP response headers (including Akamai debug/Pragma headers) and body. Useful for debugging what the edge is serving, cache status, and response timing. |
| get_error_statisticsA | Returns HTTP error statistics (status code distribution, error percentages) for a URL or CP code. Shows edge errors and/or origin errors over the last 24-48 hours. |
| verify_locate_ipA | Verifies whether an IP address belongs to the Akamai edge network and returns its geolocation details (city, country, region, ASN, network). |
| locate_ipA | Locates up to 10 IP addresses, returning geolocation data for each (city, country, region, ASN, network). |
| dig_from_edgeA | Runs a DNS dig command from an Akamai edge server, returning DNS records for a hostname. Useful for debugging DNS resolution and propagation issues. |
| mtr_from_edgeA | Runs an MTR (My Traceroute) network diagnostic from an Akamai edge server to a destination IP or hostname. Shows network path, latency per hop, and packet loss. Useful for diagnosing connectivity issues. |
| grep_edge_logsA | Searches edge server logs by edge IP, time range, and filters (CP codes, hostnames, status codes, client IPs, user agents). This is an async operation that polls until logs are available. |
| list_edge_locationsA | Lists available Akamai edge server locations. Returns location IDs that can be used as edgeLocationId in other tools (curl, dig, MTR, etc.). |
| translate_akamaized_urlA | Translates an Akamaized URL (ARL) into its component parts: CP code, serial number, TTL, origin server, and other cache key metadata. |
| verify_edge_ipB | Verifies whether up to 10 IP addresses belong to the Akamai edge network. |
| url_health_checkA | Runs a comprehensive health check on a URL from the Akamai edge, combining cURL, dig, and optionally MTR. This is an async operation that polls until complete. |
| connectivity_problemsA | Runs Akamai connectivity diagnostics for a URL — simultaneously executes GREP (edge logs), cURL (content fetch), and MTR (traceroute). Useful for diagnosing slow downloads and high response times. This is an async operation. |
| content_problemsA | Runs Akamai content problem diagnostics for a URL — fetches content via cURL from both edge and origin to compare responses. Useful for diagnosing cache inconsistencies, stale content, and origin errors. This is an async operation. |
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 14 tools
Several diagnostic tools overlap: url_health_check, connectivity_problems, and content_problems all perform edge-side diagnostics with cURL/dig/MTR, though they target different symptoms. Additionally, verify_edge_ip and verify_locate_ip serve similar verification purposes. However, descriptions are detailed enough to differentiate most tools.
Names follow a mix of verb_noun (list_edge_locations, translate_error_string) and noun phrases (url_health_check, connectivity_problems). The verb_from_edge pattern for curl, dig, mtr is consistent for those tools, but overall the set lacks a uniform naming convention.
With 14 tools, the set is appropriately sized for an Akamai diagnostics server. Each tool addresses a specific network or content debugging need without excessive redundancy.
The server covers core diagnostic workflows: URL translation, IP verification/location, edge commands, error stats, log search, and problem detection. Missing is a location details getter and maybe a direct 'get_edge_location' but most operations are covered. Minor gaps only.