Cargo Doc MCP Server
Servidor MCP de documentos de carga
Un servidor MCP para gestionar la documentación de Rust mediante comandos de documento de cargo. Este servidor proporciona herramientas para consultar, compilar y buscar documentación de Rust localmente.
Características
Herramientas
get_crate_doc- Obtenga la página de documentación principal de crate para comprender los conceptos generales y el usoParámetros:
project_path: Ruta al proyecto Rust (debe ser una ruta absoluta)crate_name: Nombre del cajón para el que se obtendrá la documentación
list_symbols- Lista todos los símbolos (estructuras, enumeraciones, rasgos, etc.) en la documentación de un cajónParámetros:
project_path: Ruta al proyecto Rust (debe ser una ruta absoluta)crate_name: Nombre de la caja para la que se listarán los símbolos
search_doc- Buscar dentro de la documentación de una cajaParámetros:
project_path: Ruta al proyecto Rust (debe ser una ruta absoluta)crate_name: Nombre de la caja en la que buscarquery: Consulta de búsqueda (palabra clave o símbolo)limit(opcional): número máximo de resultados a devolver (predeterminado: 10)
Related MCP server: MCP Rust Docs Server
Requisitos
Node.js 16 o posterior
Rust and Cargo instalado
Instalación
Instalar dependencias:
pnpm installConstruir el servidor:
pnpm run buildPara desarrollo con reconstrucción automática:
pnpm run watchUso
Agregue la siguiente configuración:
{
"mcpServers": {
"docs-rs-mcp": {
"command": "/absolute/path/to/docs-rs-mcp/build/index.js"
}
}
}Depuración
Dado que los servidores MCP se comunican a través de stdio, la depuración puede ser complicada. Recomendamos usar el Inspector MCP:
pnpm run inspectorEl Inspector proporcionará una URL para acceder a las herramientas de depuración en su navegador.
Sistema de caché
El servidor mantiene una caché con las rutas de la documentación generada para mejorar el rendimiento. Las entradas de la caché caducan a las 24 horas para garantizar que la documentación se mantenga actualizada.
Licencia
Instituto Tecnológico de Massachusetts (MIT)
Available Tools
3 toolsget_crate_docA
Get crate's main documentation page. Useful for unresolved imports (e.g. use get_crate_doc when seeing 'unresolved import tokio::sync') or understanding crate features.
Inputs: project_path (required), crate_name (required).
list_symbolsB
List all symbols in a crate. Use when implementing traits or exploring available types. Shows structs, enums, traits with their paths.
Inputs: project_path (required), crate_name (required).
search_docB
Search crate docs for specific features, error messages, or usage examples. Helps debug compilation issues or learn new APIs.
Inputs: project_path (required), crate_name (required), query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Search and read Rust documentation for the standard library and any crate on crates.io
Versioned documentation registry and semantic search for AI tools and coding assistants.
Search and read official Proa Rust framework documentation. Public, read-only, no credentials.
MCP server for opencode documentation, generated by doc2mcp.
Related MCP 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-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for fetching Rust crate documentation from docs.rs using the rustdoc JSON API.13Apache 2.0
- AlicenseAqualityDmaintenanceAn 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.422 npm38MIT
- AlicenseAqualityCmaintenanceMCP server that fetches and searches the latest stable documentation for any package from PyPI, npm, and crates.io.5MIT