Reelier MCP Server

Agents make claims, Reelier writes receipts - record an agent workflow once, replay it deterministically at 0 tokens, and get an asserted receipt on

Local serverstdio

What is the Reelier MCP server?

Connect Reelier to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Agents make claims, Reelier writes receipts - record an agent workflow once, replay it deterministically at 0 tokens, and get an asserted receipt on every run. The reelier mcp server is what makes that connection.

What the server does

Reelier records the run that worked, freezes it as a replayable skill, and replays it deterministically — every run comes back as a receipt: proof of what the agent did and what changed because of it. Agents make claims. Reelier writes receipts.

  • 1,000 / 1,000 replays byte-identical —
  • Every replay ships a signed receipt — — proof of what ran and what changed, never a claim
  • 0 LLM calls at replay — — deterministic re-execution, not re-reasoning

Installation

reelier on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: REELIER_CLOUD_URL, REELIER_CLOUD_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by seldonframe; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How to install the Reelier MCP server

{
  "mcpServers": {
    "reelier": {
      "command": "npx",
      "args": ["-y", "reelier"],
      "env": {
        "REELIER_CLOUD_URL": "your-value",
        "REELIER_CLOUD_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
REELIER_CLOUD_URLEndpoint or connection string the server talks to.Yes
REELIER_CLOUD_KEYCredential the server authenticates with.Yes

Frequently asked questions

It connects Reelier to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Reelier directly.