No.JS MCP Server
# @erickxavier/nojs-mcp
MCP (Model Context Protocol) server that provides AI assistants with deep knowledge of the **No.JS** framework — The HTML-First Reactive Framework.
## What is this?
This MCP server gives AI assistants (GitHub Copilot, Claude, Cursor, etc.) structured access to:
- **80+ directives** with syntax, examples, and usage notes
- **Head management directives** (`title`, `meta`, `link`, `script`, `base`) for declarative `<head>` control
- **Plugin system** with lifecycle hooks, custom directives, and shared state
- **32 built-in filters** (text, numbers, arrays, dates, utility)
- **Full public API** reference (config, init, router, i18n, store, plugins, etc.)
- **23 documentation pages** (getting started, routing, forms, drag-and-drop, etc.)
- **Template validation** tool to catch NoJS syntax errors
- **Component scaffolding** for common UI patterns
## Installation
### VS Code / Cursor
Add to your MCP configuration (`.vscode/mcp.json` or settings):
```json
{
"mcpServers": {
"nojs": {
"command": "npx",
"args": ["-y", "@erickxavier/nojs-mcp"]
}
}
}
```
### Claude Desktop
Add to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"nojs": {
"command": "npx",
"args": ["-y", "@erickxavier/nojs-mcp"]
}
}
}
```
## Resources
| URI | Description |
|-----|-------------|
| `nojs://ref/directives` | All directives with syntax and examples |
| `nojs://ref/api` | Complete public API reference |
| `nojs://ref/filters` | All 32 built-in filters |
| `nojs://docs/{topic}` | Documentation pages (getting-started, routing, forms-validation, etc.) |
## Tools
### `validate_template`
Validate a NoJS HTML template for syntax errors, typos, and best practices.
```
validate_template({ html: '<div bnd="name"></div>' })
// → Error: Unknown attribute "bnd" — did you mean "bind"?
```
### `explain_directive`
Get a detailed explanation of any NoJS directive.
```
explain_directive({ directive: "each" })
// → Full explanation with syntax, examples, and notes
```
### `list_directives`
List all directives, optionally filtered by category.
```
list_directives({ category: "data" })
// → All data-fetching directives (get, post, put, patch, delete, etc.)
```
**Categories:** `data`, `state`, `binding`, `conditionals`, `loops`, `events`, `styling`, `forms`, `routing`, `animation`, `dnd`, `i18n`, `refs`, `head`, `misc`
### `scaffold_component`
Generate NoJS component templates.
```
scaffold_component({ type: "form", features: ["validation", "i18n"] })
// → Complete login form with validation
```
**Types:** `form`, `list`, `detail`, `card`, `modal`, `nav`
### `get_cheatsheet`
Get a condensed directive cheatsheet for quick reference.
## Development
```bash
# Install dependencies
npm install
# Build
npm run build
# Run locally
node dist/index.js
```
## Versioning
This package version always matches the No.JS framework version. Current: **1.11.0**
## Ecosystem
- [No.JS Framework](https://github.com/AeonJVS/NoJS) — The HTML-First Reactive Framework
- [No.JS LSP](https://github.com/AeonJVS/NoJS-LSP) — Language Server Protocol support
- [No.JS Skill](https://github.com/AeonJVS/NoJS-Skill) — AI Skill for code generation
- [No.JS CLI](https://github.com/AeonJVS/NoJS-CLI) — Command-line scaffolding and tooling
- [No.JS Website](https://no-js.dev/)
- [NoJS Discord](https://discord.gg/CaSbGYg3xY)
## License
MIT © Erick Xavier
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: explain_directive provides detailed explanations, get_cheatsheet offers quick reference, list_directives enumerates available directives, scaffold_component generates templates, and validate_template checks syntax and best practices. The descriptions make it easy for an agent to select the right tool for each specific need.
All tool names follow a consistent verb_noun pattern (explain_directive, get_cheatsheet, list_directives, scaffold_component, validate_template), using clear action verbs and descriptive nouns. There are no deviations in style or convention, making the set predictable and easy to understand.
With 5 tools, this server is well-scoped for its purpose of supporting NoJS development. Each tool earns its place by covering distinct aspects: documentation (explain, cheatsheet, list), code generation (scaffold), and validation (validate). This count avoids bloat while providing complete coverage for common tasks.
The tool set provides complete coverage for the NoJS domain, including documentation lookup (explain, cheatsheet, list), component creation (scaffold), and quality assurance (validate). There are no obvious gaps; agents can access all necessary information, generate code, and validate it without dead ends.