Akamai Cloud MCP Server
Akamai Cloud account visibility, cost estimation, and inventory management.
Data last scanned today · Reviewed today
Overview
This server provides a read-only interface for Akamai Cloud (formerly Linode) environments through the Model Context Protocol. It consolidates multiple API domains into a single server, allowing users to query compute instances, storage volumes, LKE clusters, and network configurations. It is designed to surface infrastructure details and account-level information directly to AI assistants. Beyond inventory, the tool includes functionality for pricing lookups and cost estimation. It provides regional GPU availability, itemized monthly stack estimates, and account limit reporting. All sensitive payment and PII fields are redacted by design, ensuring that queried data remains restricted to operational infrastructure details.
Our verdict
This server holds a high-risk security score of 30/100. The score reflects that the project is community-maintained rather than vendor-backed and currently has only one contributor. While the implementation claims to enforce read-only status through runtime HTTP-verb guards, users should exercise caution with API tokens until the authentication method undergoes more rigorous, external security vetting. It is best suited for those evaluating Akamai Cloud infrastructure in low-stakes development environments.
- Zero direct dependencies minimize supply-chain surface area
- Explicit read-only architecture enforced via runtime HTTP-verb guards
- Detailed README provides clear operational documentation
- Redacts PII and payment data automatically
- High security risk due to single-maintainer bus factor
- Community-maintained rather than supported by Akamai
- Lacks an official security audit or external verification
- No homepage link provided for project tracking
Tools
| Tool | Description | Risk |
|---|---|---|
| linode_list_regions | Regions with capabilities, country, site type, and status. | low |
| linode_get_region_availability | Which plans are in stock, account-wide or scoped to one region. | low |
| linode_list_instance_types | Plan types with vcpus, memory, disk, transfer, GPUs, class, and prices. | low |
| linode_get_pricing | Per-type pricing for a family (compute, block_storage, nodebalancers, network_transfer, lke, object_storage) with the correct region override applied. | low |
| linode_find_gpu_availability | GPU and accelerated plans with price and the regions where each is in stock. | low |
| linode_estimate_cost | Itemized hourly and monthly cost of a described stack, each line labeled by source. | low |
| linode_list_instances | Compute instances with region, type, status, IPs, image, and specs. | low |
| linode_get_instance | One instance by id. | low |
| linode_list_volumes | Block-storage volumes with size, region, status, and attachment. | low |
| linode_list_lke_clusters | LKE clusters with region, Kubernetes version, tier, and control-plane settings. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›Do I need an API token to use all server features?
Pricing and catalog tools work without an API token, but account-scoped tools require a Linode personal access token with read-only scopes.
›How does the server ensure read-only access to my account?
The server is enforced as read-only through a runtime HTTP-verb guard and static scans, and it includes recursive secret scrubbing to prevent data leakage.
›Can I limit the number of tools loaded to improve performance or model focus?
Yes, you can use the --domains flag in your client configuration to load only specific modules like compute, pricing, or networking.
›What happens if I try to list a large volume of resources?
The server defaults to a limit of 50 results per tool call to prevent flooding the model context, though you can adjust this limit using the --max-results argument.
›Is the server compatible with both local and hosted environments?
Yes, it supports dual transport modes: stdio for local clients and auth-gated streamable-http for hosted deployments.
Alternatives
Badge
Maintain this server? Add the live badge to your README.