Database MCP

MCP client setup

After the Docker demo passes, attach a local MCP client through tested stdio config shapes.

Overview

The primary proof path is still the one-command Docker demo. Client-specific configuration is the next step after the runner has proven semantic tools, proposals, guarded writeback, idempotency, conflict, and replay locally.

Synapsor Runner uses stdio as the primary local MCP transport. The checked-in client config examples are shape-verified by the runner repository; they start the runner, call tools/list, and verify semantic tools without exposing raw SQL, approval, or commit tools.

Use the client UI only for model-facing tool requests. Approvals and writeback remain outside model-callable MCP tools.

Developer notes

Run `./scripts/demo-docker.sh` before configuring a client.
Use the checked-in Claude Desktop, Cursor, VS Code, or generic stdio snippets as starting points.
Do not expose database URLs or write credentials to client-side browser code.
Do not expose approve_proposal or commit_proposal as model-callable tools.

Verify client configs

client-configs.sh

cd ../synapsor-runner
corepack pnpm test:mcp-client-configs

Examples

json

{
  "mcpServers": {
    "synapsor-runner": {
      "command": "corepack",
      "args": ["pnpm", "runner", "mcp", "serve", "--config", "./synapsor.runner.json"],
      "env": {
        "SYNAPSOR_TENANT_ID": "acme",
        "SYNAPSOR_PRINCIPAL": "local_agent"
      }
    }
  }
}