neo4j-mcp-gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | No | Neo4j bolt URI (shared) | bolt://localhost:7687 |
| TOOLS_DIR | No | Where YAML use-case tools are discovered | tools |
| NEO4J_MCP_CMD | No | How to launch the official downstream server | uvx neo4j-mcp-server |
| NEO4J_DATABASE | No | Target database (shared) | neo4j |
| NEO4J_PASSWORD | No | Neo4j password (shared) | password |
| NEO4J_USERNAME | No | Neo4j user (shared) | neo4j |
| USECASE_PREFIX | No | Namespace prefix for YAML tool names | usecase_ |
| NEO4J_READ_ONLY | No | Set to 'true' to disable downstream write-cypher | |
| NEO4J_TELEMETRY | No | Downstream telemetry opt-in | false |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| usecase_detect_synthetic_identityA | Identifies potential synthetic identities by finding clusters of identities sharing PII elements without legitimate relationship explanation. (Use-case tool from detect_synthetic_identity.yaml; runs curated Cypher in read mode.) |
| usecase_search_movies_by_actorA | Find movies a given actor appeared in. (Use-case tool from example_movies.yaml; runs curated Cypher in read mode.) |
| usecase_high_risk_transactionsA | List a customer's outgoing transactions that benefit an account in a high-risk jurisdiction, optionally filtered to a minimum amount. Useful for AML triage. (Use-case tool from high_risk_transactions.yaml; runs curated Cypher in read mode.) |
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 3 tools
Each tool addresses a distinctly different use case: synthetic identity detection, movie search, and high-risk transaction analysis. There is no overlap or ambiguity in their intended purposes.
All tools share the consistent 'usecase_' prefix, but the action part varies: 'detect', 'search', and a noun phrase 'high_risk_transactions' (no verb). This mix of verb_noun and noun-only patterns is somewhat inconsistent.
With only 3 tools, the set is on the low side for a Neo4j gateway that could plausibly support many graph operations. It feels like a small demo set rather than a comprehensive service, but it is not absurdly thin.
The tools are a random assortment of curated use cases with no clear domain coverage. There is no general query, write, or management capability, and the movie search seems unrelated to fraud/AML use cases, leaving significant gaps for any given purpose.