Build with coding agents
Noodle Seed is built for agentic engineering. Author MCP servers with Codex and Claude Code using project-local agent files, a self-correcting validate loop, and ready-to-paste prompts.
Noodle Seed is designed for agentic engineering. Because a whole MCP server is one declarative
server.ts, a coding agent like Codex or Claude Code can author it end to end, check its own
work with noodle validate, and iterate, all without you writing boilerplate.
Why agents are first-class here
One TypeScript file, typed schemas, and structured compile errors mean an agent has a tight, machine-checkable loop: write, validate, read the error, fix, repeat.
Install the Noodle Seed plugin
Give your agent the Noodle Seed knowledge globally, before any project exists. The plugin ships the
noodle-seed skill, so a bare "build me an MCP app" prompt already reaches for the noodle CLI,
scaffolds with noodle init, and runs the validate loop.
claude plugin marketplace add NoodleSeed-com/plugins
claude plugin install noodle-seed@noodleseedCodex reads the same marketplace:
codex plugin marketplace add NoodleSeed-com/pluginsOnce a project is scaffolded, noodle init installs a fuller project-local skill (see below) and the
plugin defers to it.
The agentic loop
The agent edits server.ts, runs noodle validate, and fixes the specific errors it reports. Repeat
until validation is clean, then run it locally with noodle dev or ship it with noodle deploy.
Project agent files
noodle init writes project-local Codex and Claude Code files so your agent starts with the right
context: the authoring SDK surface, the rules (TypeScript only, no hand-written manifests, secrets via
secret("NAME")), and the validate-repair loop.
noodle init my-server # generates agent files by default
noodle agents setup --write # refresh them later (dry-run without --write)
noodle agents doctor # report whether the installed skills are currentThese files are project-local and non-secret. They never include tokens, credentials, or
~/.noodle/config.json contents.
Connect the agent to your server
Start the dev server, then in another terminal wire your agent (or any MCP client) to the local endpoint:
noodle devnoodle connect claude-codenoodle connect also supports codex, cursor, vscode, gemini, and inspector.
Now the agent can call your tools directly to test them as it builds.
Feed the docs to your agent
Export these docs in an LLM-friendly format to drop into an agent's context:
noodle docs export --format llms --output noodle-docs.txtCopy a prompt
Paste one of these into Codex or Claude Code to get started. Replace the bracketed part with your idea.
Use Noodle Seed in this project.
Install or run the Noodle Seed CLI package `@noodleseed/one`. If this is a new project, run `noodle init`. If this is an existing project, run `noodle setup --write` and `noodle agents setup --write` instead of overwriting unrelated files.
Build a Noodle Seed server for: [describe the ChatGPT app, Claude connector, MCP app, Codex plugin, or Claude Code plugin I want].
Rules:
- Author TypeScript with the `@noodleseed/one` SDK.
- Do not hand-write manifest JSON or YAML.
- Do not hard-code secrets. Use `secret("NAME")` and tell me which `noodle secrets set` commands I need.
- Keep the implementation focused in `server.ts` unless the project already has a Noodle Seed layout.
- After every meaningful change, run `noodle validate` and fix the reported errors until validation passes.
- Then run `noodle dev` for local testing.
- When I approve, run `noodle deploy` and show me the MCP endpoint and the `noodle connect` command for Claude, ChatGPT, Codex, or Claude Code.Add a new tool to my Noodle Seed `server.ts`.
- Use the `@noodleseed/one` SDK; the tool needs a Zod `input`/`output` schema and a `fulfil` function.
- If it needs an external API, add or reuse a `connector(...).http({...})` on the server `use` map.
- Run `noodle validate` and resolve every reported error before you finish.
Tool: [describe the action and its inputs/outputs].Run `noodle validate` on my Noodle Seed project and fix every error it reports.
Work through them one at a time, re-running `noodle validate` after each fix, until it passes.
Do not change unrelated code, and keep everything in `server.ts`.Integrate the Noodle Seed embedded assistant into this existing SaaS application.
Use only the public Noodle CLI, generated project instructions, and `@noodleseed/assistant`. Inspect the
repository's framework, authentication, package manager, local HTTPS support, and server-only environment
conventions before editing. Reuse the existing authenticated user through a backend session-exchange route,
mount the browser SDK only in the authenticated application shell, and keep all model and client credentials
out of browser code. Configure exact HTTPS local and production origins. Run `noodle commands --json` before
proposing flags, then validate and test. Do not deploy or create credentials until I explicitly approve.