
AGZ Rust MCP
io.github.agzyazilimPublished by GitHub account agzyazilimv0.5.0Updated Oct 31, 2026
Rust development tools for offline context, compiler diagnostics, focused tests and Cargo execution.
The publisher's own server: rust.wiki
Overview
A local stdio MCP server that gives an assistant Rust development tools: offline workspace inspection, compiler diagnostics, focused tests, Cargo runs and…
- What you can do
- Inspect Cargo workspaces offline: map packages, targets, features and dependencies, search source and read bounded excerpts
- Run bounded Cargo check, Clippy, tests, docs or a full gate, and analyze rebuild behavior
- Discover, compile and run selected tests by exact name, and execute a binary or example with literal arguments
- Resolve crate versions and exact-version docs, and probe API signatures or type-check snippets
- Navigate code with Rust Analyzer: symbols, definitions, references, implementations, hover, call hierarchy
- Produce write-free rename, refactor, change, repair and work packages in server-owned scratch
- When to use it
- Useful when an assistant works on a Rust project and needs grounded context, fresh compiler feedback, targeted test runs or analyzer navigation without pasting large files. It fits library, CLI, service and multi-package Cargo workspaces alike.
- Requirements
- Runs as a local process; install via cargo install agz-rust-mcp (Rust 1.88.0 or newer) or a prebuilt archive for Linux x86_64, macOS arm64 or Windows x86_64. Desktop only. No authentication or environment variables are declared; optional AGZ_RUST_MCP_* variables and a --config TOML file tune behavior. The project directory must be the working directory or passed as an absolute dir or --allow-root.
Installation
In SourceWeft
- Open AGZ Rust MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AGZ Rust MCP
[CI] [crates.io] [License: MIT]
English | Türkçe
An AGZ Yazılım product. agz-rust-mcp is a standalone MCP server with stdio and Streamable HTTP transports for
general-purpose Rust development grounded in Cargo and rustc. Discover a project
offline, collect focused source context and compiler diagnostics, select individual
tests, and run binaries/examples. Exact-version dependency docs, Rust Analyzer
navigation and write-free change/refactor packages support deeper work.
Everyday workflow
The same workflow works with a library, CLI, service or multi-package Cargo workspace. No framework-specific project structure or particular MCP client is required.
Pass an absolute dir for the active project when the client starts elsewhere.
A function is exercised through a test or executable example. run is a typed
Cargo runner; program arguments remain literal, including spaces and shell
metacharacters. Tests and applications execute project code with its ordinary
side effects. Empty selections return NO_TESTS, not a passing test verdict.
Use agz-rust-mcp --toolset core for a compact catalog of six everyday tools:
workspace, check, test, run, docs, and crate_lookup. The default
--toolset full preserves every existing tool plus the new additions. Individual
--tools-<name> false switches can disable tools further. See the
full reference for limits and result states.
Install
Prebuilt .tar.gz archives with .sha256 files are available for Linux
x86_64, macOS arm64, and Windows x86_64. Releases up to 0.2.0 use the legacy
agz-rust-coder-* asset names; from 0.3.0 onward the names are
agz-rust-mcp-*.
Step-by-step instructions, per-OS notes, checksum verification, and troubleshooting: docs/install.md · Türkçe.
MCP Client Setup
Use the installed executable with any client supporting local stdio MCP. Supply these fields in the client's own server configuration format:
For a client that uses HTTP, start the same binary as a local Streamable HTTP
server and configure http://127.0.0.1:8787/mcp as its MCP URL:
The HTTP listener is loopback-only. It supports the session lifecycle used by
2025-11-25 clients and the stateless 2026-07-28 protocol. Client-side display
prefixes, configuration file locations, and automatic prompt selection belong
to the client; the server depends on none of them. The canonical working
directory is the default authorized root; client-provided roots can only narrow
configured access. See connection details.
Built-in skills
Four offline skills ship inside the executable: agz-rust-workflow,
agz-rust-repair, agz-rust-refactor, and agz-rust-performance.
They are available immediately through all three standard MCP interfaces:
- Tools:
workspace(action="skills")lists the catalog;workspace(action="skills", skill="agz-rust-workflow")reads a skill. - Prompts:
prompts/listandprompts/getexposeworkflow,repair,refactor, andperformance. - Resources:
resources/readexposesagz-rust-mcp://skills/<skill-name>.
A client that only exposes tools can use the complete skill content. Version and
SHA-256 metadata identify the exact bundled instructions. No skill installation
or separate MCP is required. Optional agz-rust-mcp skills export --dir <new-directory>
creates files for clients that also support filesystem skills; existing files
are never overwritten. See built-in skills.
Documentation
Read the documentation in this order:
- Install and client setup - every install method and client configuration.
- Tool and configuration reference - tools, actions, result semantics, and all configuration keys.
- Architecture - process model, protocol lifecycle, and authority boundaries.
- Validation and benchmark protocol - smokes, gates, and evidence.
- Security policy and Contributing.
The bilingual index with the full reading path is docs/README.md / docs/README.tr.md.
Identity
MCP package ownership marker: mcp-name: io.github.agzyazilim/rust-mcp.
Tools
These are the exact server tool names. Use the names returned by tools/list;
a client may display its own namespace or prefix.
Every tool returns deterministic structured data plus an equivalent bounded text
fallback. External data stays under untrustedData. Expected domain outcomes
such as compiler failure, missing crates, or unavailable docs are typed results;
invalid input, authorization failure, resource exhaustion, and unavailable
semantic infrastructure are protocol errors.
Configuration
Precedence is CLI, then AGZ_RUST_MCP_* environment variables, then the
explicit --config TOML file, then defaults. Environment keys use __ between
sections, for example AGZ_RUST_MCP_GATE__HARD_TIMEOUT_MS=600000.
profile evidence is bounded: the latest 64 records stay in memory, and
persisted timing artifacts under the server-owned profile-evidence directory
are pruned after 24 hours or beyond 64 files. The profile result reports this
retention policy, so expired evidence is visible instead of silently reused.
Run agz-rust-mcp --help for every CLI field. The complete behavior and
default table is in docs/tools.md.
Security
The server does not modify workspace source, but it is not an operating-system sandbox. Cargo build scripts, tests, procedural macros, local rustdoc, and opted-in Rust Analyzer workspace code execute with the server user's authority. Use a container or OS sandbox when that boundary is required. Workspace, dependency, cache, lease, journal, docs, and telemetry paths are canonicalized, bounded, and fail closed, and stdout is reserved for MCP framing. Report vulnerabilities privately as described in SECURITY.md.
Links
- Repository: https://github.com/agzyazilim/rust-mcp
- Crate: https://crates.io/crates/agz-rust-mcp
- SDK docs: https://docs.rs/rmcp/3.8.0/rmcp/
- MCP
2025-11-25: https://modelcontextprotocol.io/specification/2025-11-25 - MCP
2026-07-28: https://modelcontextprotocol.io/specification/2026-07-28
License
MIT, Copyright (c) 2026 Ugur Murat Altintas.
Source: README.md at commit a74794b
Tools
0Version history
1- v0.5.0LatestOct 31, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Rust integrations
rust.wiki
wiki.rustOfficial publisher
Remote rust.wiki endpoint giving an assistant live Rust game data: item and skin prices, loot tables, monuments, servers and market stats.

Plane (Rust)
Published by GitHub account ninerf
Unofficial single-binary MCP server that lets an assistant read and write Plane project management data: work items, comments, cycles, modules, pages and more.

rust-panosmcp
Published by GitHub account mechubsec
MCP server for Palo Alto Networks PAN-OS firewalls: read-only inspection plus scoped, audited, two-person-approved configuration changes.

rust-proxmoxmcp
Published by GitHub account mechubsec
Proxmox VE MCP server for many clusters, with guest protection and plan/approve/apply change control for destructive operations.

rust-junosmcp
Published by GitHub account mechubsec
Juniper Junos/SRX MCP server: scoped, audited, two-person change control. Rust.