Cargo.toml Parser

Parse Rust Cargo manifests — package, dependencies (with features), dev/build deps, features, workspace.

Developer Reference & Lookup

Cargo.toml

Package

my-app

Version

0.1.0

Edition

2021

License

MIT

Dependencies

Dev deps

Dependencies (4)

Crate	Version	Features	Flags
serde	1.0	derive
serde_json	1.0	—
tokio	1.36	full
reqwest	0.12	rustls-tls, json	no-default-features

Dev-dependencies (2)

Crate	Version	Features	Flags
mockito	1.4	—
proptest	1.4	—

Build-dependencies (1)

Crate	Version	Features	Flags
prost-build	0.12	—

Features

default	json
json	(empty)
xml	dep:quick-xml

Workspace

members: crates/*

</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl

curl https://api.b-e-a-d.com/tools/cargo-toml-parser/run \
  -H "Content-Type: application/json" \
  -d '{
  "input": "your input here"
}'

JavaScript (fetch)

const res = await fetch("https://api.b-e-a-d.com/tools/cargo-toml-parser/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "input": "your input here"
}),
});
const data = await res.json();
console.log(data.result);

MCP (Claude Desktop / Claude Code)

# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_cargo_toml_parser

Full reference: developer docs · OpenAPI spec

What we parse

[package] metadata, [dependencies] / [dev-dependencies] / [build-dependencies] with both shorthand (name = "1.0") and detailed ({ version = "1.0", features = ["foo"] }) forms,[features], and [workspace].

Note

This is a focused subset parser optimized for Cargo.toml. It handles the shapes that show up in real manifests but doesn't implement every TOML edge case.

What we parse

Note

You might also like