Skip to content
Conduit

mcp server

noodle-core

Apache-2.0 Noodle Core: TypeScript authoring, runtime, and single-node self-hosted beta.

NoodleSeed-com/noodle-corecommunitylistedunreviewed
Use tool

Set up

Runs on your computer. Pick your agent and operating system.

Before you start

  • Node.js 20 or newer
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "noodleseed-com-noodle-core": {
      "command": "npx",
      "args": [
        "-y",
        "@noodleseed/one"
      ]
    }
  }
}

same format Cursor, GitHub Copilot CLI, Junie, JetBrains AI Assistant, Augment (Auggie CLI), Factory Droid, Kiro, Devin CLI +12

Values in angle brackets are placeholders. Restart Claude Desktop after editing its config.Claude Desktop docs

README

synced Oct 14, 2026

Noodle Core

CI

Noodle Core is the Apache-2.0 TypeScript authoring SDK, compiler, runtime, CLI, and self-host service behind Noodle Seed. This repository is a single-node, single-operator beta that you can run locally without a Noodle Seed account or license key.

This repository does not accept pull requests; public issues remain open for reproducible bugs, feedback, and change proposals. CONTRIBUTING.md explains how an accepted proposal lands.

Run the self-hosted stack

You need Node.js 24+, a working Docker Engine and Compose plugin, and access to npm during the first build. Run docker compose version and docker info first; the prerequisite guide covers installation and permission failures. The canonical clean-clone path is:

git clone https://github.com/NoodleSeed-com/noodle-core.git
cd noodle-core
npx @noodleseed/one@latest service init --profile open-core --compose
docker compose up --build --wait postgres noodle && docker compose run --build --rm bootstrap
docker compose run --build --rm cli deploy /app/examples/hello/src/server.ts --org noodle-local --app hello --env prod --access public

Noodle binds to http://127.0.0.1:8787; PostgreSQL is not exposed on the host. The final command prints the deployed MCP endpoint. Noodle Core has no web dashboard; use the Compose CLI for Core while keeping an installed host CLI signed in to Noodle Seed Cloud. The self-hosting guide owns that side-by-side workflow. Read the rest of the guide before changing authentication, exposing the service outside loopback, or relying on its data.

What is here

  • normal TypeScript server.ts authoring, validation, compilation, and local development;
  • typed deploy, status, access, history, and rollback operations through the CLI and service API;
  • tools, resources, prompts, packaged MCP Apps, Streamable HTTP, and both supported MCP eras;
  • PostgreSQL-backed operator/application state and durable local filesystem assets; and
  • a source-built Docker Compose reference with local administrator authentication.

This is not Noodle Seed Cloud. It does not include the managed Console, billing, hosted identity, managed key custody, GitHub deployment automation, cloud asset delivery, TLS, backups, high availability, monitoring, or a support SLA. See architecture for the exact public/commercial boundary and compatibility and upgrades for the 0.x guarantees.

Build an app or explore changes

Install the published CLI, then scaffold and run a TypeScript app:

npm install -g @noodleseed/one
noodle init my-app --template hello
cd my-app
noodle dev

If you prefer not to install it globally, replace each noodle invocation with npx @noodleseed/one@latest.

Start with the documentation index, then read CONTRIBUTING.md. Connector changes have a focused contribution guide. Report vulnerabilities through SECURITY.md, and review TRADEMARKS.md before naming a fork or hosted service.

Repository model

Noodle Seed develops Noodle Core in a larger private monorepo and deterministically projects the Apache-2.0 surface here. Public issues are open for bugs, feedback, and change proposals; the repository does not accept pull requests. CONTRIBUTING.md explains how an accepted proposal lands, and governance explains repository authority.

↑↓ navigate openesc close