Skip to main content
Glama
QuantGeekDev

MCP Framework Documentation Server

by QuantGeekDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to MCP Framework Documentation Server

No user-submitted related servers found.

    Related Servers

    • openai-agents-sdk-mcp

      gavinz0228
      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

    • okfy

      0dust
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, read, and traverse documentation bundles in Open Knowledge Format via MCP tools.
      318 npm
      74
      MIT

    • devdocs-mcp

      maxwhipw
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to search, install, read, and navigate DevDocs documentation offline via MCP, with token-efficient search/read/toc tools and local caching.
      6
      6 npm
      -

    • jam-nodes-docs-mcp

      KNQuoc
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to search and retrieve jam-nodes documentation, including node info, API references, and guides, via MCP tools without loading everything into context.
      5
      1
      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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_page retrieves specific page content, list_sections provides structural overview, and search_docs enables keyword-based discovery. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (get_page, list_sections, search_docs) with clear, descriptive names. The naming convention is uniform and predictable throughout the set.

    Tool Count3/5

    With only 3 tools, the server feels minimal for a documentation server scope. While the core operations are covered, the count is borderline thin, potentially limiting advanced interactions like filtering or metadata operations.

    Completeness4/5

    The tools provide essential CRUD-like coverage for documentation access: discovery (list_sections), retrieval (get_page), and search (search_docs). A minor gap exists in update or management capabilities, but the surface supports core user workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources