Skip to content
RustUse

RustUse MCP Server

The RustUse MCP Server provides structured access to the RustUse catalog, set hierarchy, crate metadata, generated documentation routes, and reusable planning prompts.

Use it when your AI client supports Model Context Protocol and you want RustUse-aware assistance without manually pasting documentation.

The server is planned as a structured alternative to choosing LLM text files by hand. Initial versions should prefer read-only resources and explicit user-controlled capabilities.

Structured access

Section titled “Structured access”

The RustUse MCP Server is intended to expose:

  • the RustUse catalog
  • set hierarchy
  • crate metadata
  • generated documentation routes
  • LLM text file routes
  • Rustdoc routes
  • reusable planning prompts

What the server provides

Section titled “What the server provides”
  • RustUse catalog resources
  • Set and crate lookup
  • LLM text file discovery
  • Rustdoc route discovery
  • Set planning prompts
  • Child-crate planning prompts
  • Collision checks for proposed crate names
  • GitHub Copilot prompt generation

What the server does not do

Section titled “What the server does not do”
  • It does not publish crates.
  • It does not create repositories by default.
  • It does not mutate files unless explicitly configured.
  • It does not replace Rustdocs, crates.io, or the docs site.

Planned resource URI patterns

Section titled “Planned resource URI patterns”
rustuse://catalog
rustuse://facades
rustuse://facades/{facade}
rustuse://facades/{facade}/children
rustuse://crates
rustuse://crates/{crate}
rustuse://llms
rustuse://llms/full
rustuse://llms/facades/{facade}
rustuse://llms/facades/{facade}/full
rustuse://llms/crates/{crate}
rustuse://llms/crates/{crate}/full
rustuse://rustdocs/workspaces/{facade}
rustuse://rustdocs/crates/{crate}

Planned tools

Section titled “Planned tools”
Tool Candidate status Expected behavior
search_facades(query) Stable/read-only Search public RustUse facades by name, tags, or description.
search_crates(query) Stable/read-only Search public RustUse crates by name, tags, or description.
get_facade(name) Stable/read-only Return metadata and route information for one facade.
get_crate(name) Stable/read-only Return metadata and route information for one crate.
list_children(facade) Stable/read-only Return child crates for a facade.
find_possible_collisions(name) Experimental Check proposed names against known RustUse and crates.io-style collision rules.
suggest_child_crates(facade, goal, min_count) Experimental Suggest focused primitive child crates for a facade goal.
generate_copilot_prompt(task, facade, children) Experimental Generate a GitHub Copilot Plan Mode prompt from RustUse conventions.
validate_facade_shape Experimental Check whether a proposed facade structure follows RustUse naming conventions.

Stable read-only candidates

Section titled “Stable read-only candidates”
  • search_facades
  • search_crates
  • get_facade
  • get_crate
  • list_children

Experimental candidates

Section titled “Experimental candidates”
  • find_possible_collisions
  • suggest_child_crates
  • generate_copilot_prompt
  • validate_facade_shape

Planned prompts

Section titled “Planned prompts”
plan-new-facade
add-child-crate
audit-facade-taxonomy
write-copilot-plan-prompt
write-readme
write-onboarding-example
split-llms-files
prepare-release-checklist

Security

Section titled “Security”

The RustUse MCP Server should be read-only by default.

Initial versions should not publish crates, write files, create repositories, run shell commands, or mutate local projects unless the user explicitly enables those capabilities.

Even when an MCP client provides structured RustUse context, generated code should still be checked against Rustdocs and local tests.