Skip to main content
Glama
rflpazini

mcp-api-gateway

by rflpazini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-api-gateway

No user-submitted related servers found.

    Related Servers

    • FastMCP Gateway

      4human-ai
      F
      license
      Not graded
      quality
      D
      maintenance
      Automatically converts OpenAPI specifications into MCP servers, allowing tools like Claude Desktop to interact with your REST APIs through a standard protocol.
      -

    • OpenAPI MCP Server

      luciVuc
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      8 npm
      MIT

    • OpenAPI MCP

      pvliesdonk
      A
      license
      Not graded
      quality
      B
      maintenance
      A generic MCP server that builds its tools at runtime from any OpenAPI specification, enabling interaction with any REST API through natural language.
      MIT

    • simple-mcp

      datj9
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns any API into a curated MCP server from a single config file, enabling interaction with APIs through MCP clients like Claude Desktop.
      6 npm
      MIT
    • Fastn Server by fastn-ai

      Fastn Serverofficial

      fastn-ai
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables dynamic tool registration and execution based on API definitions, providing seamless integration with services like Claude.ai and Cursor.ai.
      23
      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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: get_api_info retrieves metadata, check_api_health tests connectivity, and execute_api performs API calls. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_api_info, check_api_health, execute_api) using snake_case. The naming is uniform and predictable.

    Tool Count5/5

    Three tools is an appropriate scope for an API gateway server, covering information retrieval, health checking, and execution without being excessive or insufficient.

    Completeness4/5

    The tools cover the core functions of an API gateway: discovery, health, and execution. Minor gaps like authentication management or rate limiting are missing but not critical for basic use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources