For AI agents & MCP clients

Onboard onto Toffu
without a human.

Discovery, signup, and a working MCP key in a single request. No forms, no email verification, no OAuth consent click, no waiting on us. Your agent is running marketing tasks in one round-trip.

one request → a working key
curl -X POST https://mcp.toffu.ai/agent/signup \
  -H 'content-type: application/json' \
  -d '{"company_name":"Acme","email":"you@acme.com"}'
01

Discover

Read agent.json or llms.txt. Both spell out what Toffu does and how to connect — no docs-crawling required.

02

Sign up

One unauthenticated POST creates a real, persistent workspace and hands back a live MCP key. Nothing to verify, nobody to wait on.

03

Work

Point any MCP client at the endpoint with that key and call send_message. Ask for last week’s Meta numbers, or tell it to fix a budget.

What comes back

The key is a Bearer token for https://mcp.toffu.ai/mcp. Send it with every call — that’s the whole handshake.

200 · signup response
{
  "api_key": "toffu_9f3c…",
  "company_id": "6a5f71c2…",
  "mcp": { "endpoint": "https://mcp.toffu.ai/mcp" },
  "claim_url": "https://toffu.ai"
}

Then just ask

Toffu is connected to the company’s Google, Meta, and LinkedIn ad accounts, analytics, content, and memory. Delegate in plain language.

send_message
→ "How did last week's Meta campaigns perform?"
→ "Pause anything under a 1.2 ROAS and tell me what you paused."
→ "Draft three LinkedIn posts from our latest case study."
Free to start
New workspaces run in a bounded onboarding sandbox until they connect an integration and do real work.
Claimable
Pass a real email and a human can later sign in at toffu.ai to take it over. An email that already exists is refused — no takeover.
Standards-based
Prefer a consent flow? Toffu also speaks OAuth 2.1 + PKCE with Dynamic Client Registration. See the MCP guide.