Use Zapito from Claude or Cursor via MCP

Zapito ships a Model Context Protocol server, so any MCP client — Claude Code, Claude Desktop, Cursor — can list your bots, read and edit their flows, check usage, and chat with a bot, straight from your editor.

1. Create a Zapito API key

In the app, go to Settings → API keys → Zapito API keys, give the key a label (e.g. Claude Code) and hit Create key. Copy the zap_live_… token right away — only its hash is stored, so it’s shown exactly once. A key acts as your whole workspace; revoke it anytime from the same panel.

Tokens keep the historical zap_live_ prefix from before the Zapito rename — existing keys stay valid, and new keys use the same prefix on purpose.

2. Connect your client

The server speaks Streamable HTTP at:

https://api-production-bd72.up.railway.app/api/mcp

Claude Code

claude mcp add --transport http zapito \
  https://api-production-bd72.up.railway.app/api/mcp \
  --header "Authorization: Bearer zap_live_…"

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "zapito": {
      "url": "https://api-production-bd72.up.railway.app/api/mcp",
      "headers": { "Authorization": "Bearer zap_live_…" }
    }
  }
}

3. What you can do

Tool	What it does
list_bots	Every bot with id, status, connected channels, node count.
get_flow	A bot’s full canvas — nodes and edges JSON.
update_flow	Replace a bot’s canvas (whole flow, same shape get_flow returns).
get_usage	Message/conversation totals + by-channel and by-model breakdowns.
send_test_message	Chat with a bot on the test channel — returns the reply, confidence, and the node-by-node trace.

Try: “List my Zapito bots and send the FAQ bot a test message asking about returns.” The test channel runs the same engine as production, so the trace you get back is exactly what a customer message would do.

Notes

• The same key also authenticates the plain REST API (/api/bots, /api/usage, …) with Authorization: Bearer zap_live_….
• update_flow replaces the entire canvas — have the client read get_flow first and send back the full edited graph.
• Keys are workspace-scoped. Treat them like passwords; revoke immediately if one leaks.