Neo4j graph database server (schema + read/write-cypher) and separate graph database backed memory
Neo4j graph database server (schema + read/write-cypher) and separate graph database backed memory.
These MCP servers are a part of the Neo4j Labs program. They are developed and maintained by the Neo4j Field GenAI team and welcome contributions from the larger developer community. These servers are frequently updated with new and experimental features, but are not supported by the Neo4j product team.
Model Context Protocol (MCP) is a standardized protocol for managing context between large language models (LLMs) and external systems.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
| Variable | Description | Required |
|---|---|---|
| NEO4J_TRANSPORT | Configuration value read at startup. | Optional |
| NEO4J_MCP_SERVER_HOST | Endpoint or connection string the server talks to. | Optional |
| NEO4J_MCP_SERVER_PORT | Configuration value read at startup. | Optional |
| NEO4J_MCP_SERVER_PATH | Filesystem location the server is allowed to use. | Optional |
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.