Model Context Protocol
Model Context Protocol and the WhatsDo connector
Model Context Protocol is how an assistant reaches an outside system. WhatsDo has no public MCP connector yet. This page states what exists today and what is still being built.
What Model Context Protocol is
Model Context Protocol is an open standard for connecting an assistant to an outside system. The server declares what it can do, the assistant reads that and calls it. On its own it grants access to nothing.
- 01An MCP server declares its actions, inputs and outputs in a machine-readable form.
- 02The assistant reads that declaration and decides which action fits the request.
- 03The server holds the credentials for the system behind it, not the assistant.
- 04What can actually be booked comes from the connections behind the server, never from the protocol.
Where the WhatsDo connector stands
The WhatsDo MCP connector is being finished. There is no public endpoint, no install link inside ChatGPT or Claude, and no listing in an assistant directory. We publish status, not timelines.
WhatsDo API, closed beta
Credentials and the endpoint contract are issued per developer on request.
WhatsDo MCP connector
No public endpoint. No date is published.
Install link in ChatGPT or Claude
No listing exists in any assistant directory.
What is available today
Booking access exists now through the WhatsDo API during the closed beta. Testing runs against a merchant we control, so nothing is written to a real customer business while you build.
- 01Request access with your use case, target vertical and expected volume.
- 02Receive credentials, base URL, auth scheme and the supported action list.
- 03Read verified availability with service, duration, price, currency and timezone. This is live today.
- 04Write a booking in closed beta against a controlled merchant, returning a stable identifier intended to match the provider record.
The transport changes, the contract does not
A connector would be another way to reach the same actions. The rules behind a booking, and the places where a capability stops, are the same on any transport.
- 01A write requires one explicit confirmation of service, time, timezone, price and currency.
- 02Repeating the same request returns the existing booking and creates no duplicate.
- 03Cancellation and reschedule are not available through the agent path.
- 04Agent-initiated payment is not available through the agent path.
- 05Square Appointments is the supported backend today and the booking write is in closed beta.
If you are building on MCP
Tell us which assistant surface you build for and what your users ask for. That input shapes the action list a connector would expose, and it puts you on the list we notify when the status changes.
- 01Request API access and run your first calls against a controlled merchant.
- 02Name the assistant surface you target and the actions your users ask for.
- 03We report status changes as they happen, without promising a date.
Questions we get
Is there a public WhatsDo MCP server I can install today?+
No. The connector is in development and no public install path exists in ChatGPT, Claude or any assistant directory. API access during the closed beta is granted per developer.
Can an agent book from Claude or ChatGPT right now?+
Not through a WhatsDo install link, because none is published. An agent you build yourself can read availability today, and create a booking through the API on the closed-beta write.
When will the MCP connector be available?+
No date is published. We state where a capability stands rather than when it lands, and we report changes to the developers who registered interest.
Do I need MCP to use WhatsDo?+
No. The API is the path today. MCP is a transport, so the booking contract, the supported actions and the backend coverage are the same either way.
Which booking systems would a connector reach?+
The same ones the API reaches. Square Appointments is supported today. Coverage comes from the connections behind WhatsDo, and the protocol adds none of its own.
Build against the API that exists today.
Your first calls run against a controlled merchant, never a live business.
Run a business? Start here