MCP Server: SSH Rails Runner

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Server: SSH Rails Runner?

MCP Server: SSH Rails Runner is a tool that enables secure remote execution of Rails console commands via SSH, allowing for both read-only operations and managed mutations in a deployed Rails environment.

how to use MCP Server: SSH Rails Runner?

To use the MCP Server, install the package, configure the necessary environment variables, and integrate it with your Claude Desktop configuration to execute Rails commands remotely.

key features of MCP Server: SSH Rails Runner?

  • Remote execution of Rails console commands 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?

  1. Executing read-only queries on a remote Rails application.
  2. Planning and validating database mutations without immediate execution.
  3. Safely executing approved changes to a Rails application database.

FAQ from MCP Server: SSH Rails Runner?

  • Is it safe to use this tool for database mutations?

Yes, but ensure you review all mutations before execution and only use trusted SSH endpoints.

  • What are the prerequisites for using this tool?

You need to have SSH access to the remote Rails environment and the necessary environment variables configured.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago