Skip to main content
Glama
amankrokx

mcp-connector-for-akamai

by amankrokx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-connector-for-akamai

No user-submitted related servers found.

    Related Servers

    • NetPulse

      hind77
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.
      6
      MIT

    • ALECS - MCP server for Akamai

      henrikaslund
      -
      license
      B
      quality
      Not graded
      maintenance
      MCP server for Akamai APIs. 198 tools covering Property Manager, Edge DNS, CPS, WAF, and reporting. Built with TypeScript, featuring modular architecture, comprehensive testing, and multi-account support. Make Akamai accessible to AI assistants.
      1
      9 npm
      10
      -

    • cli-bridge

      JoaoBerne
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that bridges AI assistants to other CLI tools, enabling capabilities like large-context reads, vision, file generation, and cross-vendor verification without API keys.
      6
      60 PyPI
      2
      Apache 2.0
    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.7/5.0

    Scored across 14 tools

    Disambiguation3/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources