// MCP TOOL REFERENCE

R PACKAGEDEV TOOLS

30 tools from the R Packagedev MCP Server, categorised by risk level.

View the R Packagedev policy → Token cost: 3,911 tokens →
// ALL 30 R PACKAGEDEV TOOLS
READ 10 tools
Read check Run R CMD check on the package using devtools::check(). Identifies errors, warnings, and notes that would p... Read load_all Simulate installing and attaching the package using devtools::load_all(). Makes all functions available in ... Read renv_snapshot Record the current package dependencies into renv.lock using renv::snapshot(). Read renv_status Report whether the project library is synchronised with renv.lock using renv::status(). Read spell_check Spell-check the package documentation and vignettes using devtools::spell_check(). Read test Run the package's test suite (or a filtered subset) using devtools::test(). Reports test results in the cho... Read test_dir Run all test files in a directory (optionally filtered) using testthat::test_dir(). Returns a summary of pa... Read test_file Run a single testthat test file using testthat::test_file(). Useful for rapid iteration on a specific file. Read use_data Export one or more R objects as package data files under data/ using usethis::use_data(). The objects must ... Read use_test Create a matching test file under tests/testthat/ for a given function or module using usethis::use_test()....
WRITE 17 tools
Write create_package Create a new R package skeleton at the specified path using usethis::create_package(). Sets up DESCRIPTION,... Write document Generate roxygen2 documentation and update NAMESPACE using devtools::document(). Reads @-tags from R source... Write install Install the package into the local R library using devtools::install(). Write renv_init Initialise an renv project-local library for the project using renv::init(). Creates renv/ and renv.lock, a... Write renv_install Install packages into the renv project library using renv::install(). Supports CRAN packages, GitHub (user/... Write renv_restore Restore packages from renv.lock to recreate the recorded environment using renv::restore(). Write renv_update Update packages in the renv project library using renv::update(). If no package names are given, all outdat... Write use_git Initialise a Git repository in the package and make an initial commit using usethis::use_git(). Write use_github Create a GitHub remote for the package and push using usethis::use_github(). Requires a GitHub PAT configur... Write use_gpl3_license Add a GPL-3 LICENSE file and update DESCRIPTION License field using usethis::use_gpl3_license(). Write use_mit_license Add an MIT LICENSE file and update DESCRIPTION License field using usethis::use_mit_license(). Write use_package Add a package dependency to DESCRIPTION using usethis::use_package(). Supports Imports, Suggests, Depends, ... Write use_pipe Add the magrittr pipe (%>%) to the package via usethis::use_pipe(). Creates utils-pipe.R and updates NAMESP... Write use_r Add a new R source file under R/ in an existing package using usethis::use_r(). Creates 'R/<name>.R' with m... Write use_readme_md Add a README.md to the package root using usethis::use_readme_md(). Write use_testthat Configure the testthat testing infrastructure for a package using usethis::use_testthat(). Creates tests/te... Write use_vignette Create a new vignette stub (Rmd file) under vignettes/ using usethis::use_vignette().
DESTRUCTIVE 1 tools
Destructive renv_clean Remove unused packages or temporary files from the renv library using renv::clean().
EXECUTE 2 tools
Execute build Build a source (or binary) package tarball using devtools::build(). Execute build_readme Render README.Rmd to README.md and update GitHub preview using devtools::build_readme().
// RUNNING THIS SERVER

The managed route: connect R Packagedev through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y r-packagedev-mcp
// FAQ
How many tools does the R Packagedev MCP server have? +

The R Packagedev MCP server exposes 30 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on R Packagedev tools? +

Route the R Packagedev server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do R Packagedev tools fall into? +

R Packagedev tools are categorised as Read (10), Write (17), Destructive (1), Execute (2). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.