Skip to main content
Glama
api7

APISIX-MCP

by api7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to APISIX-MCP

No user-submitted related servers found.

    Related Servers

    • OpenAPI MCP Server

      ivo-toby
      A
      license
      Not graded
      quality
      B
      maintenance
      A server that enables Large Language Models to discover and interact with REST APIs defined by OpenAPI specifications through the Model Context Protocol.
      4,953 npm
      297
      MIT

    • FastMCP

      Dev00355
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.
      -

    • API-Market MCP Server

      Noveum
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that exposes over 200+ APIs from API.market as MCP resources, allowing large language models to discover and interact with various APIs through natural language commands.
      34
      35 npm
      4
      MIT

    • AI API MCP Server

      physics91
      A
      license
      C
      quality
      D
      maintenance
      A FastMCP-based Model Context Protocol (MCP) server that provides unified access to multiple AI APIs including OpenAI GPT, Google Gemini, Anthropic Claude, and xAI Grok.
      5
      8 npm
      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

    C2.7/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools are clearly distinguished by their target resource (e.g., consumer, route, plugin) and action (create, update, delete), with minimal overlap. However, some tools like 'create_or_update_consumer' and 'update_consumer_group' could cause confusion about whether they handle similar entities, and 'delete_resource' is overly generic compared to specific delete tools like 'delete_secret'.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., create_route, update_service, delete_secret) with clear actions and resources. Minor deviations exist, such as 'send_request_to_gateway' using a longer phrase and 'get_all_plugin_names' including 'all', but overall the conventions are predictable and readable.

    Tool Count3/5

    With 32 tools, the count is on the high side for an API management server, bordering on heavy. While APISIX has many components (consumers, routes, plugins, etc.), this many tools might overwhelm agents or indicate fragmentation. It's reasonable but could benefit from consolidation or better scoping.

    Completeness5/5

    The tool set provides comprehensive CRUD and lifecycle coverage for APISIX's domain, including consumers, routes, services, plugins, SSL, and more. It supports create, update, delete, and get operations across all major resources, with no obvious gaps for core API gateway management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources