Skip to main content
Glama
bradleyfay

AutoDocs MCP Server

by bradleyfay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to AutoDocs MCP Server

No user-submitted related servers found.

    Related Servers

    • MCPyDoc

      amit608
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides real-time access to Python package documentation, source code, and symbol search to prevent AI hallucinations.
      6
      MIT

    • FreshStack MCP

      Jayesh01323
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to inspect project dependency versions, resolve version constraints, and audit Python code for deprecated or incompatible APIs using authoritative evidence and local AST analysis.
      3
      27 npm
      MIT

    • Context7 MCP

      geobio
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides LLMs with up-to-date, version-specific documentation and code examples from library sources directly into prompts, eliminating outdated code generation and hallucinated APIs.
      354,384 npm
      MIT

    • react-native-toolkit

      ItamiForge
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with accurate, version-aware documentation for React Native, Expo, React Navigation, and Ignite by automatically detecting project dependencies and fetching matching documentation.
      12
      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

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_cache_stats retrieves cache statistics, get_package_docs fetches documentation for a specific package, refresh_cache updates the cache, and scan_dependencies analyzes project dependencies. The descriptions clearly differentiate their functions, making tool selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_cache_stats, get_package_docs, refresh_cache, scan_dependencies) using snake_case throughout. This predictability aids in understanding and usage without any deviations or mixed conventions.

    Tool Count4/5

    With 4 tools, the count is reasonable for a documentation-focused server, covering key operations like fetching docs, scanning dependencies, and managing cache. It feels slightly thin but well-scoped, as each tool serves a distinct and necessary function without bloat.

    Completeness4/5

    The tool set covers core workflows for documentation retrieval and management: scanning dependencies, fetching package docs with caching, and cache operations. A minor gap exists in not having tools for updating or deleting cached docs, but agents can work around this with the provided refresh and get operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources