Skip to main content
Glama
routebase-dev

Routebase

Official
by routebase-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Routebase

No user-submitted related servers found.

    Related Servers

    • swag2mcp

      mmadfox
      A
      license
      A
      quality
      A
      maintenance
      Turn any OpenAPI/Swagger/Postman spec into an MCP server — give your LLM live access to any API.
      19
      Apache 2.0

    • OpenAPI to MCP

      procoders
      A
      license
      Not graded
      quality
      D
      maintenance
      Automatically converts any OpenAPI specification or Postman Collection into an MCP server, enabling AI assistants like Claude to directly interact with REST APIs without writing any code.
      Apache 2.0

    • EasyPeasyMCP

      derberg
      A
      license
      Not graded
      quality
      B
      maintenance
      A lightweight, zero-config MCP server that makes documentation and API specifications instantly accessible to AI models using the llms.txt standard. It enables searching and retrieving full documentation, OpenAPI, and AsyncAPI specs without requiring a complex RAG infrastructure or vector database.
      2 npm
      1
      Apache 2.0

    • openapi-mcp

      ceski23
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.
      7 npm
      3
      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.6/5.0

    Scored across 162 tools

    Disambiguation3/5

    Descriptions carefully cross-reference and differentiate tools by scope and object, but with 162 tools there is substantial overlap (e.g., multiple drift, monitoring, and documentation reads) making misselection likely.

    Naming Consistency4/5

    Names predominantly follow a snake_case verb_noun convention (list_, get_, manage_, etc.), with only minor deviations like get_scheduled_publishes for a list operation.

    Tool Count1/5

    162 tools is an extreme mismatch for any server; even with toolsets, the surface is overwhelmingly large and violates the typical 3-15 tool scope.

    Completeness2/5

    Core API design CRUD is missing: no manage/create/update tools for specs, endpoints, or schemas are listed, despite references to create_endpoint and update_schema. Significant gaps will cause agent failures for mutation workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources