Skip to main content
Glama
Sign In
openapi-lookup-mcp

openapi-lookup-mcp

by fredarcito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to openapi-lookup-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      42 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
      -

    • code-context

      jieyefriic
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to automatically scan, store, and query API endpoints from codebases, providing instant lookup and semantic search to reduce context switching and token consumption.
      1
      MIT

    • @octri/mcp

      OctriDev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.
      7
      415 npm
      3
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search finds endpoints, get_endpoint retrieves one endpoint's details, and get_schema retrieves one schema. There is no meaningful overlap between searching, endpoint inspection, and schema inspection.

    Naming Consistency5/5

    All three names follow a consistent verb_noun pattern: search_endpoints, get_endpoint, get_schema. The singular/plural distinction is natural and predictable for the resources involved.

    Tool Count5/5

    Three tools is well-scoped for a focused OpenAPI lookup server. Each tool covers a distinct lookup operation and none feels redundant or extraneous.

    Completeness4/5

    The surface covers the core lookup workflow: discover endpoints via search, inspect endpoint details, and inspect schemas. Minor gaps exist, such as no explicit list-all-endpoints or list-all-schemas operation, but search and schema lookups allow agents to work around this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources