Your AI can send cake now.

https://daymaker.com/api/v1/mcp
how to connect

teams already sending

Deel Marketer.com Rippling PostHog virio KPMG Staffer
how to connect

Two minutes. No API key.

Claude web · desktop

  1. 01Open Settings → Connectors
  2. 02Click Add custom connector, name it Daymaker
  3. 03Paste the endpoint. That's the whole setup.
# the endpoint https://daymaker.com/api/v1/mcp

Claude Code terminal

  1. 01One command in any project
  2. 02Ask for cake
claude mcp add --transport http \ daymaker https://daymaker.com/api/v1/mcp

Any MCP client Cursor · API · yours

  1. 01Point your client's MCP config at the URL
  2. 02No OAuth, no headers. It just answers
{ "mcpServers": { "daymaker": { "url": "https://daymaker.com/api/v1/mcp" } } }
Streamable HTTP · stateless · no auth
then open a chat and say something like

Our biggest customer just renewed. Design a thank-you cake for their office. Show me the art and the price, then give me the checkout link.

Prompt in. Cake out.

Three coldcakes printed with the Browserbase logo, edible ink on strawberry frosting
01 The agent designs
Checkout · Stripe
✓ Draft locked · 8″ round $126
✓ Link opened by you, in a browser
✓ Card seen by agent never
02 A human pays
Boxed coldcakes coming out of a car on a San Francisco street, on the way to be hand-delivered
03 We bake & hand-deliver

your agent gets the delivery photo too.

the toolbox

Sixteen tools. The whole loop.

Everything a human does in our checkout, your agent does over MCP. From "can we even deliver there?" to the delivery photo.

check_delivery_coverageIs an address in range, and what do sizes cost there? Real prices, no auth.
get_cake_catalogSizes, shapes, fonts, and the print-safe layout rules for designs.
start_giftOpens a free draft and mints the private session token. Pass your account token and it opens on your Daymaker account instead, so the gift shows up in your dashboard.
find_recipient_addressCompany website in, verified street address out.
add_recipientWho gets the cake and where. Instantly told if it's deliverable.
update_recipientFix a typo’d address or add the phone number later. Re-routes, keeps the id.
set_gift_designSVG or image rasterized print-ready, or a message we typeset. Returns fit warnings.
create_checkoutLocks the price, returns the Stripe link. A human takes it from there.
get_gift_statusPayment, baking, delivery, and the photo once it lands.
building a product?

There's a REST API too.

MCP is for your agent. This is for your backend — one call that routes, renders and checks out, a durable key, an account per end user, and retries that can't send a second cake.

Read the API docs
questions

Fair questions.

Do I need an account or an API key?
Not for MCP. The server is public and drafting is free. The only credential is a private per-gift token your agent receives when it opens a draft. It keeps that for the session and passes it to each tool. Payment happens on a Stripe page in your browser, not through the agent. If you already have a Daymaker account and want the cakes your agent orders to land in your dashboard next to the ones you ordered on the site, link it: your dashboard's Connect AI page gives you a server URL with your account on it, and gifts opened through that URL belong to you. Without it an agent's gift is a standalone order with its own tracking link. If you're building cake-sending into your own product, that's the other surface — the REST API uses a durable key so sends roll up to an account instead of a throwaway session, and you create that key yourself on the same Connect AI page.
What's the difference between the MCP server and the API?
Who's calling. MCP is for an agent talking to us directly — conversational, self-describing, nothing to sign up for. The REST API is for a backend: durable keys, an account per end user so you can bill your platform or theirs, and an Idempotency-Key so a timed-out retry can't send a second cake. Same bakeries, same loop, same code underneath — see the API docs.
Can the agent spend my money?
It can't. Checkout is always a Stripe link a person opens and pays. The agent never holds a card, and there's no tool that charges anyone. Automations are created paused and default to a human-approved pay link per cake; auto-charge exists only if you set it up on the dashboard with a spend cap.
What does a cake cost?
Standard cakes start around $80–$100, hand-delivery included. Exact prices depend on size and delivery area. check_delivery_coverage returns real numbers for the recipient's address before anything is drafted, so the agent can quote you up front.
Where can it deliver?
Metros like San Francisco, New York, and Los Angeles, with new cities added every month. See the live coverage map, or skip the map and let the agent check any address in one call.
Which AI clients work?
Anything that speaks MCP over Streamable HTTP: Claude on web and desktop, Claude Code, Cursor, and agents you build on the Claude API. The server is stateless JSON. No OAuth dance, no session juggling.
What actually shows up at the door?
A fresh cake from a partner bakery near the recipient (Cocola, Sweet Lady Jane, Lady Wong, Roland's), with the design printed edible on top, walked in by a courier. The delivery photo comes back through get_gift_status.

Your agent already knows who deserves cake.

The customer that renewed this morning. The engineer who shipped last night. Paste the endpoint, and the next time your team says "we should celebrate this", it actually happens.

https://daymaker.com/api/v1/mcp
prefer buttons to prompts? Create a Campaign
Slack message from a recipient: Thank you for the cake! It was delicious!

More on how sends work

New here? See how a Daymaker send works beat by beat, check the delivery coverage map, read why physical converts, connect your HR stack with our integrations, or if you're putting cake-sending inside your own product, take the REST API.