Connect AI appsone address, a sign-in, and you choose what it may do.

Every AI app that speaks MCP can use Wakato through one address:

There is no key to copy. When you connect, Wakato shows who is asking and lets you choose:

• Where it may work — your whole account (every space you own or run as an admin, including ones to come, plus making spaces, phone numbers, domains and moving money between spaces), or only the spaces you pick.
• What it may do — everything it asked for, read only, or area by area.

Paid actions it runs (AI, texts, searches) come from the wallet of the space it works in, labelled with the app's name. You can change what it may do, or disconnect it, any time in Backstage → Connected apps; the space's owner and admins see apps connected to their space in Settings → Apps.

Claude

In claude.ai or the Claude desktop app: Settings → Connectors → Add custom connector. Name it Wakato, paste https://mcp.wakato.io/mcp, click Add, then Connect. Claude detects the sign-in and registers itself; leave those options as they are. Allow on the Wakato page, and Wakato is in Claude's tools menu in a new chat.

Custom connectors need a paid Claude plan. On Team and Enterprise plans an owner may have to add the connector for the organization first.

ChatGPT

ChatGPT adds custom connectors in developer mode: Settings → Apps & Connectors, turn on developer mode under Advanced, then create a connector with the URL https://mcp.wakato.io/mcp and OAuth as the authentication. Menu names change often; the URL and the sign-in are what matter.

Claude Code

claude mcp add --transport http wakato https://mcp.wakato.io/mcp

Then type /mcp inside Claude Code and choose to authenticate wakato. The Wakato page opens in your browser.

Cursor and other clients

Any client that supports remote MCP servers with OAuth needs only the URL. In Cursor, add it to .cursor/mcp.json (or ~/.cursor/mcp.json) and sign in when Cursor asks:

{
  "mcpServers": {
    "wakato": { "url": "https://mcp.wakato.io/mcp" }
  }
}

A client that cannot sign in can still use an API key instead — see Cursor and Claude Desktop.

What a connected app can and cannot do

It works inside the spaces you chose with the tools you allowed: contacts, tables, pages, forms, documents, tasks, social drafts, the shop, automations and more. Every tool says whether it only reads or may change or delete something, so the app can ask you before a risky step.

Sending on your behalf — emails, texts, meeting invitations — still goes through Wakato's own approval, which today lives in your Wakato assistant's chat. A connected app is refused those actions with a sentence saying so; send them from Wakato or ask your assistant.

A connected app never sees your password, cannot pay money out, and cannot delete a space or your account.

Build an app that connects to Wakato

To put a Connect Wakato button in your own product, register it in Backstage → Connected apps → Your apps. You get a client ID (and a secret for a server-side app) and the endpoints:

The flow is the authorization-code grant with PKCE (S256, required). Send resource=https://mcp.wakato.io/mcp to ask for the account (the person picks the spaces), or omit it for the same. Access tokens last an hour; refresh tokens rotate on every use, and a refresh token used twice closes the connection. Clients that cannot keep a secret register without one and rely on PKCE; MCP clients may register themselves (RFC 7591) at https://api.wakato.io/functions/v1/oauth/register.

A new app starts Private (you and people in spaces you run), can be opened to everyone as Unverified (up to 100 people, with a warning on the consent page), and becomes Verified after Wakato reviews it.