Ship your tool as a Codex and Claude plugin from one TypeScript project.
Developers live inside coding agents now, not your standalone UI. Author your capabilities once as a declarative MCP server and Noodle Seed serves them headless into the agents your users already drive, so your product is one prompt away from the work.
01Meet developers inside their agent
The IDE tab is the old head. The new surface is the coding agent: Codex, Claude Code, and every MCP-speaking client. A headless tool shows up where developers are already typing, with no context switch.
02One authoring surface, every client
Author tools, resources, and prompts once in TypeScript. The same governed server is served as a Codex plugin and a Claude Code plugin, so you are not hand-maintaining a separate integration per client.
03Governed, not a loose local script
Identity, scoped access, secrets brokering, rate limits, and audit come from the runtime. Your plugin is something a team can adopt and IT can reason about, not an unmanaged token in a config file.
What appears after the first workflow works.
Noodle Seed compiles your TypeScript project to the data the runtime serves, then hosts it with OAuth, policy, secrets, and audit, so the same capability reaches every agent client without a bespoke build per surface.
Review the production pathEvery shipped pattern and open example runs on the same runtime your plugin would use. See the apps
Coding agents are becoming the default developer surface. The tools that are reachable inside them now are the ones developers reach for by reflex later. A tool that is not agent-callable is a tab nobody opens.