Introduction
Noodle Seed is the platform to build, host, and ship MCP servers and apps. Author one server.ts in TypeScript and a governed multi-tenant runtime serves it across every AI assistant.
Noodle Seed lets you build a Model Context Protocol (MCP) server the same way you write
application code: you author one server.ts in TypeScript, and a shared, governed runtime hosts it
and serves it to any MCP client, including Claude, ChatGPT, Codex, Claude Code, and the MCP
Inspector.
You describe what your server exposes (tools, resources, prompts, and optional UI widgets), and Noodle Seed handles the how: the protocol wire, schema validation, connector execution, credentials, and multi-tenant hosting.
Alpha
Noodle Seed is in active development. This documentation marks capabilities as Shipped, Partial, or Roadmap so you always know what you can rely on today.
The idea: thin language, fat runtime
A traditional MCP server bundles the same machinery into every project: a protocol server, auth, HTTP clients, retries, validation. Noodle Seed moves that machinery into a runtime that is built once and shared, so your server stays small and declarative.
Your server is data
One server.ts compiled to a small, portable description of your tools, resources, prompts, and
connector references. It says what to expose, not how to serve it.
The runtime is a shared engine
A stateless, multi-tenant runtime that speaks MCP, validates every call, runs your connectors, brokers credentials, and applies policy. The same engine serves every server.
Because the heavy lifting lives in one place, a single runtime serves many servers, your server diffs and reviews like data, and every connector or capability the platform gains becomes available to your app.
What you can build
Tools
Typed actions the model can call, with Zod input/output schemas and a fulfil function.
Resources & prompts
Readable context at fixed or templated URIs, and reusable prompt templates.
Apps & widgets
React UI rendered inside the host as an MCP App, linked to your tools.
Connectors
Reach real HTTP APIs or run sandboxed logic, declared as data with brokered credentials.
How you work
Author a server.ts with the @noodleseed/one SDK in Claude Code, Codex, or your editor.
Run it locally with noodle dev, a loopback MCP server with hot reload and no account required.
Deploy with noodle deploy to get a governed, identity-gated MCP URL that works across assistants.
Start here
Quickstart with Claude Code or Codex
Paste one prompt into your terminal agent, then validate and run locally.
Build with coding agents
Use the validate-repair loop, project-local agent files, and ready prompts.
Manual CLI reference
Every noodle command, generated from the CLI source.
Core concepts
How authoring, compilation, the runtime, tenancy, and connectors fit together.