Sposai speaks MCP — the same open protocol Claude Code and Claude Desktop use. Mint a token, paste a config, and drive your guest list, seating chart, and run sheet from the AI surface you already live in.
Because the AI you already trust — the one you use to draft emails and review code — should be allowed to help with the biggest project on your plate.
Claude Code today; Claude Desktop, ChatGPT with MCP, or your own scripts — anything that speaks the protocol. One token, every client.
The exact catalogue the in-app Sposai chat uses. Query guests, update RSVPs, draft run sheets, move tables, fix data health. No read-only downgrade.
Writes always preview first and wait for your explicit yes. Scoped tokens let you pick read-only or read-write. Revoke any token instantly from your dashboard.
When you mint a token, pick which weddings it can act on — every wedding you're a member of, a single client, or any subset. Add a new wedding to your roster later and it automatically inherits your token's access. Switch weddings mid-conversation (coming soon) — until then, mint a per-wedding token if you need to focus.
Mint a multi-wedding tokenAbout 90 seconds, end-to-end. You'll need Claude Code or another MCP-compatible client already installed.
Visit /dashboard/settings/integrations in Sposai and click Add to Claude Code. We'll mint a fresh token named after your device — no form, no scope picker, no expiration dropdown. (Want fine-grained control? Use the Advanced disclosure to mint a raw token instead.)
The connect modal shows a single line you copy into your shell. No .mcp.json, no local checkout, no DATABASE_URL — Sposai hosts the MCP endpoint and you authenticate with the bearer token. Looks like this, with your real token in place of the placeholder:
claude mcp add --transport http sposai https://sposai.com/api/mcp --header 'Authorization: Bearer tok_paste_your_token_here'Restart Claude Code. Type /mcp — you should see sposai connected with 37 tools. Then ask Claude: "How many guests have RSVP'd?" — it calls queryGuests and answers from your real data.
Claude Desktop's native Add Integration UI speaks OAuth 2.1 with PKCE. Pick Sposai from the connectors list, sign in once, click Allow, and you're connected — no command to copy, no token to paste. The Sposai server handles consent, scope, and revocation through standard OAuth endpoints (RFC 7591 DCR and CIMD client_ids both supported).
Once connected, your Sposai dashboard's Devices panel shows the Claude Desktop entry with an OAuth badge and one-click revoke.
If you're already a Sposai customer, mint a token and you're minutes from chatting with your wedding from any MCP client. New here? Start a wedding first, then come back.