MCP Server: SSH Rails Runner
by tadasant
An MCP server that enables secure remote execution of Rails console commands via SSH. This server provides tools for both read-only operations and carefully managed mutations in a deployed Rails environment.
Last updated: N/A
What is MCP Server: SSH Rails Runner?
This is an MCP server that allows you to securely execute Rails console commands on a remote server via SSH. It provides tools for read-only operations and carefully managed mutations in a deployed Rails environment.
How to use MCP Server: SSH Rails Runner?
First, install the server using npm install
and npm run build
. Then, configure the necessary environment variables (SSH_HOST, SSH_USER, SSH_PRIVATE_KEY_PATH, RAILS_WORKING_DIR). Finally, you can use the provided tools (run_read_only, dry_run_mutate, execute_mutate) to interact with your Rails application.
Key features of MCP Server: SSH Rails Runner
Remote Rails console execution over SSH
Safe read-only operations
Dry-run capability for mutations
Execution of approved mutations
Resource management for code snippets
Use cases of MCP Server: SSH Rails Runner
Data wrangling and analysis in a deployed Rails environment
Performing read-only queries on a remote database
Planning and validating potential database mutations
Executing approved database changes
Integrating with tools like Cursor for enhanced development workflows
FAQ from MCP Server: SSH Rails Runner
What is the purpose of this server?
What is the purpose of this server?
It allows you to securely execute Rails console commands on a remote server via SSH.
What environment variables are required?
What environment variables are required?
SSH_HOST, SSH_USER, SSH_PRIVATE_KEY_PATH, and RAILS_WORKING_DIR are required.
What are the available tools?
What are the available tools?
The available tools are run_read_only, dry_run_mutate, and execute_mutate.
What is dry_run_mutate?
What is dry_run_mutate?
It plans and validates potential mutations without executing them, creating a code snippet resource with the proposed changes.
What security considerations should I keep in mind?
What security considerations should I keep in mind?
Only use with trusted SSH endpoints from your own local machine and review all mutations before execution.