Replication you can
talk to.
The TwinCommit MCP server connects your replication pipelines to Claude, GitHub Copilot, Cursor and any MCP-compatible assistant. Install it with one command, then check lag, diagnose errors, re-snapshot tables and verify data by asking.
txn 991204, with 2.1M rows on BILLING.LEDGER. It's spilling to disk, so it will apply as one unit at commit. Nothing is broken.max_txn_memory_bytes to 1 GiB for this pipeline?twincommit_caught_up…Super-easy install
One command. Every client.
No servers to deploy and no API keys to mint. The MCP server runs locally next to your assistant and talks to the TwinCommit status endpoint you already have.
- 1
Install
Add the server to your MCP client with one command.
- 2
Connect
Point TWINCOMMIT_URL at a running pipeline status endpoint (default http://localhost:9108).
- 3
Ask
Ask your assistant about lag, errors, broken tables or data verification in plain English.
$ claude mcp add twincommit -- npx -y @twincommit/mcp{
"mcpServers": {
"twincommit": {
"command": "npx",
"args": ["-y", "@twincommit/mcp"],
"env": { "TWINCOMMIT_URL": "http://localhost:9108" }
}
}
}$ code --add-mcp '{"name":"twincommit","command":"npx","args":["-y","@twincommit/mcp"]}'// ~/.cursor/mcp.json
{
"mcpServers": {
"twincommit": { "command": "npx", "args": ["-y", "@twincommit/mcp"] }
}
}Tools
10 tools for day-two operations
Every tool maps to a TwinCommit capability you can also script with the CLI.
list_pipelinesEvery pipeline with its source, target, state and current lag.
get_statusCheckpoint position, open transactions, broken tables and last error.
get_lagLag history for a pipeline over a time window, from Prometheus or /status.
start_pipelineStart or resume a pipeline from its last committed checkpoint.
stop_pipelineDrain in-flight transactions and stop cleanly.
resnapshot_tableRe-snapshot one broken table while the rest keep streaming.
verify_tablesCompare source and target row counts and checksums.
explain_errorTurn a log or apply error into a cause and a concrete fix.
check_sourceRun source prerequisite checks and return the exact fix commands.
tail_eventsStream recent change events for a table (values redacted by default).
Try asking
Things on-call engineers actually ask
Read-only by default
Write tools need TWINCOMMIT_MCP_ALLOW_WRITES=true. Nothing changes unless you say so.
Row values stay private
Tools return metadata only. Row values are redacted unless you explicitly opt in.
Every call audited
Each tool call is logged with its arguments, result status and the client that made it.
MCP server FAQ
What is the TwinCommit MCP server?
+
It is a Model Context Protocol server that exposes TwinCommit pipelines as tools to AI assistants such as Claude, GitHub Copilot and Cursor, so you can monitor and operate replication in plain English.
How do I install the TwinCommit MCP server?
+
Run claude mcp add twincommit -- npx -y @twincommit/mcp for Claude Code, or add the same npx command to the MCP configuration of Claude Desktop, VS Code or Cursor.
Can the assistant change my pipelines?
+
Only if you allow it. The server is read-only by default. Start, stop and re-snapshot tools need TWINCOMMIT_MCP_ALLOW_WRITES=true, and every call is written to an audit log.
Does row data get sent to the AI model?
+
Not by default. Tools return metadata such as positions, counts, lag and errors. Row values are redacted unless you explicitly enable TWINCOMMIT_MCP_ALLOW_ROW_VALUES.
Give your assistant a replication superpower.
Install the MCP server, point it at a pipeline and ask your first question in under a minute.