Start a plan from a conversation.

The endpoint

create_meal_plan starts a plan and returns a job id and a status link immediately. Writing it takes about fifteen minutes, so an assistant should finish its turn and call get_meal_plan later rather than wait.

A plan can cook for a household of up to 4: pass people instead of the per-person fields and everybody gets their own copy, sized to them, from one dish per meal. Somebody with no training week of their own is planned as easy days rather than refused — so a partner you know nothing about still gets fed.

When the plan is ready, get_meal_plan also returns a plan_url — the same plan as JSON, at /j/<job_id>/plan.json. An assistant that fetches it can answer what is for dinner on Thursday without asking anyone to open the PDF.

revise_meal_plan changes one thing about a plan that has already been written — a meal that should not have been dropped, a day the athlete is no longer travelling — without generating a fresh week. It starts a new plan at a new link and leaves the original working; when it is ready, get_meal_plan says what moved, including the shopping list, so somebody who has already shopped can be told what else to buy. Only plans your own key started can be revised: a revision is written from what the athlete gave at intake, which the plan document does not carry. Any plan can still be read with get_meal_plan.

Get a key

No account, no email, no waiting. The key is how your plans are kept separate from everybody else's in the queue; it is not a payment and there is nothing to enter.

Connect it

Claude Code, Cursor, VS Code — one command, with your key in the header:

claude mcp add --transport http fuelweek https://fuelweek.app/mcp \
  --header "Authorization: Bearer <your key>"

Cursor and VS Code take the same three things in their own MCP settings: the URL, the transport, and that header.

Claude and Gemini in the browser — paste https://fuelweek.app/mcp into their connector settings and press Approve on the page that opens. Nothing to copy, no account, no email.

In Claude: Settings → Connectors → Add custom connector. In Gemini: Settings → Connected apps → Add a custom app. ChatGPT takes a custom connector too, with developer mode on, though we have not yet tried this endpoint there.

What to tell it

Describe your week the way you would to a training partner. That is the input this is best at, and the one you have already given your assistant:

“Tuesday 90 minutes on the bike with threshold work, Thursday two hours endurance, Saturday three hours with race efforts, Sunday a long run. 70.3 in three weeks. I'm 72 kg and I shop in Portugal.”

You can pass a TrainingPeaks calendar link instead. Think before you do: that link is a password to your entire training history, it does not expire, and putting it in a chat leaves it in that conversation's record for good. We use it once and never store it — but we cannot reach into your assistant's history. Describing the week avoids the question entirely.

What to expect

• Plans are written one at a time on a single machine, so about fifteen minutes each — and longer if somebody is ahead of you.
• One key may have 10 plans waiting at once. Finished ones give the slot back.
• Plans and their links are deleted after 7 days. The link is the only way back to one, so keep it.
• It's early access and free, for the same reason it is slow: one machine. Whether it becomes a proper service depends on how much it gets used.