Skip to main content
Glama
ProsodyAI

@prosodyai/mcp-docs

Official
by ProsodyAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @prosodyai/mcp-docs

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

    • max-docs

      Launchery
      A
      license
      A
      quality
      C
      maintenance
      Provides comprehensive documentation for MAX Platform, including Bot API endpoints, guides, Bridge API, and UI components, via MCP tools and resources for AI coding agents.
      8
      MIT

    • okfy

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

    • docrag

      ryan-m-bishop
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides RAG (Retrieval Augmented Generation) access to technical documentation through MCP, enabling LLMs to search and retrieve relevant documentation on-demand.
      4
      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

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getting specific endpoint details, full spec, overview, listing various resources, searching, and reading. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., get_endpoint, list_docs, search_docs) with underscores, making them predictable and easy to use.

    Tool Count5/5

    8 tools are appropriate for a documentation server: they cover browsing (list), searching, and reading, with specialized tools for API details and overview. No redundancy or inadequacy.

    Completeness5/5

    The tool surface is complete for the domain: it allows listing all resources, searching, and retrieving full content, plus targeted access to API spec and overview. No dead ends for typical documentation workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources