No.JS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_templateC | Validate a NoJS HTML template for syntax errors, unknown directives, and best practices |
| explain_directiveB | Get a detailed explanation of a NoJS directive with syntax and examples |
| list_directivesB | List all NoJS directives, optionally filtered by category |
| scaffold_componentC | Generate a NoJS component template following framework conventions |
| get_cheatsheetB | Get a condensed NoJS directive cheatsheet for quick reference |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs-README | NoJS documentation: README |
| docs-actions-refs | NoJS documentation: actions refs |
| docs-animations | NoJS documentation: animations |
| docs-cheatsheet | NoJS documentation: cheatsheet |
| docs-conditionals | NoJS documentation: conditionals |
| docs-configuration | NoJS documentation: configuration |
| docs-custom-directives | NoJS documentation: custom directives |
| docs-data-binding | NoJS documentation: data binding |
| docs-data-fetching | NoJS documentation: data fetching |
| docs-drag-and-drop | NoJS documentation: drag and drop |
| docs-error-handling | NoJS documentation: error handling |
| docs-events | NoJS documentation: events |
| docs-examples | NoJS documentation: examples |
| docs-filters | NoJS documentation: filters |
| docs-forms-validation | NoJS documentation: forms validation |
| docs-getting-started | NoJS documentation: getting started |
| docs-i18n | NoJS documentation: i18n |
| docs-loops | NoJS documentation: loops |
| docs-playground | NoJS documentation: playground |
| docs-routing | NoJS documentation: routing |
| docs-state-management | NoJS documentation: state management |
| docs-styling | NoJS documentation: styling |
| docs-templates | NoJS documentation: templates |
| ref-directives | Complete reference of all NoJS directives with syntax and examples |
| ref-api | NoJS public API reference (config, init, directive, filter, etc.) |
| ref-filters | All 32 built-in NoJS filters with syntax and examples |
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.