Borrowing it
Nothing to install: this file belongs to zeenix/rust-analyzer-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zeenix/rust-analyzer-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/zeenix/rust-analyzer-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/zeenix/rust-analyzer-mcp/claude-md)<a href="https://agentmods.dev/instructions/zeenix/rust-analyzer-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/zeenix/rust-analyzer-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01007 | $0.01007 |
| Opus 5 | $0.00504 | $0.00504 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
rust-analyzer-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
rust-analyzer-mcp is a Model Context Protocol (MCP) server that provides integration with rust-analyzer LSP, allowing AI assistants to analyze Rust code through standardized tools. The server acts as a bridge between MCP clients and rust-analyzer, translating MCP tool calls into LSP requests.
Architecture
The codebase follows a modular architecture:
- Main MCP Server (
src/main.rs): Handles MCP protocol, manages rust-analyzer subprocess, and routes tool calls to LSP methods - Test Support Library (
test-support/): ProvidesMCPTestClientfor integration testing with proper process lifecycle management - Test Structure:
tests/integration/: Core MCP server integration teststests/stress/: Concurrency and performance stress teststests/unit/: Protocol and component unit teststests/property/: Property-based fuzzing tests
Key architectural decisions:
- Uses Tokio async runtime for concurrent request handling
- Maintains persistent rust-analyzer subprocess for performance
- Implements proper LSP initialization sequence with workspace support
- Handles CI environment detection for test reliability
Development Commands
Building and Running
# Development build and run
cargo build
cargo run -- /path/to/workspace
# Release build (optimized with LTO)
cargo build --release
# Run with debug logging
RUST_LOG=debug cargo run -- /path/to/workspace
Testing
# Run all tests
cargo test
# Run specific test
cargo test test_concurrent_tool_calls
# Run tests in release mode (for stress tests)
cargo test --release
# Run integration tests only
cargo test --test integration_tests
# Run with verbose output to debug failures
cargo test -- --nocapture
# Run tests with specific timeout debugging
RUST_BACKTRACE=1 cargo test --test integration_tests test_all_lsp_tools
Linting and Formatting
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 144 lines · 1,007 tokens per session scan A 21bc84bc8ce6
rust-analyzer-mcp CLAUDE.md is an instructions file published in the GitHub repository zeenix/rust-analyzer-mcp (79 stars, last pushed 15d ago), licensed MIT. It adds 1,007 tokens to every session, about $0.0050 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.