NeoCoder Neo4j AI Workflow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level for the server | INFO |
| NEO4J_URL | No | Neo4j connection URL | bolt://localhost:7687 |
| MCP_TRANSPORT | No | MCP transport protocol | stdio |
| NEO4J_DATABASE | No | Neo4j database name | neo4j |
| NEO4J_PASSWORD | Yes | Neo4j database password | |
| NEO4J_USERNAME | No | Neo4j database username | neo4j |
| PYTHONUNBUFFERED | No | Python unbuffered output mode | 1 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_guidance_hubA | Get the AI Guidance Hub content, which serves as the central entry point for navigation. |
| list_action_templatesA | List all available action templates. |
| get_action_templateA | Retrieve detailed steps for a specific action template by keyword. |
| get_best_practicesC | Get the best practices guide for coding workflows. |
| suggest_toolB | Suggest the appropriate tool based on a task description. |
| get_projectA | Get details about a specific project. |
| list_projectsB | List all available projects. |
| log_workflow_executionA | Record a successful workflow execution (ONLY after passing tests). |
| get_workflow_historyB | View history of workflow executions, optionally filtered. |
| add_template_feedbackA | Provide feedback about an action template to improve it. |
| run_custom_queryB | Run a custom Cypher query for advanced operations. |
| write_neo4j_cypherB | Execute a WRITE Cypher query (for creating/updating data). |
| list_cypher_snippetsC | List all available Cypher snippets with optional filtering. |
| get_cypher_snippetA | Get a specific Cypher snippet by ID. |
| search_cypher_snippetsC | Search for Cypher snippets by keyword, tag, or pattern. |
| create_cypher_snippetC | Add a new Cypher snippet to the database. |
| update_cypher_snippetC | Update an existing Cypher snippet. |
| delete_cypher_snippetC | Delete a Cypher snippet from the database. |
| get_cypher_tagsA | Get all tags used for Cypher snippets. |
| propose_toolB | Propose a new tool for the NeoCoder system. |
| request_toolC | Request a new tool feature for the NeoCoder system. |
| get_tool_proposalA | Get a specific tool proposal by ID. |
| get_tool_requestA | Get a specific tool request by ID. |
| list_tool_proposalsA | List all tool proposals with optional filtering. |
| list_tool_requestsB | List all tool requests with optional filtering. |
| get_current_incarnationA | Get the currently active incarnation type. |
| list_incarnationsB | List all available incarnations. |
| switch_incarnationC | Switch the server to a different incarnation. |
| get_cleanup_statusA | Get current cleanup and resource status for monitoring. |
| check_connectionB | Check the Neo4j connection status and database access permissions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 30 tools
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.
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.
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.
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.