Skip to main content
Glama
eshaanmathakari

scoutdocs-mcp

by eshaanmathakari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to scoutdocs-mcp

No user-submitted related servers found.

    Related Servers

    • open-context

      incu6us
      A
      license
      A
      quality
      C
      maintenance
      A high-performance MCP server providing up-to-date documentation for Go, npm, Python, Rust, Docker, Kubernetes, Terraform, and more — fetched from official sources, not training data.
      18
      3
      MIT

    • web-docs-mcp

      Aleksandrr
      F
      license
      A
      quality
      B
      maintenance
      A local-first MCP server for web search and documentation fetching, providing free DuckDuckGo search, URL-to-markdown conversion, and library docs from npm, PyPI, crates.io, Go, and GitHub with caching.
      5
      -

    • mcp_for_agents

      chineidu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables building local, offline MCP servers that expose open-source package documentation to AI agents, with tools to list doc sources, search docs, and retrieve doc content over stdio.
      MIT

    • devdocs-mcp

      madhan-g-p
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.) and also via offline mode. Not via Scraping! But using the supported downloading option from devdocs.
      45 npm
      13
      MIT

    • ts-docs-mcp

      xvantz
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI coding agents accurate, version-aware API documentation for any npm package — straight from the source.
      1
      13 npm
      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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: metadata retrieval, documentation fetching, documentation search, local dependency detection, and cache statistics. No overlap or ambiguity.

    Naming Consistency4/5

    Four tools follow the verb_noun pattern (get_package_info, get_package_docs, search_package_docs, detect_project_dependencies), while cache_stats deviates slightly but still uses consistent snake_case and remains descriptive.

    Tool Count5/5

    Five tools is an ideal count for this domain, covering all necessary operations without redundancy or overwhelming options.

    Completeness5/5

    The tool set covers the full workflow for exploring package documentation: metadata lookup, content retrieval, search, and even local dependency detection. No obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources