Mmcp.market

Cargo MCP server

by Dave-London·io.github.Dave-London/cargo·v0.7.1·138 stars
No reviews yet

Structured Rust cargo operations (build, test, clippy) as typed JSON.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Established

138 stars70 downloads/wk

Reviews

Write one

Nobody has reviewed Cargo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cargo tools (10, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add

    Adds dependencies to a Rust project and returns structured output.

  • buildwrite action

    Runs cargo build and returns structured diagnostics (file, line, code, severity, message). Use instead of running `cargo build` in the terminal.

  • checkwrite action

    Runs cargo check (type check without full build) and returns structured diagnostics. Faster than build for error checking. Use instead of running `cargo check` in the terminal.

  • clippywrite action

    Runs cargo clippy and returns structured lint diagnostics. Use instead of running `cargo clippy` in the terminal.

  • doc

    Generates Rust documentation and returns structured output with warning count. Use instead of running `cargo doc` in the terminal.

  • fmt

    Checks or fixes Rust formatting and returns structured output. Use instead of running `cargo fmt` in the terminal.

  • removewrite action

    Removes dependencies from a Rust project and returns structured output. Use instead of running `cargo remove` in the terminal.

  • runwrite action

    Runs a cargo binary and returns structured output (exit code, stdout, stderr). Use instead of running `cargo run` in the terminal.

  • tree

    Displays the dependency tree for a Rust project.

  • updatewrite action

    Updates dependencies in the lock file. Optionally updates a single package.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan35 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Cargo in Claude Code, Cursor or VS Code

Runs npx -y @paretools/cargo on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add cargo -- npx -y @paretools/cargo
Add to Cursor

What the publisher says

From the Cargo repository's README, as published. We do not edit it. Read it on GitHub

  Pare

Reliable, structured CLI output for AI agents — no more parsing fragile terminal text.

Pare provides MCP servers that wrap common developer tools (git, npm, docker, test runners, etc.) and return clean, schema-validated JSON instead of raw terminal text. Agents get typed data they can act on directly, without brittle string parsing.

The Problem

Parsing CLI output is fragile. Raw terminal text includes ANSI escape codes, decorative headers, progress bars, locale-specific formatting, and platform differences that break agent workflows in subtle ways. An agent that works fine with git status on macOS may fail on Windows because the output format changed. A test runner's summary line might shift between versions, silently breaking a regex.

Pare eliminates this entire class of errors by returning schema-validated JSON with consistent field names, regardless of platform, tool version, or locale. As a bonus, structured output is significantly smaller — agents use fewer tokens per tool call:

Token estimates use ~4 chars/token. The biggest savings appear on verbose commands (builds, installs, tests). For simpler tools like eslint or tsc, the main advantage is reliable structured data — agents can use typed JSON directly rather than parsing strings.

How It Works

Each Pare tool returns two outputs:

  • content — human-readable text, for MCP clients that display it
  • structuredContent — typed, schema-validated JSON, ready for agents to process

This uses MCP's structuredContent and outputSchema features to provide type-safe, validated data that agents can rely on without custom parsing.

Example: git status

Raw git output (~118 tokens):

On branch main
Your branch is ahead of 'origin/main' by 2 commits.
  (use "git push" to publish your local commits)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cargo: common questions

Is Cargo MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Cargo safety report
How do I install Cargo?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Cargo need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cargo maintained?
The last commit was 21 days ago (2026-09-22). The latest release is v0.7.1.

More from Dave-London →