R Packagedev Mcp
Expose R package authoring with usethis, devtools, renv, and testthat to your agent through a stdio MCP while you build statistical tooling.
Overview
R Package Dev MCP is a MCP server for the Build phase that automates R package development with usethis, devtools, renv, and testthat over stdio.
What is this MCP server?
- stdio MCP server r-packagedev-mcp (npm v1.0.1) for R package workflows
- Wraps usethis scaffolding, devtools build/check cycles, renv environments, and testthat suites
- Lets agents run package-dev commands instead of memorizing R console incantations
- Targets maintainers shipping CRAN-style or internal R packages
- Lightweight npm bridge—requires local R toolchain alongside MCP client
- MCP server version 1.0.1
- npm package identifier r-packagedev-mcp
- 4 named R ecosystems in description: usethis, devtools, renv, testthat
What problem does it solve?
R package maintainers waste cycles translating repetitive usethis/devtools/testthat steps into chat-friendly instructions the agent cannot execute.
Who is it for?
Indie R developers and small teams publishing packages who already use the tidyverse-adjacent dev stack and want MCP-native tooling.
Skip if: JavaScript-only SaaS builders, analysts who only run notebooks, or users without a local R installation.
What do I get? / Deliverables
Your agent can invoke structured R package development operations so scaffolding, checks, and tests stay consistent across sessions.
- Agent-executable R package scaffold and maintenance commands
- Consistent renv and testthat workflows from chat-driven development
- MCP bridge between npm transport and local R toolchain
Recommended MCP Servers
Journey fit
R package creation is core product construction for data-science developers, not distribution or production monitoring. Backend subphase fits library/package implementation, dependencies (renv), and automated tests (testthat).
How it compares
R-specific devtools MCP bridge, not a general polyglot build server or Python packaging assistant.
Common Questions / FAQ
Who is R Package Dev MCP for?
R package authors and data-science solo builders who want MCP access to usethis, devtools, renv, and testthat from their coding agent.
When should I use R Package Dev MCP?
Use it during Build while creating, testing, and hardening an R package before you ship documentation or publish to CRAN.
How do I add R Package Dev MCP to my agent?
Install the npm package r-packagedev-mcp, configure stdio in your MCP client, and ensure R with usethis, devtools, renv, and testthat is available on your machine.