Docs.

Using the Booqit app (marketplace)

Once Booqit lands in the ChatGPT app directory and the Claude connector directory, you add it the way you add any other app: open your assistant's app or connector gallery, search for Booqit, enable it, and authorize with your Booqit account (or create one in the same step). The app brings the scheduling and events tools with it: polls, booking pages, open slots, bookings, and events.

The directory listings aren't live yet. Until they are, add the connector yourself (next) and you get every tool today, including subscription, checkout, and account management.

Want all the tools now? Add the custom connector.

You don't have to wait for a directory listing. Add the full custom connector at:

https://mcp.booqit.online/api/mcp

This self-add endpoint carries the complete tool set — the scheduling tools plus subscription, checkout, and account management — and it works today. In ChatGPT, add it as a developer-mode connector; in Claude, add it as a custom connector; in any other MCP client, point the client at the URL. The step-by-step for each client is right below. For the difference between this endpoint and the narrower marketplace one, see Connect →.

Using an assistant? Connect it. (OAuth)

If you want Booqit inside ChatGPT, Claude, or any MCP client that speaks OAuth, you don't need an API key. You add the endpoint and authorize with your Booqit account.

1. Add the endpoint. The full connector lives at:

   https://mcp.booqit.online/api/mcp

   • ChatGPT— turn on developer mode (Settings → Apps & Connectors → Advanced settings), then create a connector with that URL.
   • Claude — Settings → Connectors → Add custom connector, paste the URL.
   • Any other MCP client — point it at the URL; Booqit publishes standard OAuth discovery metadata (/.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server), registers clients dynamically, and requires PKCE (S256). No pre-registration, no client secret to request from us.
2. Authorize. Your browser opens once: sign in (or create an account on the spot), review the consent screen, approve. Connectors typically request the coarse booqit scope, which covers all operations; a client can narrow to granular scopes (polls:read, polls:write, pages:read, pages:write, bookings:write) instead.
3. That's it.The tools appear in your assistant and you talk in plain words — “find a time for the team next week” becomes a poll. Which tools you see depends on which endpoint you added; see Connect → for the three endpoints and why the self-add one is the full set.

One boundary worth knowing: anything involving payment hands you a hosted Stripe checkout link in the browser. Card details never pass through the chat.

Building your own thing? Use a key.

For a server, a backend job, or an agent you run yourself, an API key is the right credential — no browser hop, no per-user consent.

1. Create an API key. Open the keys dashboard, create a key, and copy the secret. It's shown once — we store only a hash, so if you lose it you rotate the key rather than recover it. Keep it server-side; never ship it in client code or commit it.
2. Point your MCP client at the endpoint. Authenticate with the key as a bearer token:

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

3. Call a tool. The endpoint speaks JSON-RPC 2.0 over a single POST and exposes every operation below as an MCP tool. A raw tools/call for create_poll with curl:

   curl -X POST https://mcp.booqit.online/api/mcp \
     -H "Authorization: Bearer $BOOQIT_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "create_poll",
         "arguments": {
           "title": "Team sync",
           "options": [
             { "start": "2026-07-10T09:00:00Z", "end": "2026-07-10T09:30:00Z" },
             { "start": "2026-07-10T14:00:00Z", "end": "2026-07-10T14:30:00Z" }
           ]
         }
       }
     }'

   The response carries a text content block plus a structuredContentobject with the new poll's id and secret adminKey (returned once, to the creator only). Discover the tool set at any time with a tools/list request.

Both paths hit the same operation registry — OAuth for assistants, keys for your own code. Neither is a second-class door.

These are the operations the endpoint exposes — the same set backs the REST routes, so the two can't drift. Each lists the scope a key must hold; ops marked subscription require an active subscription on the calling account.

Every tool is also reachable as a plain REST route under /api, authenticated with the same bearer key. Creating a poll over REST is a direct POST — the request body is the tool's arguments, and the response is its result:

curl -X POST https://booqit.online/api/polls \
  -H "Authorization: Bearer $BOOQIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Team sync",
    "options": [
      { "start": "2026-07-10T09:00:00Z", "end": "2026-07-10T09:30:00Z" },
      { "start": "2026-07-10T14:00:00Z", "end": "2026-07-10T14:30:00Z" }
    ]
  }'

A booking page's open slots are a public read — list them by slug without a key:

curl https://booqit.online/api/bookings/pages/$SLUG/slots

Keys carry scopes; each tool above names the scopes it needs. Mint narrow keys for servers that only read (polls:read, pages:read) and separate keys that can write (polls:write, pages:write, bookings:write). A dashboard-issued key can also manage other keys (keys:write). Rotate a key to issue a replacement while the old one keeps working through a short grace window, then revoke the old one once your services have switched over.

Keys and OAuth grants use the same scope names. A tool that needs polls:write needs it whether the caller is your server with a key or an assistant a user authorized.