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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jeffneo/neo4j-mcp-gateway'
If you have feedback or need assistance with the MCP directory API, please join our Discord server