Akamai Cloud MCP Server
Akamai publishes one official Model Context Protocol server, akamai-cloud-mcp, covering Akamai Cloud (Linode). It is read-only by construction - a GET-only HTTP client, an allowlist serializer and a recursive secret scrub, enforced by a static scan and a runtime verb guard - and exposes 37 curated tools across ten loadable domains plus one read-only escape hatch. There is no vendor-hosted endpoint: the server is distributed on PyPI and run by the consumer over stdio, or self-hosted behind the auth-gated streamable-http transport. No MCP server is published for the EdgeGrid control-plane APIs (Property Manager, purge, security, identity); those remain REST only.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
Tools
linode_list_regions— Regions with capabilities, country, site type, and status.linode_get_region_availability— Which plans are in stock, account-wide or scoped to one region.linode_list_instance_types— Plan types with vcpus, memory, disk, transfer, GPUs, class, and prices.linode_get_pricing— Per-type pricing for a family with the correct region override applied.linode_find_gpu_availability— GPU and accelerated plans with price and the regions where each is in stock.linode_estimate_cost— Itemized hourly and monthly cost of a described stack, each line labeled by source.linode_list_instances— Compute instances with region, type, status, IPs, image, and specs.linode_get_instance— One instance by id.linode_list_volumes— Block-storage volumes with size, region, status, and attachment.linode_list_lke_clusters— LKE clusters with region, Kubernetes version, tier, and control-plane settings.linode_get_lke_cluster— One cluster with node pools, API endpoints, and control-plane ACL.linode_list_kubernetes_versions— Kubernetes versions available for new and upgraded clusters.linode_list_object_storage_buckets— Buckets with hostname, endpoint type, size, and object count.linode_get_object_storage_bucket— One bucket's detail (hostname, S3 endpoint, size, object count).linode_list_object_storage_endpoints— Endpoints (region, type, S3 hostname) available to the account.linode_get_object_storage_transfer— Object Storage network transfer for the current billing period.linode_list_object_storage_quotas— Object Storage quotas.linode_list_firewalls— Cloud Firewalls with status and tags.linode_get_firewall— One firewall with its inbound/outbound rules and attached resources.linode_list_ips— IP addresses with type, region, reverse DNS, and assignment.linode_list_vlans— VLANs with region, CIDR, and attached instances.linode_list_vpcs— VPCs with region and description.linode_get_vpc— One VPC with its subnets and the instances in each.linode_list_nodebalancers— NodeBalancers with region, hostname, IPs, and transfer usage.linode_get_account— Company, country, balance, capabilities. Payment and personal fields redacted.linode_get_account_transfer— Network transfer for the current billing period, including per-region.linode_list_invoices— Invoices with date, subtotal, tax, and total. Payment detail redacted.linode_list_events— Recent account events (the audit log).linode_get_account_limits— Composed account-limits summary (rate limits, Object Storage quotas, transfer pool).linode_list_domains— DNS domains (zones) with type, status, and SOA email.linode_get_domain— One zone with SOA timers, master/AXFR IPs, and tags.linode_list_domain_records— A/AAAA/NS/MX/CNAME/TXT/SRV/PTR/CAA records with name, target, and TTL.linode_list_databases— Managed Database clusters (all engines) with engine, version, region, status, plan, and host.linode_get_database— One database by engine and id, with host, port, and maintenance window.linode_list_database_engines— Available database engines and versions.linode_list_database_types— Managed Database plan types with vcpus, memory, disk, engines, and price.linode_api_get— Read-only GET against any Linode API v4 path a curated tool does not cover.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.