AI & MCP
@nuforge/mcp is a Model Context Protocol (MCP) stdio server that lets AI assistants such as Claude Code, Claude Desktop, and Cursor understand and work with nuforge. It ships a binary named nuforge-mcp, so an assistant can validate, format, and convert DSL directly inside your editor or chat.
Tools
| Tool | What it does |
|---|---|
nuforge_validate | Parse DSL and report whether it is valid |
nuforge_format | Parse and re-stringify DSL into canonical form |
nuforge_to_react | Generate a clean React/TSX component from DSL |
nuforge_explain | Search the reference (overview, DSL, API, examples) for a topic |
Resources
The server also exposes reference resources that an assistant can read on demand:
nuforge://reference/overviewnuforge://reference/dslnuforge://reference/apinuforge://reference/examples
Run it
Build the package first, then start the server over stdio:
node packages/mcp/dist/index.mjs # build first: pnpm --filter @nuforge/mcp build
# or, once published: npx -y @nuforge/mcp
Register with a client
For Claude Code, register the server by absolute path:
claude mcp add nuforge -- node /ABS/PATH/to/packages/mcp/dist/index.mjs
For Claude Desktop or Cursor, add a JSON config entry:
{
"mcpServers": {
"nuforge": {
"command": "node",
"args": ["/ABS/PATH/to/packages/mcp/dist/index.mjs"]
}
}
}
Once the package is published, you can replace the command with npx and use args ["-y", "@nuforge/mcp"] instead of an absolute path.
What it unlocks
With the server registered, an assistant can validate DSL you wrote, convert a page to React, or look up the API without leaving the chat. The reference resources keep the assistant grounded in nuforge's actual surface rather than guessing.
Next steps
- Codegen — how DSL becomes React/TSX
- Getting started — set up nuforge from scratch