START
Connect an assistant
Wittle Scheduling Tool is a remote MCP server. Any assistant that supports custom MCP connectors can use it.
Connector address
https://scheduling.wittlelabs.ai/mcp- Transport: Streamable HTTP, stateless, JSON responses. Every MCP message is a
POST. - No session to keep: each call stands alone.
Adding it
| Assistant | Where | Notes |
|---|---|---|
| Claude | Settings → Connectors → Add custom connector | Works on web, desktop and mobile apps. |
| ChatGPT | Settings → Connectors → custom connector (Developer mode) | Custom connectors work on the web; mobile apps support listed plugins only. |
| Muse | Ask Muse to add a custom connector and give it the address | Web, iOS, Android and WhatsApp. |
| Other MCP clients | Wherever the client adds a remote (HTTP) MCP server | OAuth 2.1 with discovery, described below. |
Sign-in: only to book
Looking around needs no account. search_providers, get_provider_details and get_availability work anonymously. The first call to prepare_booking, confirm_booking or get_booking_status without a token gets an HTTP 401 challenge, and the assistant starts sign-in (email code or Google, no password). The account keeps a person’s bookings private to them and protects businesses from fake bookings.
If “Connect” or sign-in does nothing, the browser probably blocked the sign-in pop-up. Allow pop-ups for the assistant’s site, or connect from the assistant’s mobile app.
For MCP client developers
- Authorization follows the MCP authorization spec (OAuth 2.1 + PKCE). The
401carriesWWW-Authenticate: Bearer resource_metadata=…. - Protected resource metadata (RFC 9728):
https://scheduling.wittlelabs.ai/.well-known/oauth-protected-resource/mcp, which names the authorization server. Authorization server metadata is also served on our origin for older clients. - Client registration: Client ID Metadata Documents or Dynamic Client Registration.
- Resource indicator (RFC 8707):
https://scheduling.wittlelabs.ai/mcp. Tokens for any other audience are rejected. Scopes:openid email profile.
Tips for assistants
- Pass the customer’s own description of the problem as
need; don’t guess a trade. - Always show the
prepare_bookingsummary and get a clear yes before confirming. - Every tool accepts an optional
intent: one short sentence about what the customer is trying to do, with no names, phone numbers, emails or addresses. It helps us see what people need. - If no participating business covers the request, carry on helping with your own search, but don’t present those results as Wittle businesses.
Next: the tools reference.