Neo4j MCP Servers — Cypher + Memory + Aura API

Main

• Treat schema access as the first success metric: the Cypher server exposes schema tools and enforces read timeouts (docs mention a 30s default).

• Use token limits to prevent huge query payloads from blowing up context; the Cypher server docs describe truncation using tiktoken for read responses.

• Run multiple servers with namespacing when you have multiple Neo4j instances (dev/prod or multiple graphs) to avoid tool-name collisions.

Source-backed notes

• Root README lists multiple servers: mcp-neo4j-cypher, mcp-neo4j-memory, mcp-neo4j-cloud-aura-api, and mcp-neo4j-data-modeling.
• Docs describe transport modes (stdio/SSE/HTTP) and show --transport http --host ... --port ... --path /api/mcp/ examples.
• The Cypher server docs include read timeouts (default 30s) and response token limits for read_neo4j_cypher.

FAQ

• Do I need APOC?: Yes for schema inspection: the README says APOC must be installed/enabled for schema tools to work.
• Is this the official Neo4j MCP server?: No — the root README calls these Neo4j Labs servers and links to the official product repo separately.
• How do I keep query results manageable?: Use read timeouts + token limits as documented in the Cypher server docs.