A
licenseA
qualityC
maintenanceEnables AI assistants to manage Flow Relay projects, generate handoffs and insights, and interact with integrations like Discord through natural language.
18
622 npm
AGPL 3.0
neon3-mcp
by unco999
Related Servers
Alternatives to neon3-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceConnects AI assistants to the Node-RED Admin API, enabling flow inspection, node management, graph analysis, debug capture, and rollback operations through natural language.3713 npmMIT
- AlicenseBqualityDmaintenanceEnables the management of AI-powered VibeKit apps, allowing users to control deployments, monitor logs, and perform database operations directly from MCP-compatible clients. It facilitates interaction with hosted AI agents and the execution of headless coding tasks through natural language.499 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and manage Flowcore resources through a structured API.215 npm9-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to execute Expo and EAS operations including project setup, cloud builds, OTA updates, app submission, and diagnostics.MIT
- AlicenseAqualityDmaintenanceLets AI assistants interact with Node-RED to read flows, search nodes, edit function code, deploy changes safely, and manage modules.131MIT
TDQS
B3.3/5.0
Scored across 11 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues