Skip to main content
Glama
ryanjoachim

mcp-rtfm

by ryanjoachim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-rtfm

No user-submitted related servers found.

    Related Servers

    • AnyDocs MCP Server

      funky1688
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Transforms any website's documentation into an MCP-compatible interactive knowledge base with universal scraping, advanced search, and AI-powered tools. Supports GitBook, Notion, Confluence, and custom documentation platforms with real-time synchronization.
      2
      MIT

    • GitMCP

      anillahane
      A
      license
      Not graded
      quality
      D
      maintenance
      Transforms any GitHub repository into a documentation hub for AI assistants, enabling access to up-to-date documentation and code to eliminate hallucinations. Supports repository-specific and dynamic endpoints with smart search capabilities.
      45 npm
      Apache 2.0

    • MCPDocSearch

      MCP-Mirror
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Crawls documentation websites and provides semantic search capabilities over the content through vector embeddings, enabling natural language queries of technical documentation.
      2
      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

    B3.2/5.0

    Scored across 11 tools

    Disambiguation3/5

    The tool set has clear distinctions for most operations like reading, updating, and searching docs, but there is significant overlap between analyze_project and analyze_project_with_metadata, which could confuse agents about which to use for basic analysis. Additionally, analyze_existing_docs and analyze_project serve similar purposes with unclear boundaries, leading to potential misselection.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., analyze_existing_docs, customize_template, get_doc_content), making them predictable and readable. However, there are minor deviations like read_doc (verb_noun) vs. update_doc (verb_noun), which are still consistent in structure, and no chaotic mixing of conventions, so the naming is largely uniform.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a documentation management server, covering analysis, retrieval, updating, and metadata handling. Each tool appears to earn its place by addressing specific aspects of the domain, such as project analysis, content management, and search, without feeling overly heavy or thin.

    Completeness4/5

    The tool surface provides comprehensive coverage for documentation workflows, including analysis, reading, updating, searching, and metadata management. Minor gaps exist, such as no explicit tool for deleting documentation files or handling versioning, but agents can likely work around these with existing update and metadata tools for most tasks.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources