@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:
Any other MCP client: run npx -y @noodlrstudio/mcp as a stdio server. For example,
in a project .mcp.json:
Paths in tool arguments are resolved against the directory the server starts
in, normally your project.
What it provides
Resources
Tools
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
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):
Or open it in the MCP Inspector:
npx @modelcontextprotocol/inspector node packages/mcp/dist/bin.js.
Releasing
- Bump
version in package.json, src/server.ts (SERVER_VERSION) and
both places in server.json, and add a CHANGELOG.md entry.
- Publish to npm:
npm publish in this folder.
- 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.