Prerequisites
- An admin login to your Sapot Chat account.
- Claude Code (or another MCP-compatible client).
- Your numeric account id — the number in your dashboard URL (
/app/accounts/<id>/…), also shown in Settings.
1
Mint a scoped key
In the dashboard: Settings → API & Agents → Create key.
- Give it a clear name (one key per agent or use case).
- Grant the fewest scopes you need — for this Quickstart, just
conversations:read. - Optionally set an expiry.
2
Connect
Register the Sapot Chat MCP server with your agent. With Claude Code:Replace
https://mcp.sapot.ai/mcp with your environment’s MCP URL, YOUR_AGENT_KEY with the key from step 1, and YOUR_ACCOUNT_ID with your numeric account id. The key and account id are fixed by the connection — you never pass the account into a tool call.No hosted MCP URL yet? The MCP server is a tiny stateless proxy — run it yourself and point it at the API. It holds no credentials and needs no model key:Then connect to your local instance (same key + headers):Your key still authenticates against the real API, so the agent operates your actual account — the local proxy just relays the request.
3
Verify
Ask your agent to list the available tools, then run a read:
“List my open conversations.”which calls
list_conversations(status="open"). A result confirms the connection is live and the key works. You’ll only see tools your scopes unlock — with just conversations:read, that’s the six read tools.Read the mental model before writing
Two things will otherwise look like bugs:- A
missing the required scoperesponse means the key wasn’t granted that capability — add the scope (or leave it off on purpose). See Authentication & Scopes. - A campaign that stays a draft, or a flow whose graph you can’t see, are enforced boundaries, not failures.
Next steps
Authentication & Scopes
The default-deny scope model and how keys authenticate.
The Agent Skill
Install the companion skill so the agent uses the tools correctly out of the box.

