Neo4j documents an official Model Context Protocol server at neo4j.com/docs/mcp/current and in the neo4j/mcp repository. It gives MCP clients structured access to a Neo4j graph: get-schema introspects labels, relationship types, and property keys; read-cypher runs read-only Cypher checked with EXPLAIN and Neo4j query-type classification; write-cypher runs writes unless NEO4J_MCP_READ_ONLY=true; list-gds-procedures lists Graph Data Science procedures when GDS is installed. Prerequisites are a running Aura, Neo4j Desktop, or self-managed database plus the APOC plugin. Local clients use stdio via uvx neo4j-mcp-server or the Homebrew/binary neo4j-mcp, with NEO4J_MCP_URI, NEO4J_MCP_USERNAME, NEO4J_MCP_PASSWORD, and NEO4J_MCP_DATABASE. Aura uses HTTP at https://<instance-id>.mcp-instances.neo4j.io after Tool authentication is enabled in the Aura console. Docs also describe an HTTP transport mode that takes URI and credentials per request and selects the database from the /db/{databaseName}/mcp path.
Use cases
- Let an agent inspect labels and relationship types before writing Cypher
- Answer graph questions with read-cypher while NEO4J_MCP_READ_ONLY=true
- Prototype writes with write-cypher only on non-production databases
- List GDS procedures when the Graph Data Science library is installed
- Connect Cursor or VS Code to Aura through the instance MCP URL
Key features
- Claude
- Cursor
- VS Code
Frequently Asked Questions
- Does read-cypher guarantee every procedure is read-only?
- The neo4j/mcp README says read-cypher uses EXPLAIN and Neo4j query-type classification. Custom procedures or functions that Neo4j misclassifies as read-only can bypass that check; classification is the procedure maintainer’s responsibility.
- What must be installed on the database?
- Neo4j MCP docs require a running instance and the APOC plugin. Graph Data Science is optional and is needed for list-gds-procedures.
- How does Aura access differ from local stdio?
- Aura docs say to enable Tool authentication, then use https://<instance-id>.mcp-instances.neo4j.io. Local stdio needs URI, username, password, and database environment variables.
Related
Related
3 Indexed items
Upstash MCP Server
Upstash documents an official Model Context Protocol server at upstash.com/docs/agent-resources/mcp implemented in the `upstash/mcp-server` repository and npm package `@upstash/mcp-server`. Started with `npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY`, it exposes tools for serverless Redis, QStash, Workflow runs, and Upstash Box so agents can manage and debug account resources from Cursor, Claude Code, VS Code, Codex, and other MCP clients. Read-only API keys automatically disable mutating tools per docs; optional `--transport http`, `--disable-telemetry`, and Upstash Box API key flags are documented for advanced setups.
Chroma MCP Server
Chroma documents an official Model Context Protocol server in the chroma-core/chroma-mcp repository and docs.trychroma.com/integrations/frameworks/anthropic-mcp, started with `uvx chroma-mcp` over stdio. Tools include `chroma_list_collections`, `chroma_create_collection`, `chroma_peek_collection`, `chroma_modify_collection`, `chroma_delete_collection`, `chroma_add_documents`, `chroma_query_documents`, `chroma_get_documents`, `chroma_update_documents`, and `chroma_delete_documents` per the README. Client types documented: ephemeral (default), persistent (`--client-type persistent --data-dir`), HTTP self-hosted, and Chroma Cloud (`--client-type cloud` with API keys). Embedding function options include default, Cohere, OpenAI, Jina, VoyageAI, and Roboflow per Chroma MCP docs.
Convex MCP Server
Convex documents a Model Context Protocol server shipped in the Convex CLI at docs.convex.dev/ai/convex-mcp-server, started locally with `npx -y convex@latest mcp start` over stdio after linking a project via `npx convex dev`. Tools include `status` (deployment selector), `tables` (declared and inferred schemas), `data` (paginated documents), `runOneoffQuery` (sandboxed read-only JS), `functionSpec`, `run` (invoke deployed functions), `logs`, `insights` (72-hour OCC and resource-limit health), and `envList`/`envGet`/`envSet`/`envRemove`. Flags such as `--prod`, `--preview-name`, `--deployment-name`, and `--disable-tools` restrict scope; production writes require `--dangerously-enable-production-deployments` per changelog defaults.