F
licenseNot graded
qualityA
maintenanceConnect RStudio directly to Claude Desktop, Claude Code, Codex, Gemini CLI, or any other MCP based AI assistant for interactive coding and data analysis.
346
-
rstudio-mcp-server
by lerlerchan
Related Servers
Alternatives to rstudio-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to deeply integrate with RStudio for environment management, code execution, project management, and package management.11MIT
- AlicenseNot gradedqualityCmaintenanceAccess your live RStudio session from any MCP-capable client. Inspect objects, preview data, and execute R code directly in the current RStudio environment.MIT
- AlicenseNot gradedqualityBmaintenanceEnables developers to build, test, debug, and operate MCP servers from VS Code or CI, while also exposing trusted MCP capabilities to AI agents.MIT
- FlicenseNot gradedqualityCmaintenanceConverts VSCode into an MCP server that enables external clients to remotely execute VSCode internal commands, query workspace information, and interact with the editor through HTTP streaming. Built on the FastMCP framework with security controls and real-time monitoring.63-
- AlicenseDqualityBmaintenanceEnables controlled local developer operations including file and process management, shell execution, SSH, WSL, Docker, Git, browser and desktop automation, media processing, and asynchronous jobs through MCP.146MIT
TDQS
A3.5/5.0
Scored across 12 tools
Disambiguation5/5
Each tool targets a distinct action: jamovi_* for module tasks, r_* for R package development and general execution. Even closely related tools like r_test_file and r_test_package are clearly differentiated by their scope.
Naming Consistency4/5
Most tools follow a prefix_verb_noun pattern (e.g., r_build_package, r_check_package). Minor deviations like 'r_execute' (no noun) and 'r_workspace_ls' (noun_verb) are still clear and do not cause confusion.
Tool Count5/5
With 12 tools, the set covers jamovi module work and comprehensive R package development (build, check, document, install, test, load) without being bloated. Each tool serves a clear purpose.
Completeness4/5
The R package development tools adequately cover the core lifecycle (build, check, document, test, install), but missing operations like package removal or update are minor gaps. Jamovi tools are limited to build and check, which is acceptable for a niche focus.
Maintenance
ActivityInactive
ResponsivenessNo issues