Skip to main content
Glama
OctriDev

@octri/mcp

by OctriDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @octri/mcp

No user-submitted related servers found.

    Related Servers

    • mcp-swagger

      awssam
      A
      license
      A
      quality
      D
      maintenance
      Exposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.
      14
      2 npm
      2
      MIT

    • LockSpec

      LockSpec
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with accurate OpenAPI contract details to prevent hallucinated API calls, supporting multi-version pinning, endpoint discovery, and request validation.
      72 npm
      Apache 2.0

    • MCP-DOC-MID

      manuelperezg
      F
      license
      A
      quality
      B
      maintenance
      Enables LLMs to dereference and query OpenAPI/Swagger specifications, search endpoints and schemas, validate payloads, extract security schemes, and generate production-ready integration code in multiple languages.
      8
      -

    • Janus MCP

      DeanWard
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to understand and interact with OpenAPI specifications, providing deep insight into API structures for faster and more accurate API integration.
      9
      11 npm
      1
      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.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource: changelog, endpoint docs, guides, SDK methods, endpoint listings, SDK listings, and search. No two tools appear to overlap in purpose, so an agent can reliably select the right one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (get_, list_, search_). The verbs are clear and the nouns are specific, making the naming predictable and uniform.

    Tool Count5/5

    With 7 tools, the set is well-scoped for an API documentation server. Each tool serves a clear function without redundancy, and the count falls comfortably within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers the core documentation workflows: discovering endpoints, retrieving details, searching, accessing guides, checking changelog, and SDK info. The only notable gap is the lack of a list_guides tool, though search_docs can partially compensate.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources