Skip to main content
Glama
Sign In
kong-ai-gateway-mcp

kong-ai-gateway-mcp

by Iqram09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to kong-ai-gateway-mcp

No user-submitted related servers found.

    Related Servers

    • mnm-incident-investigator

      mnm-incident-investigatorofficial

      MNM-Technology-LLC
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables a local AI agent to investigate service incidents by querying read-only telemetry such as service health, metrics, logs, and traces, then produce verifiable assessments with evidence links and uncertainty.
      Apache 2.0

    • nats-trail

      solsolettidev
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents read-only access to production NATS and JetStream event buses through twenty-five bounded, schema-typed tools covering message search, dead-letter inspection, causal flow reconstruction from a request or correlation id, and stream, consumer, KV, object-store and server-health topology. Because the runtime is wired only to read paths and every result is limited, cursored and truncation-flagged, agents can debug live traffic without any ability to mutate it.
      Apache 2.0

    • K8gentS

      JDoornink
      F
      license
      Not graded
      quality
      D
      maintenance
      A Kubernetes diagnostic agent that provides on-demand root cause analysis and human-in-the-loop remediation via Slack, using LLM reasoning with OPA-bounded security controls.
      1
      -

    • netdiag-server

      ZANYANBU
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run eleven read-only network checks — interfaces, Wi-Fi signal, IP configuration, ping, traceroute, routing and ARP tables, DNS, port and HTTP probes — and to diagnose faults bottom-up across the network layers, returning the first broken layer with a plain-English explanation and fix.
      11
      MIT

    • Payment Orchestrator MCP

      vryahn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to interrogate payment routing decisions through six tools: route transactions, explain decisions, simulate scenarios, inspect segment evidence, normalize decline codes, and review backtest summaries. It provides read-only access to the routing engine, allowing natural-language queries without modifying any decisions.
      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

    A4.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Tools target distinct Kong entities and actions, and descriptions explicitly steer between similar options such as find_route_by_path vs get_route and diagnose_route vs explain_auth_failure. However, the composite diagnostic tools overlap with the lower-level get/list tools, so an agent could still be unsure whether to assemble evidence manually or use the high-level diagnostic.

    Naming Consistency5/5

    All 14 tools use consistent snake_case and a verb-first pattern (find_, list_, get_, check_, diff_, diagnose_, explain_). There are no mixed conventions or ambiguous suffixes.

    Tool Count5/5

    14 tools is well within the expected 3–15 range for a Kong diagnostic surface. Each tool maps to a meaningful entity or check, with no obvious bloat or thin coverage.

    Completeness4/5

    The set covers core diagnostic paths: route resolution, service/consumer/upstream lookup, plugin scoping, health checks, config diff, and high-level diagnosis. Minor gaps remain, such as no general list_routes or get_upstream, but core route/auth troubleshooting workflows are largely complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources