AI Prompt Toolkit

MCP Bake Manifest Studio

All tools

Convert recipe steps into a JSON manifest an agent can follow, with every tool URL resolved.

How it works

Four simple steps

1

Pick a starter

Load a ready pack or choose Custom.

2

List the steps

Paste recipe JSON or one tool slug per line.

3

Bake the plan

Slugs are checked and resolved to tool URLs.

4

Download JSON

Save the manifest for your agent or MCP host.

MCP Bake Manifest Studio

About MCP Bake Manifest Studio

You want a coding agent to run the same three-tool routine your team does by hand, but it keeps guessing tool names. A manifest with verified slugs and exact URLs removes the guessing. MCP Bake Manifest Studio produces one.

Start from a starter pack (JSON for API, JWT security pack, PDF plus receipt, Ship prompts safely, or HAR incident) or choose Custom. The input accepts recipe JSON with a steps array, a plain JSON array of slugs or step objects, or one slug per line. Give the manifest a name and click Bake plan. The output is JSON with a schema reference, the type mcp-bake-manifest, a generation timestamp, an ok flag, a missing list and a plan array where each step has its index, slug, label, tool URL and a found flag. An mcpHint block names the matching bake_plan tool.

The ok flag is the check that matters. Any slug not in the live catalog lands in missing and the status line names it, so typos are caught before an agent tries to call a tool that does not exist. If you do not have a plan yet, Recipe Autopilot can draft one from a plain description, and saved recipes in Recipe Studio can be pasted in as JSON. Other agent helpers are on the AI tools hub.

The manifest is assembled from the site's tool catalog in your browser and downloads as mcp-bake-manifest.json. No secrets or files are involved.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

No. It produces the manifest file. The manifest names the bake_plan tool so an agent that has the OneDevToolkit MCP server configured knows which call matches it.

The step is still listed, but its found flag is false, its URL is null, the slug appears in the missing array and ok becomes false. Fix the slug and bake again.

A JSON object with a steps array, a JSON array of strings or step objects with a slug field, or plain text with one slug per line. Blank lines are ignored.

View more FAQs

Related tools

View all

LLM Cost Estimator

Estimate multi-model API cost from tokens or pasted prompts.

Open

RAG Chunk Simulator

Split documents into RAG chunks with overlap, variance heatmaps, and cost estimates.

Open

Chat Messages Studio

Build and convert OpenAI/Anthropic chat message JSON payloads locally.

Open

Prompt Eval Rubric

Score prompt variants against weighted rubrics before spending API credits.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools