Operate a Sapot Chat account with a coding agent (Claude Code or any MCP client) over a scoped, metered, IP-safe API.
The AI-native / MCP surface is verified on staging and rolling toward production. Endpoints and
tool names are stable; treat the MCP server URL as environment-specific until GA.
Sapot Chat lets you operate an account with a coding agent — Claude Code, or any MCP-compatible client — over a scoped, metered, IP-safe API. The agent can triage and reply to conversations, manage contacts, pull reports, curate your AI Knowledge, manage WhatsApp templates, operate flow agents, and prepare campaign drafts.Unlike handing an AI a full-access personal token, every agent key is limited to the exact capabilities you grant, is metered against your plan, and is prevented — server-side — from doing the two things that must stay human: sending a blast and seeing how your AI flows are built.
Coding agent (Claude Code / MCP client) │ Authorization: Bearer <agent key> │ X-Sapot-Account-Id: <account id> ▼Sapot MCP server ── stateless FastMCP proxy, holds no credentials, │ relays your token per-request ▼ api_access_token: <agent key>Sapot REST API ── validates the scoped agent token, │ enforces the default-deny scope allowlist ▼Your account's data
The MCP server is a thin pass-through: it runs no AI/inference of its own and stores no credentials. Your agent holds the scoped key; the server relays it to the Sapot Chat API, which is the single point that authenticates and authorizes every call. You can also skip MCP and call the REST API directly with the same scoped token.
External customers and partners wiring a coding agent to their own Sapot Chat account. If you just want to use the feature without code, the in-app Help Center has a no-code walkthrough; these docs are the technical reference.
