RustUse MCP Server is the AI-facing Model Context Protocol server for RustUse. It exposes RustUse catalog data, rules, adoption paths, docs, reusable prompt templates, and bounded planning tools to...
概览
RustUse MCP Server is the AI-facing Model Context Protocol server for RustUse. It exposes RustUse catalog data, rules, adoption paths, docs, reusable prompt templates, and bounded planning tools to MCP-compatible clients. This repository lives beside docs, use-math, use-geometry, use-cli, use-web, and the other RustUse repositories. It is not a use-* facade crate and should not be named use-mcp. Version 0.1 is deliberately small and read-only. It uses stdio transport through the official Rust rmcp SDK. It does not write files, run commands, publish crates, call GitHub write APIs, or mutate sibling RustUse repositories. RustUse has many small primitive Rust crates, facade sets, documentation surfaces, and adoption paths. AI clients need a stable way to ask about that structure without guessing from the filesystem or making broad changes.
README
以下为原文 README 节选,完整内容请查看原文。
RustUse MCP Server
RustUse MCP Server is the AI-facing Model Context Protocol server for RustUse. It exposes RustUse catalog data, rules, adoption paths, docs, reusable prompt templates, and bounded planning tools to MCP-compatible clients.
This repository lives beside docs, use-math, use-geometry, use-cli, use-web, and the other RustUse repositories. It is not a use-* facade crate and should not be named use-mcp.
Version 0.1 is deliberately small and read-only. It uses stdio transport through the official Rust rmcp SDK. It does not write files, run commands, publish crates, call GitHub write APIs, or mutate sibling RustUse repositories.
Why It Exists
RustUse has many small primitive Rust crates, facade sets, documentation surfaces, and adoption paths. AI clients need a stable way to ask about that structure without guessing from the filesystem or making broad changes. This MCP server gives those clients a bounded, protocol-compliant interface for catalog lookup, rule validation, overlap checks, and prompt generation.
Local Development
Build the server:
cargo build --release -p rustuse-mcp-server
Run it over stdio:
cargo run -p rustuse-mcp-server
Validate the workspace:
cargo fmt
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
Client Configuration
Use stdio transport and point your MCP client at the release binary:
/path/to/RustUse/git_local/mcp/target/release/rustuse-mcp-server
Example client configs live in examples/.
Resources
rustuse://catalogrustuse://rulesrustuse://adoption-pathsrustuse://setsrustuse://sets/use-mathrustuse://sets/use-geometryrustuse://sets/use-clirustuse://sets/use-webrustuse://sets/use-datarustuse://promptsrustuse://docs/overviewrustuse://docs/security
Resource templates are available for sets, crates, and docs where the SDK supports them.
Tools
rustuse_catalog_searchrustuse_get_setrustuse_get_craterustuse_list_childrenrustuse_check_name_collisionrustuse_find_overlaprustuse_validate_set_planrustuse_generate_copilot_prompt
Tools return readable text and structured JSON where practical. Domain validation failures are returned as tool execution errors, not process crashes.
Prompts
rustuse_brainstorm_setrustuse_create_set_v0_1rustuse_create_child_craterustuse_validate_facaderustuse_audit_overlaprustuse_generate_copilot_planrustuse_generate_docs_page
Prompt templates live in prompts/*.md and can be read directly outside MCP.
Security Posture
Version 0.1 is read-only. It does not implement Streamable HTTP, file writes, shell execution, GitHub writes, crates.io publishing, git commits, repository creation, or sibling repository mutation.
Stdout is reserved for valid MCP protocol messages. Diagnostics must go to stderr.
Roadmap
安装
This server does not publish a one-line install command.
Open the repository installation guide 新手?先看 mcpskill.org 教程 →