Connect Doodle to Claude Code

Coordinate scheduling with Claude despite Doodle's API limits. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Doodle to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Doodle, you add a Doodle MCP server: a small hosted service that exposes Doodle's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Doodle account. No API keys pasted into config files.

claude mcp add --transport http doodle https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Doodle once connected?

If your account has grandfathered Doodle Enterprise API access, a custom connector can let Claude work against the endpoints your account already permits, with each action gated by your approval. For everyone else, Doodle no longer issues new API access, so we typically build the connector against an API-available alternative such as Microsoft Bookings or SavvyCal, where Claude can create and manage bookings end to end.

Confirm with Doodle support whether your account has grandfathered Enterprise API access
Map the scheduling coordination you want into endpoints your account already permits
Build the same workflow against an API-available alternative like Microsoft Bookings or SavvyCal
Draft a group poll's time options and meeting details for you to set up in the Doodle dashboard
Surface a poll's responses from data you export, then highlight the times that work for everyone
Prepare a booking-page summary you can paste or share manually

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Doodle access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Doodle API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Doodle changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Doodle connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Doodle connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Doodle account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Doodle's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Doodle?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Doodle account it signs in with. Revoking access is one click in Doodle.

More on the Doodle connector

Doodle connector for claude.ai Microsoft Bookings + Claude Code SavvyCal + Claude Code Chili Piper + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us