Cargo Metadata MCP Server

Created By
frozenliba year ago
AI任せで作ってみたMCP Server
Overview

What is Cargo Metadata MCP Server?

Cargo Metadata MCP Server is an implementation that provides metadata information for Cargo projects using the Model Context Protocol (MCP).

How to use Cargo Metadata MCP Server?

To use the server, build it using cargo build --release and run it with cargo run, or execute the pre-built binary directly. To integrate with an MCP client, add the server path to the client's configuration file.

Key features of Cargo Metadata MCP Server?

  • Retrieve project metadata information
  • Get package information
  • Obtain dependency lists
  • Access build targets
  • Fetch workspace information
  • Retrieve feature information

Use cases of Cargo Metadata MCP Server?

  1. Managing and retrieving metadata for Rust projects.
  2. Integrating with development tools that require Cargo project information.
  3. Facilitating automated build processes by providing necessary project details.

FAQ from Cargo Metadata MCP Server?

  • What is MCP?

MCP stands for Model Context Protocol, which is used for structured communication between tools.

  • Can I use this server with any MCP client?

Yes, as long as the client supports the MCP protocol, it can be integrated with this server.

  • Is there any documentation available?

Yes, detailed documentation can be found on the project's GitHub page.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
frozenlib
Star
0
Language
Rust
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago