Skip to main content
Glama
natural-docs-mcp

natural-docs-mcp

by jsharma103

Related Servers

Alternatives to natural-docs-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP tools to list and search OpenAI Agents SDK documentation, enabling LLMs to retrieve documentation topics and content via natural language queries.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides read-only MCP tools that let coding agents search and read bundled Bharosa documentation, API operation details, and SDK/cURL examples. It enables retrieving a contract, selecting grounded examples, and planning integrations without accounts, credentials, or live API calls.
      7
      42 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to fetch current, version-accurate library documentation at request time instead of relying on training memory, with search for answering questions and full-fidelity retrieval of pages or specific declarations. Supports bare or module-path library names, version pinning, and disambiguation when names collide.
      47 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search a daily-refreshed index of official documentation and read whole sections of it, so answers come from current pages with citations. Covers Claude Code, Cursor, Codex and MCP through two tools over MCP or REST.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search public documentation, retrieve SDK snippets with verification status, and access published pricing and an llms.txt resource in a read-only, credential-free way.
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing docs, searching docs, reading a specific doc, and looking up API endpoints. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names use a consistent verb_noun pattern in snake_case: list_docs, search_docs, read_doc, lookup_endpoint. No naming conventions are mixed.

    Tool Count5/5

    With 4 tools, the server is well-scoped for providing documentation and API endpoint lookup. Each tool is necessary and justified.

    Completeness4/5

    The tool surface covers listing, searching, reading docs, and querying endpoints. A minor gap is the lack of a way to list all endpoints without a search query, but the set is otherwise complete for its purpose.