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
      C
      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.
      10 npm
      1
      Apache 2.0

    • openapi-mcp

      ceski23
      A
      license
      Not graded
      quality
      C
      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.
      17 npm
      3
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 164 tools

    Disambiguation3/5

    The descriptions do an unusually good job cross-referencing sibling tools (e.g., list_schemas vs list_shared_schemas, get_header_policies vs get_resolved_headers), which helps separate many overlapping reads. However, with 164 tools there are many near-neighbors across org/project/spec levels and list/get variants, so misselection remains likely.

    Naming Consistency4/5

    Most names follow a predictable snake_case verb_noun pattern (list_*, get_*, update_*, export_*, validate_*). A few tools use action-style manage_* references or non-verb-first names like pre_publish_impact, test_smart_mock, and preview_smart_mock, but the set is still broadly readable and consistent.

    Tool Count1/5

    164 tools is far beyond a reasonable scope for a single MCP server, even for a broad API lifecycle platform. The toolset mechanism may hide some tools, but the advertised surface alone is extremely heavy and hard for an agent to navigate.

    Completeness2/5

    The surface is rich in read/list/get operations, but core create/update/delete operations for specs, endpoints, schemas, tests, mocks, and docs are largely absent. Many descriptions point to manage_* tools that do not appear in the provided tool list, leaving significant dead ends for write workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources