Connect.

In plain terms: two of these are the versions a marketplace lists (the ChatGPT app and the Claude directory listing), and one is the connector you add yourself. If you just want to schedule things, any of them does that. If you also want to manage your subscription or account from your assistant, add the self-add connector — that's the only one with those tools.

• Fullhttps://mcp.booqit.online/api/mcp

  Everything — all 68 tools: polls, booking pages, events, plus subscription, checkout, and account management. The connector you add yourself.

• ChatGPT apphttps://mcp-chatgpt.booqit.online/api/mcp

  Scheduling and events (33 tools): polls, booking pages, slots, bookings, events. No billing, account, or admin tools, per OpenAI's app rules. This is what a Booqit app listed in ChatGPT would use.

• Claude directoryhttps://mcp-claude.booqit.online/api/mcp

  Its own allowlist (33 tools): the same scheduling and events set as the ChatGPT profile — polls, booking pages, slots, bookings, events. No billing, account, or admin tools. What a Booqit listing in Anthropic's connector directory would use.

The short version: marketplace listings are restricted; the self-add connector isn't. If you want more than scheduling — managing your subscription, checkout, your account — add the custom connector (mcp.booqit.online), not the marketplace app.

Availability, honestly:the self-add connector and its OAuth flow work today. The ChatGPT and Claude marketplace listings are not live yet — their endpoints are up and you can point a client at them, but you won't find Booqit in either catalog for now.

All three endpoints authenticate the same two ways: OAuth (authorize as yourself; assistants use this) or an API key (Authorization: Bearer ak_...; your own code uses this). Reads on public resources — a poll by id, a booking page's open slots — work without either.

1. Turn on developer mode: Settings → Apps & Connectors → Advanced settings → Developer mode.
2. Create a connector and paste https://mcp.booqit.online/api/mcp. ChatGPT discovers the OAuth configuration itself.
3. Approve the authorization in the browser window that opens — sign in to Booqit (or create an account there and then), review the consent screen, done.
4. Back in the chat, mention what you want: “ask the team whether Tuesday or Thursday works.” The connector may need to be enabled per-conversation depending on your ChatGPT plan.

1. Settings → Connectors → Add custom connector.
2. Name it Booqit, paste https://mcp.booqit.online/api/mcp, and add.
3. Claude walks you through the same authorize-in-browser step.
4. The tools show up in your chats; enable the connector where you want it available.

Two options, depending on whose behalf the client acts:

On a user's behalf — OAuth. Point your client at the endpoint with no credentials. The 401 response carries a WWW-Authenticate header pointing at our protected-resource metadata (RFC 9728); authorization-server metadata (RFC 8414) is at /.well-known/oauth-authorization-server. Register dynamically, use PKCE with S256 — plain is refused — and request the booqit scope, or narrow to granular ones. Any MCP client that implements the standard authorization flow needs zero Booqit-specific configuration.

Each of the three endpoints is its own protected resource and names itself in its protected-resource metadata, so the resource your client binds its token to is the endpoint you actually connected to. All three share one authorization server, named in that document's authorization_servers — so one account, one consent, one set of credentials across every endpoint. Follow that field rather than assuming the authorization server lives on the host you connected to.

On your own behalf — API key. Mint a key in the keys dashboard and send it as a bearer token:

{
  "mcpServers": {
    "booqit": {
      "type": "http",
      "url": "https://mcp.booqit.online/api/mcp",
      "headers": { "Authorization": "Bearer ak_your_secret_here" }
    }
  }
}

Scopes on the key gate tools exactly as OAuth scopes do — see Scopes & rotation.

Payment never happens inside a conversation. When a tool involves paying — starting a subscription, a one-time checkout — Booqit returns a hosted Stripe link and the browser takes it from there. No card details in chat, ever, on any endpoint.