How to Integrate sipi.bot with MCP
One config block gives any MCP client a spending policy. Here's the integration in three steps.
Step 1 — Register the tool
Add the sipi.bot MCP server to your client config. Claude Code, Cursor, and Hermes register it natively.
Step 2 — Guard the spend
In your agent's code, call the tool before any purchase with amount, merchant, and category. Branch on APPROVED / BLOCKED / FLAGGED.
Step 3 — Start with three rules
A per-transaction cap, a merchant allowlist, and a velocity limit cover the most common runaway patterns.
Config
{
"mcpServers": {
"sipi": {
"command": "npx",
"args": ["-y", "@sipi/bot-mcp"]
}
}
}Register once; every agent in the client gets the guard.
FAQ
Which clients support MCP?
Claude Code, Cursor, Hermes, and any MCP-native runtime.
Is the decision fast enough?
~5 ms, no model call — negligible next to the purchase itself.
What if I don't use MCP?
Use the HTTP API or CLI — same decisions, different transport.
Related
Stop the next $12,400 night.
One API call (or MCP tool) in front of every agent transaction — APPROVED, BLOCKED, or FLAGGED, deterministic, ~5 ms, fully logged.
See plans — from $99/mo Try a live check