Production MCP infrastructure for software and SaaS teams

Software isn't dead. It's going headless.

Build, host, and ship MCP servers, plugins, and connectors without rebuilding the platform underneath them. OAuth, policy, secrets, audit, rate limits, observability, and agent distribution are built in.

npm install -g @noodleseed/one@latest

brightdesk · agent · 80×24agent workflow

Replay in

›

Build with your coding agent

Paste the full Noodle Seed workflow into Claude Code or Codex.

Noodle Seed, Product of the Day, 1st, on Product Hunt

Awarded on Product Hunt, and the #1 developer in the ChatGPT app directory

One platform powering more ChatGPT apps than any other company

Real businesses, live in agents right now

Production MCP infrastructure

The platform underneath every MCP server is already built.

Your team defines the product capabilities. Noodle Seed operates the infrastructure every serious MCP server needs: identity, OAuth, credential brokering, policy, rate limits, audit, secrets, variables, observability, hosting, and protocol compatibility.

Author

Tools, data, workflows, and interfaces in TypeScript.

Compile

A validated, portable artifact the runtime can serve.

Operate

Identity, policy, secrets, audit, scaling, and observability.

Distribute

One governed endpoint for every MCP-speaking client.

server.ts

1import { asset, server, tool, z } from '@noodleseed/one';
2
3export default server('brightdesk', {
4  title: 'Brightdesk',
5  version: '1.0.0',
6  branding: { logo: asset('./assets/logo.png') },
7}, [
8  tool('ticket_status', {
9    description: 'Look up a support ticket and show a status card.',
10    input: z.object({ ticketId: z.string() }),
11    output: z.object({ status: z.string() }),
12    fulfil: () => ({ status: 'resolved' }),
13    view: { component: 'TicketStatus', entry: './views/TicketStatus.tsx' },
14  }),
15]);

Infrastructure included with every deployment

MCP protocol & spec driftwire handling, sessions, version negotiation
runtime
Auth + OAuth 2.0 + DCR + PKCEsign-in, consent, token verification
runtime
Hosting, scaling, TLSmulti-tenant stateless runtime, no cold-start config
runtime
Widget runtime & sandboxingrendering, data binding, CSP, host theming
runtime
Policy, audit, rate limitsadmission, safe events, abuse controls, rollback proof
runtime
Credential brokeringdownstream tokens scoped at connector-call time
runtime
Secrets & variablesmanaged config without leaking values into artifacts
runtime
Logs & observabilitytenant-safe operational signals without request bodies
runtime

How it works

Define the product. Noodle Seed operates the infrastructure.

You describe the experience in TypeScript. The runtime validates it, deploys it, operates it, and keeps the endpoint governed as clients and protocol versions change.

Define the product surface

Describe the tools, resources, prompts, widgets, connectors, and customer actions your software exposes.

Deploy and operate

noodle deploy ships a stable tenant URL with auth, credential brokering, secrets, variables, audit, logs, rate limits, and policy managed by the runtime.

Distribute with control

The same governed endpoint reaches ChatGPT, Claude, Gemini, coding agents, and every MCP client without a separate platform per surface.

brightdesk · zsh

›

Get started

Start inside Claude Code or Codex.

Install the Noodle Seed plugin in Claude Code or Codex and your agent knows the whole workflow from the first prompt: scaffold, author, validate, and run a local MCP server before creating an account. Deploy only when you approve.

claude plugin marketplace add NoodleSeed-com/plugins && claude plugin install noodle-seed@noodleseed

Codex: codex plugin marketplace add NoodleSeed-com/plugins

1Install the Noodle Seed plugin in your coding agent
2Tell it what to build
3Let the agent validate, run, and deploy

No plugin? Install the CLI directly and paste the agent prompt instead:

npm install -g @noodleseed/one@latest

Starter intents

Create a ChatGPT app for my support workflowCreate a Claude connector for my SaaSCreate an MCP app with a small UICreate a Codex or Claude Code plugin for this repo

Plugins & connectors

One project. Every agent surface.

Package repeatable capabilities for coding agents as plugins, and expose governed tools and data to assistants as connectors and apps. Every surface runs through the same MCP endpoint and operating model.

Plugins & connectors

Ship Codex and Claude Code plugins alongside Claude, Gemini, Copilot, and Perplexity connectors without building a separate deployment or governance layer for each one.

Codexplugin

Claude Codeplugin

Claudeconnector

ChatGPTapp

Geminiconnector

Microsoft Copilotconnector

Perplexityconnector

and every MCP client

Just-in-time interfaces

Headless, not faceless. An MCP App shows a screen only when a task needs one.

No permanent shell. Widgets appear exactly when a task needs them, declared in TypeScript and rendered by the runtime: data-bound, action-bound, themed to the host, and able to hold typed state.

Permanent dashboardCapabilities agents call

Screen for everythingInterface only when needed

ui://case_card

MCP App

Case #4821

M. Okafor · premier

In review

Card dispute

Disputed · 2026-06-08

$482.16

Brightdesk cases: a contact-center app with cases, policies, and operator prompts.

ui://order_form

MCP App

Account action

Brightdesk · customer tenant

Scoped

APIExtend trialrequires support:write

14d

Usage limit

Brightdesk admin: scoped customer actions with data-bound forms and confirmation cards.

ui://tour

MCP App

Widget capabilities

Declared in TypeScript, enforced by the runtime

Data bindingBound
Tool actionsConsented
Credential field••••••

Widget Capabilities: binding, actions, and redaction in one view.

Solutions

Infrastructure for software that needs to be callable.

Software and developer-tool teams lead the platform, with the same governed infrastructure supporting marketplaces, internal systems, commerce, travel, hospitality, and agency portfolios. A Codex or Claude Code plugin is an MCP server, built and operated through the same platform.

Software and developer tools

Turn product APIs, admin workflows, docs, and customer actions into a Codex plugin, Claude Code plugin, ChatGPT app, and Claude connector without rebuilding governance per surface.

Learn more

Pricing

Production economics without the platform tax.

Start free, then pay for the pooled hosted footprint, usage, and operational control your team runs. Paid tiers are priced per billing account, never per seat.

Free

1M MCP calls each month plus 1 production app for personal projects, prototypes, and public or owner-only servers.

Pro

$30/month

10M calls and 5 production apps for teams and early customer workflows.

ScalePopular

$300/month

100M calls and 25 production apps with higher limits and operational controls.

Enterprise

Custom

Contract-defined governance, connectivity, deployment, security, and support scope.

These are our published plan terms. Paid activation is manual during beta. Self-service billing-account checkout, paid-plan admission, and automatic overage invoicing are still being built. Pooled Free limits and operator suspensions remain active.

Compare plans and limits

Why now

Default status is being assigned right now.

Assistants reuse the tool that already works. The first reliable product available for a task tends to become the default, so showing up later means replacing an established workflow rather than filling an empty one. What stays unreachable eventually becomes irrelevant.

Community

Going headless is better together.

Join builders shipping MCP servers, connectors, and agent-ready products. Share what you are operating, get help with the platform, and help shape what comes next.

Join the Discord

// founding members welcome

The head dies. The body lives.

Operate the MCP infrastructure your product actually needs.

Start locally without an account. Deploy when you are ready, with identity, governance, observability, hosting, and distribution already in place.

Install CLI