Rails MCP server

rails-mcp

A self-hosted, caller-configured default-deny action registry + append-only spend ledger + CLI-only sign-off audit trail, exposed as MCP tools. Different category from this author's other six MCP servers (mcp-factory, rag-mcp, bus-mcp, desktop-mcp, github-mcp, discord-mcp) -- those are devtools ("connect an agent to X"); this one is governance and safety: "stop an agent from doing something irreversible without a human noticing."

Ported and generalized from a live internal registry (shared/rails/, 31 tests, running against a real multi-bot fleet since 2026-07-06) -- this pattern shipped internally before it shipped publicly.

What this is / is not

Is:

unconditionally GATED (default-deny), registered or not.

• A schema + pure logic for classifying action_type strings as

enforcement (enforcementlayer, enforcementpointer, ceremony) -- informational, never permissive.

• A place to register what you know about an action-type's current

registry's current hash and when.

• An append-only spend-intent ledger + rolling-window budget check.
• An append-only human sign-off ledger, recording who blessed the

Is NOT:

anything by itself. You still wire it into your own PreToolUse hook, permission deny-list, or CI gate -- rails-mcp gives you the schema and the audit trail, not the interceptor. recordspendintent records intent to spend; it never calls a vendor, a paid API, or a broker, and nothing here stops an over-budget spend from happening.

• Not an enforcer. classify_action returning GATED does not block

their own registry (a YAML/JSON config file, or a plain dict). No fleet's specific action-types ship with this package.

• Not pre-loaded with any action-type data. Every adopter supplies

string per registry; fine for v1, a known limitation for later.

• Not multi-tenant. The sign-off ledger assumes one human operator

The one invariant that is never configurable

classifyaction(actiontype) always returns "GATED" -- registered or not, whatever config was loaded, no argument or config field can change it. This is the whole product. A config-driven fail-open knob would defeat the entire pitch, so classify() (railsmcp/registry.py) takes only an actiontype argument: there is no parameter through which a caller could ever make it return anything permissive. isactionregistered answers a separate, purely informational question -- "do I know something about this action-type's enforcement?" -- and never feeds back into the GATED verdict.

Quickstart (60 seconds)

pip install rails-mcp

Add to your Claude Desktop/Code MCP config:

{
  "mcpServers": {
    "rails-mcp": {
      "command": "rails-mcp"
    }
  }
}

No console script on PATH? Fall back to "command": "python", "args": ["-m", "rails_mcp"].

By default the registry loads empty (honest-empty, not fail-open -- classify_action is still unconditionally GATED for everything). Point it at your own action-type config:

{
  "mcpServers": {
    "rails-mcp": {
      "command": "rails-mcp",
      "env": { "RAILS_MCP_CONFIG_PATH": "C:\\path\\to\\rails.config.yaml" }
    }
  }
}

See examples/rails.config.example.yaml (or .example.json) for the config shape.

Tools

All six are read-mostly -- none of them can write to the sign-off ledger.

Shortened. The full README is on GitHub.