Cursor Rust Tools

Created By
terhechtea year ago
A MCP server to allow the LLM in Cursor to access Rust Analyzer, Crate Docs and Cargo Commands.
Overview

What is Cursor Rust Tools?

Cursor Rust Tools is a server that enables the LLM in Cursor to access Rust Analyzer, Crate Docs, and Cargo Commands, enhancing the capabilities of AI agents by providing real-time Rust type information.

How to use Cursor Rust Tools?

To use Cursor Rust Tools, install it via Cargo with the command cargo install --git https://github.com/terhechte/cursor-rust-tools, then run it with or without a UI to configure your projects and access Rust documentation.

Key features of Cursor Rust Tools?

  • Access to Rust type information and documentation through the Model Context Protocol (MCP).
  • Retrieve hover information, references, and implementations for Rust symbols.
  • Execute Cargo commands like cargo test and cargo check directly.

Use cases of Cursor Rust Tools?

  1. Assisting AI agents in understanding Rust codebases.
  2. Providing up-to-date documentation for Rust crates.
  3. Enhancing development workflows with real-time type information.

FAQ from Cursor Rust Tools?

  • Can Cursor Rust Tools be used with any Rust project?

Yes! It can be configured to work with any Rust project by setting up the appropriate configuration files.

  • Is there a UI for Cursor Rust Tools?

Yes! You can run it with a UI for easier configuration and management of projects.

  • How does Cursor Rust Tools improve AI interactions?

By providing real-time access to Rust type information, it allows AI to make more informed decisions and reduce errors.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
terhechte
Star
8
Language
Rust
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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