MCP Server & AI Skill
Two packaged tools make AI-assisted ChainRender development first-class: the MCP server (so an AI calls the SDK
as tools) and the app-builder skill (so an AI knows the workflow). Both wrap the shipped @chainrender/client —
the AI's output stays verifiable (graded, compiled, validated), never blind.
They enforce two things a correct build needs: the on-chain paradigm (the component IS the app — compiled,
registered on-chain, rendered by an eth_call; not a React app that fetches with viem and hand-renders while
ChainRender only prints a hash — see Building Correctly) and the
trust grade (A = fully on-chain/trustless; off-chain dependencies drop the grade
and must be declared, never hidden). The skill teaches both; the MCP grade tool proves the second.
The MCP server — @chainrender/mcp
A Model Context Protocol server that exposes the ChainRender SDK as tools, so an AI assistant in an MCP-capable editor or chat can build apps by calling them directly.
Tools
| Tool | What it does |
|---|---|
chainrender_vocabulary |
The closed vocabulary (node types, capabilities, resolver kinds). Call first. |
chainrender_grade |
Grade a composition (A/B/C + itemized breakdown). |
chainrender_compile |
Compile to the content-addressed hash (deterministic). |
chainrender_validate |
Enforcer-equivalent checks (pass a manifest { name, version, root }). |
chainrender_review |
grade + compile + (optional) validate in one call — the finalize loop. |
Install & configure
npm install -g @chainrender/mcp # published — installs the ChainRender MCP server
Add to your MCP client's config:
{
"mcpServers": {
"chainrender": { "command": "chainrender-mcp" }
}
}
Now the AI can call the tools directly — the same grade/compile/validate loop, without pasting the vocabulary by
hand. The tools are thin wrappers over @chainrender/client; no logic is duplicated, so what the tools compute is
exactly what the chain computes.
The app-builder skill — chainrender-app-builder
A skill (a SKILL.md plus worked examples) that teaches an AI agent how to build ChainRender apps well: the
non-negotiable workflow (vocabulary → compose → grade → compile → validate), the Grade-A rules, the do's and
don'ts, and request→app examples. Where the MCP server gives the AI the tools, the skill gives it the method.
Load it wherever your AI tooling discovers skills. It's plain Markdown — no build step. It pairs naturally with the MCP server: the skill tells the agent the workflow, the MCP tools execute it.
How they fit together
skill (the method) → the AI follows the workflow
+
MCP server (the tools) → the AI calls vocabulary / grade / compile / validate
+
@chainrender/client (the SDK) → the single source of truth both wrap
=
verifiable AI-built apps: graded, compiled, validated — never blind trust
Status
@chainrender/client— live on npm (npm install @chainrender/client).@chainrender/mcp— published on npm (npm install -g @chainrender/mcp); wraps the SDK'svocabulary/grade/compileComponent/validateApp.chainrender-app-builderskill — built (Markdown; ready to distribute).create-chainrender— live on npm (npm create chainrender@latest my-app).
Related
- Building with AI — the step-by-step workflow.
- Instructing an AI — prompt patterns.
- Building Correctly — the on-chain paradigm the skill enforces.
- The Vocabulary · The Trust Grade — the grading the tools compute.