Use with Claude Code

A Space API key turns Claude Code into a teammate inside one Wakato Space: it can read your contacts and tables, build and publish pages, draft social posts, run automations, even author full Space Apps — limited to exactly the scopes you granted the key.

1. Mint a key

In Wakato: Space → Settings → API Keys → New API key. Pick the scopes you want Claude to have (start with read + write; add run scopes only for actions you want it to take live). Copy the wks_live_… token — it's shown once.

2. Connect over MCP (recommended)

One command from your project directory:

claude mcp add --transport http wakato \
  https://api.wakato.io/functions/v1/space-mcp \
  --header "Authorization: Bearer wks_live_YOUR_TOKEN"

Or commit a .mcp.json to the project (keep the token out of git — use an environment variable):

{
  "mcpServers": {
    "wakato": {
      "type": "http",
      "url": "https://api.wakato.io/functions/v1/space-mcp",
      "headers": { "Authorization": "Bearer ${WAKATO_SPACE_KEY}" }
    }
  }
}

Claude Code discovers every tool the key allows via tools/list — tools the key lacks scopes for are not even listed. Then just ask:

• "List my open tasks and mark the overdue ones high priority."
• "Build a pricing page with our contact form embedded, but don't publish it."
• "Draft next week's LinkedIn posts from the contents of the Launch table."

3. Or call REST from scripts

The same token works as a plain Bearer token against https://api.wakato.io/functions/v1/space-api — useful inside Bash steps, CI jobs, or any non-MCP tool:

curl https://api.wakato.io/functions/v1/space-api/contacts \
  -H "Authorization: Bearer $WAKATO_SPACE_KEY"

See the API Reference for every endpoint and its required scope.

4. Add context via CLAUDE.md

Drop a note in your project's CLAUDE.md so Claude knows what the connection is for:

## Wakato
The "wakato" MCP server is connected to our Marketing Space.
Drafts are fine to create freely; anything live (publish, post, send)
should be confirmed with me first.

Safety recap

• A key is locked to one Space — it can't see other Spaces, members, or your login.
• write creates drafts; going live (publish/post/send/run) needs the matching run scope.
• Wallet and Finance are read-only; secret values are never returned.
• Revoke the key in Space Settings and the connection dies instantly.