Skip to main content
Glama
akamai-developers

Akamai Cloud MCP Server

Official
by akamai-developers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Akamai Cloud MCP Server

No user-submitted related servers found.

    Related Servers

    • kc-mcp-server

      Kvindo
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for Kvindo Cloud that lets AI clients list, inspect, create, update, and delete cloud resources (VMs, volumes, Kubernetes, etc.) via natural language. Read-only by default, with write/delete operations gated by explicit opt-in environment variables.
      7 npm
      1
      MIT

    • Linode MCP Server

      komer3
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables Large Language Models like Claude to manage Linode cloud resources, including listing regions, creating, viewing, deleting, and rebooting Linode instances.
      1
      1
      MIT

    • aws-readonly-mcp

      ziyuyu23
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that lets an LLM inspect an AWS account — list EC2 instances, S3 buckets, IAM users, and cost — with a structural guarantee against any mutations.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 37 tools

    Disambiguation5/5

    Each tool targets a specific Linode resource and action (get vs list), with clear naming. Even similar tools like 'list_instances' and 'get_instance' are distinct by scope (all vs single). No overlapping purposes.

    Naming Consistency5/5

    All tools follow the consistent pattern 'linode_<verb>_<noun>' in snake_case. Verbs are limited to 'get', 'list', 'find', and 'estimate', making it predictable and easy to navigate.

    Tool Count4/5

    37 tools is high but appropriate for covering the broad Linode API surface (compute, storage, network, databases, DNS, etc.). A few utilities like 'list_database_types' and 'list_database_engines' could be merged, but overall the count is justified.

    Completeness4/5

    For a read-only toolset, coverage is comprehensive across major Linode resources (instances, volumes, firewalls, LKE, DNS, Object Storage). Minor gaps exist (e.g., SSH keys, StackScripts), but core infrastructure is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources