Cargo MCP Eb2c96d6

MCP开发工具

提供方 SignalWhisperer

开发工具 未标注 无需鉴权 社区 / 第三方

一个基于MCP协议的Rust项目管理服务器,提供全面的cargo命令行工具集成,用于构建、测试、依赖管理和项目维护。

一句话选型结论

按资料字段整理

Cargo MCP Eb2c96d6 属于开发工具类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

Rust开发Rust本地部署项目管理构建工具依赖管理代码分析

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Cargo MCP Eb2c96d6当前 未标注 未标注 未标注 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方SignalWhisperer上游标注的维护方 SignalWhisperer
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

12.0 KB
来自项目仓库与上游目录的原文,未做删改

Cargo MCP Server

A Model Context Protocol (MCP) server that provides tools for managing Rust projects using the cargo command-line tool.

Disclaimer

This entire repository was built with generative AI assistance, guided by human oversight throughout the development process. The code, documentation, and architecture were collaboratively developed between human direction and AI implementation.

Architecture

The server is organized into several modules for maintainability:```
src/
├── main.rs # Entry point
├── lib.rs # Library exports
├── server.rs # MCP server implementation
├── tools/
│ ├── mod.rs # Tool module exports
│ ├── definitions.rs # Main tool registry
│ ├── schemas.rs # Common schema utilities
│ ├── build_tools.rs # Build-related tools (check, build, clippy, fmt)
│ ├── execution_tools.rs # Execution tools (run, test, bench)
│ ├── dependency_tools.rs # Dependency management (add, remove, update, tree)
│ ├── project_tools.rs # Project management (new, init, clean, doc)
│ ├── registry_tools.rs # Registry operations (search, info, install, uninstall)
│ ├── utility_tools.rs # Utility tools (metadata, version)
│ └── executor.rs # Command execution logic
├── types.rs # Data structures and types
└── error.rs # Error handling


## Features

This MCP server provides comprehensive cargo tools organized by category:

### Build Tools
- **check** - Analyze code without producing executables
- **build** - Compile the current package
- **clippy** - Run Clippy lints on the current package
- **fmt** - Format Rust code using rustfmt

### Execution Tools
- **run** - Run a binary or example of the local package
- **test** - Run unit and integration tests
- **bench** - Run benchmarks

### Dependency Management
- **add** - Add dependencies to a Cargo.toml manifest file
- **remove** - Remove dependencies from a Cargo.toml manifest file
- **update** - Update dependencies as recorded in the local lock file
- **tree** - Display a tree visualization of a dependency graph

### Project Management
- **new** - Create a new cargo package at
- **init** - Create a new cargo package in an existing directory
- **clean** - Remove artifacts that cargo has generated in the past
- **doc** - Build this package's and its dependencies' documentation

### Registry Operations
- **search** - Search packages in crates.io
- **info** - Display information about a package in the registry
- **install** - Install a Rust binary
- **uninstall** - Remove a Rust binary

### Utility Tools
- **metadata** - Output the resolved dependencies of a package in machine-readable format
- **version** - Show version information for cargo and rust

## Installation

1. Clone this repository
2. Build the project:```bash
   cargo build --release
   ```
3. Configure your MCP client to use the server. Example configuration:```json
   {
     "mcpServers": {
       "cargo-mcp": {
         "command": "/path/to/cargo-mcp/target/release/cargo-mcp",
         "args": []
       }
     }
   }
   ```

## Usage

The server communicates via JSON-RPC over stdin/stdout. It's designed to be used with MCP-compatible clients.

### Example Tool Calls

#### Check a project```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check",
    "arguments": {
      "working_directory": "/path/to/project",
      "all_targets": true
    }
  }
}

Build in release mode```json

{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "build",
"arguments": {
"working_directory": "/path/to/project",
"release": true
}
}
}


#### Run a specific binary```json
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "run",
    "arguments": {
      "working_directory": "/path/to/project",
      "bin": "my-binary"
    }
  }
}

Format code```json

{
"jsonrpc": "2.0",
"id": 4,
"method": "tools/call",
"params": {
"name": "fmt",
"arguments": {
"working_directory": "/path/to/project"
}
}
}


#### Run Clippy with fixes```json
{
  "jsonrpc": "2.0",
  "id": 5,
  "method": "tools/call",
  "params": {
    "name": "clippy",
    "arguments": {
      "working_directory": "/path/to/project",
      "fix": true,
      "allow_dirty": true
    }
  }
}

Add a dependency```json

{
"jsonrpc": "2.0",
"id": 6,
"method": "tools/call",
"params": {
"name": "add",
"arguments": {
"working_directory": "/path/to/project",
"dependency": "serde",
"features": ["derive"]
}
}
}


#### Search for packages```json
{
  "jsonrpc": "2.0",
  "id": 7,
  "method": "tools/call",
  "params": {
    "name": "search",
    "arguments": {
      "working_directory": "/path/to/project",
      "query": "tokio",
      "limit": 5
    }
  }
}

Run tests```json

{
"jsonrpc": "2.0",
"id": 8,
"method": "tools/call",
"params": {
"name": "test",
"arguments": {
"working_directory": "/path/to/project",
"release": true
}
}
}
```

Tool Parameters

Common Parameters

Most tools support these common parameters:

  • working_directory (string, optional) - Working directory to run cargo in
  • package (string, optional) - Package to operate on
  • features (array of strings, optional) - Features to activate
  • all_features (boolean, optional) - Activate all available features
  • no_default_features (boolean, optional) - Do not activate default features
  • release (boolean, optional) - Use release profile
  • target (string, optional) - Target triple

Target Selection Parameters

For check, build, clippy, test, and bench:

  • lib (boolean, optional) - Only this package's library
  • bin (string, optional) - Only the specified binary
  • bins (boolean, optional) - All binaries
  • example (string, optional) - Only the specified example
  • examples (boolean, optional) - All examples
  • test (string, optional) - Only the specified test target
  • tests (boolean, optional) - All tests
  • bench (string, optional) - Only the specified bench target
  • benches (boolean, optional) - All benches
  • all_targets (boolean, optional) - All targets

Build-specific Parameters

For check and build:
- profile (string, optional) - Build artifacts with the specified profile
- message_format (string, optional) - Error format (human, short, json, etc.)
- workspace (boolean, optional) - Build all packages in the workspace
- exclude (array of strings, optional) - Exclude packages from the operation

Clippy-specific Parameters

  • fix (boolean, optional) - Automatically apply lint suggestions
  • allow_dirty (boolean, optional) - Fix code even if working directory has changes
  • allow_staged (boolean, optional) - Fix code even if working directory has staged changes

Test-specific Parameters

  • exact (boolean, optional) - Exactly match filters rather than by substring
  • ignored (boolean, optional) - Run ignored tests
  • include_ignored (boolean, optional) - Run both ignored and not ignored tests
  • jobs (integer, optional) - Number of parallel jobs
  • nocapture (boolean, optional) - Don't capture stdout/stderr
  • test_threads (integer, optional) - Number of threads for running tests

Dependency Management Parameters

add Parameters

  • dependency (string, required) - Dependency to add
  • dev (boolean, optional) - Add as development dependency
  • build (boolean, optional) - Add as build dependency
  • optional (boolean, optional) - Mark the dependency as optional
  • rename (string, optional) - Rename the dependency
  • path (string, optional) - Filesystem path to local crate
  • git (string, optional) - Git repository location
  • branch (string, optional) - Git branch
  • tag (string, optional) - Git tag
  • rev (string, optional) - Git reference
  • default_features (boolean, optional) - Re-enable default features
  • registry (string, optional) - Registry to use

remove Parameters

  • dependency (string, required) - Dependency to remove
  • dev (boolean, optional) - Remove as development dependency
  • build (boolean, optional) - Remove as build dependency

update Parameters

  • aggressive (boolean, optional) - Force updating all dependencies
  • dry_run (boolean, optional) - Don't actually write the lockfile
  • precise (string, optional) - Update to exactly this version
  • workspace (boolean, optional) - Update all packages in workspace

tree Parameters

  • duplicates (boolean, optional) - Show only dependencies with multiple versions
  • edges (string, optional) - Kinds of dependencies to display
  • format (string, optional) - Format string for printing dependencies
  • invert (array of strings, optional) - Invert dependency graph
  • no_dedupe (boolean, optional) - Repeat shared dependencies
  • prefix (string, optional) - How to display the tree
  • prune (array of strings, optional) - Prune packages from display
  • depth (integer, optional) - Maximum display depth
  • charset (string, optional) - Character set (utf8, ascii)

Project Management Parameters

new/init Parameters

  • path (string, required for new) - Path for the new package
  • name (string, optional) - Package name
  • bin_template (boolean, optional) - Use binary template
  • lib_template (boolean, optional) - Use library template
  • edition (string, optional) - Edition to set
  • registry (string, optional) - Registry to use

doc Parameters

  • open (boolean, optional) - Open docs in browser
  • no_deps (boolean, optional) - Don't build documentation for dependencies
  • document_private_items (boolean, optional) - Document private items
  • jobs (integer, optional) - Number of parallel jobs

Registry Parameters

search Parameters

  • query (string, required) - Search query
  • limit (integer, optional) - Limit results (default: 10, max: 100)
  • registry (string, optional) - Registry to use

info Parameters

  • query (string, required) - Package name
  • registry (string, optional) - Registry to use

install Parameters

  • query (string, optional) - Package name to install
  • version (string, optional) - Specify version
  • git_url (string, optional) - Git URL to install from
  • branch_install (string, optional) - Git branch
  • tag_install (string, optional) - Git tag
  • rev_install (string, optional) - Git commit
  • path_install (string, optional) - Local path
  • bin_install (string, optional) - Install only specified binary
  • bins_install (boolean, optional) - Install all binaries
  • example_install (string, optional) - Install only specified example
  • examples_install (boolean, optional) - Install all examples
  • force (boolean, optional) - Force overwrite
  • no_track (boolean, optional) - Don't save tracking information
  • locked (boolean, optional) - Assert Cargo.lock unchanged
  • root (string, optional) - Installation directory
  • registry (string, optional) - Registry to use
  • index (string, optional) - Registry index
  • list (boolean, optional) - List installed packages

uninstall Parameters

  • query (string, required) - Package name to uninstall
  • bin_install (string, optional) - Only uninstall specified binary
  • root (string, optional) - Directory to uninstall from

Utility Parameters

metadata Parameters

  • no_deps (boolean, optional) - Don't fetch dependencies
  • format_version (integer, optional) - Format version

Protocol Support

This server implements MCP protocol version 2024-11-05 and supports:

  • initialize - Server initialization
  • tools/list - List available tools
  • tools/call - Execute cargo commands

Development

To contribute to this project:

  1. Clone the repository
  2. Make your changes
  3. Test with cargo check and cargo build
  4. Format code with cargo fmt
  5. Run lints with cargo clippy

Error Handling

The server provides detailed error messages when cargo commands fail, including both stdout and stderr output from the cargo process.

常见问题

5 问
答案由本站依据条目字段整理,不引用上游原文
Cargo MCP Eb2c96d6 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Cargo MCP Eb2c96d6 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Cargo MCP Eb2c96d6 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Cargo MCP Eb2c96d6 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Cargo MCP Eb2c96d6 能提供哪些能力?

资料显示能力标签包括 代码分析、Rust、构建工具、依赖管理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。