30 tools from the R Packagedev MCP Server, categorised by risk level.
View the R Packagedev policy →check Run R CMD check on the package using devtools::check(). Identifies errors, warnings, and notes that would prevent CRAN submission. load_all Simulate installing and attaching the package using devtools::load_all(). Makes all functions available in the current R session for interactive te... 2/5 renv_snapshot Record the current package dependencies into renv.lock using renv::snapshot(). renv_status Report whether the project library is synchronised with renv.lock using renv::status(). spell_check Spell-check the package documentation and vignettes using devtools::spell_check(). test Run the package's test suite (or a filtered subset) using devtools::test(). Reports test results in the chosen format. test_dir Run all test files in a directory (optionally filtered) using testthat::test_dir(). Returns a summary of pass/fail/skip counts. 2/5 test_file Run a single testthat test file using testthat::test_file(). Useful for rapid iteration on a specific file. use_data Export one or more R objects as package data files under data/ using usethis::use_data(). The objects must already be loaded in the R environment. use_test Create a matching test file under tests/testthat/ for a given function or module using usethis::use_test(). Automatically sets up testthat if not a... create_package Create a new R package skeleton at the specified path using usethis::create_package(). Sets up DESCRIPTION, NAMESPACE, and the R/ directory. 3/5 document Generate roxygen2 documentation and update NAMESPACE using devtools::document(). Reads @-tags from R source and creates man/*.Rd files. 2/5 install Install the package into the local R library using devtools::install(). 2/5 renv_init Initialise an renv project-local library for the project using renv::init(). Creates renv/ and renv.lock, and updates .Rprofile. 2/5 renv_install Install packages into the renv project library using renv::install(). Supports CRAN packages, GitHub (user/repo), or version-pinned installs. 2/5 renv_restore Restore packages from renv.lock to recreate the recorded environment using renv::restore(). 2/5 renv_update Update packages in the renv project library using renv::update(). If no package names are given, all outdated packages are updated. 2/5 use_git Initialise a Git repository in the package and make an initial commit using usethis::use_git(). 2/5 use_github Create a GitHub remote for the package and push using usethis::use_github(). Requires a GitHub PAT configured via GITHUB_PAT or gh_token(). 2/5 use_gpl3_license Add a GPL-3 LICENSE file and update DESCRIPTION License field using usethis::use_gpl3_license(). 2/5 use_mit_license Add an MIT LICENSE file and update DESCRIPTION License field using usethis::use_mit_license(). 2/5 use_package Add a package dependency to DESCRIPTION using usethis::use_package(). Supports Imports, Suggests, Depends, LinkingTo, and Enhances. 2/5 use_pipe Add the magrittr pipe (%>%) to the package via usethis::use_pipe(). Creates utils-pipe.R and updates NAMESPACE. 2/5 use_r Add a new R source file under R/ in an existing package using usethis::use_r(). Creates 'R/<name>.R' with minimal boilerplate. 2/5 use_readme_md Add a README.md to the package root using usethis::use_readme_md(). 3/5 use_testthat Configure the testthat testing infrastructure for a package using usethis::use_testthat(). Creates tests/testthat/ and adds testthat to Suggests. 2/5 use_vignette Create a new vignette stub (Rmd file) under vignettes/ using usethis::use_vignette(). 2/5 The R Packagedev MCP server exposes 30 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the R Packagedev server.
R Packagedev tools are categorised as Read (10), Write (17), Destructive (1), Execute (2). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept