neon3-mcp
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 |
|---|---|
| neon3_nui_referenceB | Read the authoritative Neon3 NUI Flow V1 reference. Topics: overview, grammar, components, statecharts, interactions, diagnostics. |
| neon3_nui_validateB | Parse and compile NUI Flow with Neon3's production parser/compiler. Never submit automatically. |
| neon3_nui_inspectC | Return the canonical IR, typed input schema, state machines, stable node outline, bindings, and budgets for NUI Flow. |
| neon3_capabilitiesC | Query service.describe from Neon3 services and return their current capabilities and epochs. |
| neon3_ui_snapshotC | Read the current UI runtime snapshot, including active fragment and input revisions. |
| neon3_nui_submitC | Validate NUI Flow locally, then submit it through ui-runtime to the WGPU runtime. |
| neon3_project_assetsC | Read project summary and stable AssetRef entries from projectd. |
| neon3_app_initB | Create a bounded Python or Node Neon3 application template. Files are written only below NEON3_APP_ROOT. |
| neon3_app_runC | Run a generated Python or Node app with a fixed executable profile and bounded timeout. |
| neon3_app_testA | Run the generated app's deterministic local protocol checks without contacting a live Neon3 service. |
| neon3_diagnoseC | Aggregate service snapshots, UI revisions, and interaction trace for a Neon3 authoring issue. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| neon3-skill | The Neon3 AI authoring skill for NUI Flow and external applications. |
| neon3-reference | Authoritative Neon3 NUI Flow topic reference. |
TDQS
Scored across 11 tools
Each tool addresses a distinct stage or resource: reference docs, validation, IR inspection, submission, project assets, capabilities, UI snapshot, app template lifecycle, and diagnostics. There is no meaningful overlap, and validate/inspect/submit are clearly separated by compile, inspect, and runtime submission roles.
All tool names share the neon3_ prefix and use snake_case, which is consistent and readable. However, the set mixes noun-style names like nui_reference and ui_snapshot with verb-style names like nui_validate and app_run, so the naming pattern is not perfectly uniform.
11 tools is a well-scoped count for a Neon3 authoring/debugging server. Each tool provides a distinct capability needed for the domain without redundant or superfluous entries.
The core workflow is well covered: reference, validate, inspect, submit, create/run/test app templates, and diagnose issues. Minor gaps exist, such as no explicit update/delete for app templates and no write access to project assets, but these do not block the primary authoring flow.