Skip to main content
Glama
heecheon92

SpecBridge MCP

by heecheon92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to SpecBridge MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      8 npm
      3
      MIT

    • mcp-openapi-schema

      hannesj
      A
      license
      Not graded
      quality
      F
      maintenance
      A MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context
      48 npm
      49
      MIT

    • MCP OpenAPI Server

      ReAPI-com
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that loads multiple OpenAPI specifications and exposes them to LLM-powered IDE integrations, enabling AI to understand and work with your APIs directly in development tools like Cursor.
      7
      49 npm
      90
      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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: generate_typescript_dto creates TypeScript types, get_endpoint_contract retrieves endpoint details, list_api_endpoints lists endpoints, list_backends lists backends, load_openapi_spec loads specs, and propose_new_endpoint proposes new endpoints. The descriptions make it easy to differentiate their functions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: generate_typescript_dto, get_endpoint_contract, list_api_endpoints, list_backends, load_openapi_spec, and propose_new_endpoint. This uniformity makes the tool set predictable and easy to navigate.

    Tool Count5/5

    With 6 tools, the count is well-scoped for an OpenAPI-focused server, covering core operations like loading specs, listing endpoints and backends, generating types, and proposing new endpoints. Each tool earns its place without feeling excessive or insufficient.

    Completeness4/5

    The tool set provides strong coverage for OpenAPI workflows, including loading specs, listing endpoints/backends, generating DTOs, and proposing new endpoints. A minor gap exists in lacking direct update or delete operations for endpoints or backends, but agents can work around this given the server's focus on analysis and generation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources