Noodlr plugins

io.github.noodlrstudioPublished by GitHub account noodlrstudiov0.2.2Updated Nov 14, 2026

Build Noodlr Board plugins: Play API docs, schemas, UI kit, scaffolding and review checks.

The publisher's own server: Pipeline Pal

Overview

AI-generated overview

Local stdio MCP server that gives a coding agent Noodlr Board plugin docs, schemas, UI kit and theme tokens, plus scaffolding and review checks.

What you can do
  • Scaffold a Play node or web app bridge plugin project, writing files to a directory or returning them
  • Validate Play node manifests, state fields and ports, audiframe and legacy web app manifests, and audio plugin manifests
  • Compare declared capabilities with the context APIs the source uses
  • Lint CSS and Svelte style blocks for colour literals that should be theme tokens
  • Read reference resources on plugin routes, design rules, capabilities, web apps, submission and UI components
When to use it
Use it when you are building or reviewing Noodlr Board plugins with a coding agent and want the agent to work against the real plugin API, schemas and theme tokens instead of guessing, and to run the same checks reviewers run before submitting.
Requirements
Runs locally over stdio, typically started with npx from the npm package. Needs Node.js and an MCP client that can launch a stdio server. No account, API key or environment variable is required. Relative paths in tool arguments resolve against the directory the server starts in.
Before you install
scaffold_plugin writes files when given a directory, which must be empty or not exist. Validation and lint tools only report problems; check_capabilities is a static heuristic, so an unused capability may be a false positive. The server states it sends nothing anywhere and needs no account.

Installation

In SourceWeft

  1. Open Noodlr plugins in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@noodlrstudio/mcp

A Model Context Protocol server for building Noodlr Board plugins with a coding agent. It gives the agent the plugin contracts, schemas, UI kit and theme tokens, and the checks reviewers run, so it writes plugins against the real API instead of guessing.

It runs locally over stdio. It needs no account and sends nothing anywhere.

Full guide, with a walkthrough that builds a compressor: Building plugins with a coding agent.

Set up

Claude Code:

sh
claude mcp add noodlr -- npx -y @noodlrstudio/mcp

Any other MCP client: run npx -y @noodlrstudio/mcp as a stdio server. For example, in a project .mcp.json:

json
{  "mcpServers": {    "noodlr": { "command": "npx", "args": ["-y", "@noodlrstudio/mcp"] }  }}

Paths in tool arguments are resolved against the directory the server starts in, normally your project.

What it provides

Resources

URIContents
noodlr://docs/overviewPlugin routes, when to use each, and the workflow
noodlr://docs/design-rulesTheming, capability, state and lifecycle rules
noodlr://docs/capabilitiesEvery capability and the context API behind it
noodlr://docs/web-appsWeb apps on audiframe, and the earlier Noodlr bridge
noodlr://schemas/audiframe/manifestThe audiframe client manifest schema
noodlr://docs/submittingWhat a review pull request needs
noodlr://ui/components@noodlrstudio/ui Play node controls and their props
noodlr://theme/tokensThe --noodlr-* tokens for Light and Dark
noodlr://schemas/play-node/manifestPlay node manifest JSON Schema
noodlr://schemas/play-node/definitionPlay node definition JSON Schema
noodlr://schemas/audio-plugin/manifestWAM 2 / Cmajor / WCLAP manifest JSON Schema

Tools

ToolWhat it does
scaffold_pluginCreates a Play node or web app bridge project
validate_play_nodeValidates a manifest, state fields and ports, including defaults
validate_audiframe_manifestChecks an audiframe manifest with audiframe's own validator
validate_web_app_manifestChecks a manifest for the earlier Noodlr bridge
validate_audio_plugin_manifestValidates a curated audio plugin manifest
check_capabilitiesCompares declared capabilities with the context APIs the code uses
lint_themeFinds colour literals that should be --noodlr-* tokens

check_capabilities is a static check. A missing capability is reliable; an "unused" one may be reached in a way the check cannot see, so treat it as a prompt to look.

Prompts

  • create-play-node: build a Play node from an idea, end to end.
  • connect-web-app: make an existing web app playable in a Web App node with audiframe.
  • prepare-for-review: run every check and list what review still needs.

Developing

sh
npm run build   # regenerates the UI catalogue from packages/ui, then compilesnpm test

src/generated/ui-catalogue.ts is generated from packages/ui/src/play-node. Do not edit it by hand.

To call the built server by hand, use scripts/call.mjs (run from the repo root, so paths resolve there):

sh
node packages/mcp/scripts/call.mjs toolsnode packages/mcp/scripts/call.mjs check_capabilities '{"directory":"examples/compressor-play-node"}'

Or open it in the MCP Inspector: npx @modelcontextprotocol/inspector node packages/mcp/dist/bin.js.

Releasing

  1. Bump version in package.json, src/server.ts (SERVER_VERSION) and both places in server.json, and add a CHANGELOG.md entry.
  2. Publish to npm: npm publish in this folder.
  3. In GitHub, run Actions › Publish to MCP Registry › Run workflow. It checks that server.json matches the version on npm, then publishes it to the MCP Registry as io.github.noodlrstudio/noodlr, using GitHub's OIDC identity for the noodlrstudio organization.

mcp-publisher login github run on your own machine can't publish under the organization: it only sees your personal account.

Source: packages/mcp/README.md at commit 7bb1541

Tools

7

scaffold_plugin

Scaffold a plugin

Create a new Play node (Svelte, reviewed) or web app bridge plugin (no review). With `directory`, writes the files there (it must be empty or not exist); otherwise returns them.

Parametersidrequirednamerequiredrouterequireddirectorydescription

validate_play_node

Validate a Play node definition

Validate a Play node's manifest, state fields and ports against the host's rules, including that state defaults are valid. Pass the objects from your definePlayNode call as JSON.

Parametersportsstatemanifestrequired

validate_audiframe_manifest

Validate an audiframe manifest

Check the manifest passed to createClient from @audiframe/client, using audiframe's own validator, and explain what is wrong. This is the route for new web apps.

Parametersmanifestrequired

validate_web_app_manifest

Validate a legacy Noodlr bridge manifest

For apps on the earlier @noodlrstudio/plugin-sdk bridge (createNoodlrWebAppBridge) only; new web apps use audiframe and validate_audiframe_manifest. Returns the manifest as the host will see it.

Parametersmanifestrequired

validate_audio_plugin_manifest

Validate an audio plugin manifest

Validate a curated WAM 2, Cmajor or WCLAP plugin manifest, including checksums and ports.

Parametersmanifestrequired

check_capabilities

Check declared capabilities

Compare the capabilities a Play node declares with the context APIs its source uses. Reports missing (the host will refuse the call) and unused (reviewers will ask) capabilities. Static heuristic: treat 'unused' as a prompt to check, not proof.

Parametersdeclareddirectoryrequired

lint_theme

Find colour literals

Find hex, rgb(), hsl(), oklch() and named colours in .css files and Svelte <style> blocks. Play nodes must use --noodlr-* tokens so they work in Light and Dark themes.

Parametersdirectoryrequired

Version history

1
  1. v0.2.2LatestNov 13, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Plugins integrations