Skip to main content
Glama
angrysky56

NeoCoder Neo4j AI Workflow

by angrysky56
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to NeoCoder Neo4j AI Workflow

No user-submitted related servers found.

    Related Servers

    • genpark-knowledge-graph-entity-relation-triplet-extractor-skill by Alpha-Park

      genpark-knowledge-graph-entityofficial

      Alpha-Park
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to build and query structured semantic graphs, extracting, traversing and multi-hop reasoning over entity-relation-object triples while producing Cypher and JSON-LD graph output. It also combines BM25 lexical and dense vector retrieval with rank fusion, semantic caching and context reordering for grounded agentic memory.
      7
      MIT

    • Neo4j MCP Server

      vpro1032
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Neo4j graph databases through natural language, supporting Cypher queries, schema management, data manipulation, and graph algorithms.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 30 tools

    Disambiguation3/5

    Most tools have distinct purposes, but several pairs overlap: propose_tool/request_tool have nearly identical descriptions, and run_custom_query/write_neo4j_cypher both execute Cypher queries with unclear boundaries. get_guidance_hub and get_best_practices also serve similar informational roles.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, with predictable use of get, list, create, update, delete, and switch. This consistency makes the toolset easy to navigate.

    Tool Count2/5

    With 30 tools, the server exceeds the 25-tool threshold and feels heavy for a single server. While the breadth is ambitious, many tools could be consolidated (e.g., separate proposal/request workflows) to reduce cognitive load.

    Completeness2/5

    The domain is broad but incompletely covered. Snippets have full CRUD, but action templates lack create/update/delete, projects are read-only, and tool proposals/requests have no update/delete operations. These gaps create dead ends in workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources