Skip to main content
Glama
Sign In
neon3-mcp

neon3-mcp

by unco999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to neon3-mcp

No user-submitted related servers found.

    Related Servers

    • node-red-mcp

      kskwon02
      A
      license
      B
      quality
      D
      maintenance
      Connects AI assistants to the Node-RED Admin API, enabling flow inspection, node management, graph analysis, debug capture, and rollback operations through natural language.
      37
      33 npm
      MIT
    • Init MCP

      Init MCPofficial

      init-computer
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to turn plain-English descriptions into live, typed, versioned HTTPS backend endpoints with auth and secrets handled, then call them — with each endpoint able to combine LLM reasoning, web search, scraping, media and voice generation, email, databases, storage and scheduled jobs. Also lets agents create and edit projects, list and inspect generated resources and runtime packages, and apply local manifest files.
      334 npm
      MIT

    • vibekit-mcp

      vibekit-apps
      A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      49
      26 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivityStale
    ResponsivenessNo recent community issues

    Resources