Cargo Doc MCP Server
Related Servers
Alternatives to Cargo Doc MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI tools with access to Rust documentation from docs.rs, enabling search for crates, documentation, type information, feature flags, version information, and source code.33-
- FlicenseNot gradedqualityDmaintenanceA Docs.rs MCP server that enables AI models to deeply access Rust crate documentation, including searching crates, viewing API definitions, feature flags, and code examples, all within the editor.3 npm2-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for fetching Rust crate documentation from docs.rs using the rustdoc JSON API.13Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that enables searching for Rust crates and their documentation from docs.rs, allowing AI agents to find required crates and access the latest documentation.427 npm37MIT
- AlicenseAqualityBmaintenanceThis server crawls documentation sites and provides search and page-retrieval tools through MCP, enabling users to query indexed documentation content.4MIT
- AlicenseAqualityCmaintenanceMCP server that fetches and searches the latest stable documentation for any package from PyPI, npm, and crates.io.5MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_crate_doc retrieves main documentation pages, list_symbols enumerates all symbols in a crate, and search_doc performs targeted searches within documentation. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on the task.
All tool names follow a consistent verb_noun pattern (get_crate_doc, list_symbols, search_doc) with clear, descriptive verbs. There are no deviations in naming conventions, making the tool set predictable and easy to understand.
With only 3 tools, the server feels somewhat thin for a documentation-focused domain, as it might lack operations like updating or managing documentation. However, the tools cover core use cases, so it's borderline but not severely mismatched.
The tools provide good coverage for basic documentation tasks: retrieving main docs, listing symbols, and searching. Minor gaps exist, such as no direct support for navigating between documentation sections or handling version-specific docs, but agents can likely work around these limitations.