ClaudeR MCP Server

Connect ClaudeR to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Connect RStudio to AI assistants for interactive R coding and data analysis. The clauder mcp server is what makes that connection.

What the server does

Connect RStudio to Claude Code, Codex, Gemini CLI, or any MCP-based LLM agent for interactive coding, multi-agent orchestration, and automated manuscript auditing.

• execute_r — Execute R code and return the output
• execute_r_with_plot — Execute R code that generates a plot that the model can see
• execute_r_async — Execute long-running R code asynchronously (>25 seconds). Returns a job ID for polling
• get_async_result — Poll for the result of an async job. Includes a built-in delay to throttle polling
• list_sessions — List all active RStudio sessions the agent can connect to
• connect_session — Connect to a specific RStudio session by name for multi-session workflows

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Value — first auditing (R 0.6.0 / clauder-mcp 0.9.0).** Built from field feedback after a full manuscript+supplement audit. read_file now transparently
• Deep — dive audit release (R 0.3.1 / clauder-mcp 0.6.2).** 20+ bug fixes across the addin, bridge, and Lab Mode: reopened addin UIs now share live state
• Multi — Agent Coordination Protocol.** Built-in protocol for multiple agents sharing one RStudio session. Agents negotiate through a shared message board in
• Non — blocking async execution.** execute_r_async now runs long-running code in a separate R process via callr, keeping the main session fully responsive
• Visualization — The AI can generate, view, and refine plots and visualizations
• Long — Running Analysis**: Async execution handles model fitting, simulations, and large data processing without timing out

Installation

The server ships on PyPI as clauder-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. ClaudeR's toolset — Value, Deep, Multi and 3 more — is a fair guide to whether it matches your workflow. It is maintained by IMNMV; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.