Cold CakedcakeMCP

Your AI can send cake now.

Connect Claude, Cursor or any MCP client. Your agent designs a real cake, books a bakery near the recipient and hands you a Stripe link. Drafts are free. Nothing bakes until a human pays.

https://daymaker.com/api/v1/mcp

Streamable HTTP · stateless · no API keyHow to connect

Teams already sending

Two minutes. No API key.

Pick where your agent lives. Every client gets the same endpoint, and nobody asks you to sign in.

01
Open Customize → Connectors.
02
Click +, then Add custom connector, and name it Cold Caked.
03
Paste the endpoint. If Claude asks about Authentication, pick No sign-in.

fill it in like this

Name: Cold Caked
Remote MCP server URL: https://daymaker.com/api/v1/mcp
Authentication: No sign-in

On a Team or Enterprise plan, an owner adds it once in Organization settings.

Open Claude

01
One command in any project.
02
Ask for cake.

terminal

claude mcp add --transport http \
  daymaker https://daymaker.com/api/v1/mcp

01
Turn on Developer mode in Settings → Security and login.
02
Open Plugins, click +, then Create app.
03
Fill it in like the card. Needs a paid ChatGPT plan, on the web.

fill it in like this

Name: Cold Caked
MCP server URL: https://daymaker.com/api/v1/mcp
Authentication: No authentication

Open ChatGPT

01
Point your client's MCP config at the URL.
02
No OAuth, no headers. It just answers.

mcp config

{ "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.

01
The agent designs
Checkout · Stripe
- Draft locked · 8″ round$126
- Link opened byyou, in a browser
- Card seen by agentnever
02
A human pays
03
We bake & hand‑deliver

your agent gets the delivery photo too.

Drafts are free. Nothing is charged while the agent works.
Nothing bakes until a human pays. Checkout is always a Stripe link a person opens.
No tool charges anyone. The agent never holds a card.

Thirty-three 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.

here's the order a cake runs in

before a draft
check_delivery_coverage
Is an address in range, and what do sizes cost there? Real prices, no auth.
get_cake_catalog
Sizes, shapes, fonts, and the print-safe layout rules for designs.
the draft
start_gift
Opens a free draft and mints the private session token. Pass your account token and it opens on your Cold Caked account instead, so the gift shows up in your dashboard.
find_recipient_address
Company website in, verified street address out.
add_recipient
Who gets the cake and where. Instantly told if it's deliverable.
update_recipient
Fix a typo’d address or add the phone number later. Re-routes, keeps the id.
set_gift_design
SVG or image rasterized print-ready, or a message we typeset. Returns fit warnings.
a human pays
create_checkout
Locks the price, returns the Stripe link. A human takes it from there.
Stripe link you
after
get_gift_status
Payment, baking, delivery, and the photo once it lands.

Researched gifts, same connection. Pin your account on the server URL and the gift advisor is a tool too: research a person, pick a gift, buy it. Nothing is bought until a person pays the link.

research_prospect
A name or LinkedIn URL in. Our research reads what they publish and picks one buyable gift per interest, with a live price. A job that takes minutes; metered to your account. The person shows on your Daymaker People screen when you sign in with the same email.
suggest_gift
For someone you already know: their interests in your own words, no research, one gift with a real link. Cheaper and faster.
get_gift_recommendation
Poll a job until the gift is there: the idea, the note, the product link, the verified price.
buy_gift
Quotes the picks for one or more people and returns the Stripe link. We buy and ship; the recipient can type their own address.
get_gift_order_status
Paid, bought, shipped, delivered, per recipient.
list_prospects
Everyone you've researched, with your agent or in Daymaker. Search by name, company or title. Free.
get_prospect
One person in full: what research found and where, the gift and the runners-up, the order. Free.
list_campaigns
Your research campaigns and how many people are in each. Free.

Building a product? There's a REST API too.

MCP is for your agent. The API 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

Compare	cakeMCP	REST API
Credential	Per-gift token, anonymous	Durable `dm_live_…` key
Account	A fresh one every gift	Yours, plus a sub-account per end user
Retry safety	None needed: a human is in the loop	`Idempotency-Key`
Payment	A person pays a Stripe link	Saved card, prepaid balance, or a link

Fair questions.

More on how sends work: how it works the coverage map why physical converts

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 Cold Caked account and want the cakes your agent orders to land in your dashboard next to the ones you ordered yourself, 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.

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 to $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, ChatGPT (paid plans, with Developer mode on), 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? Start a campaign