Can AI agents automate Neo4j?

Neo4j is automatable today through the Query API and a first-party MCP server. The Query API executes Cypher over HTTP at /db/{databaseName}/query/v2 and supersedes the deprecated transactional HTTP API. Callers POST JSON with a statement and parameters. The documented MERGE example writes nodes. Default ports on self-managed instances are 7474 HTTP and 7473 HTTPS; Aura uses HTTPS on 443. Authentication is HTTP Basic or Bearer, with Bearer intended for SSO. Official drivers for Python, Go, Java, and JavaScript speak Bolt and are the vendor's preferred path when a supported language exists. cypher-shell is the official CLI over Bolt. It runs interactively or as a script via a positional Cypher string, --file, or a piped file, with --format auto, verbose, or plain. It requires Java 21 when installed separately. Official Neo4j MCP is documented at neo4j.com/docs/mcp/current/ and implemented by github.com/neo4j/mcp (pip package neo4j-mcp-server). Tools are get-schema, read-cypher, write-cypher, and list-gds-procedures. Prerequisites are a running Neo4j instance (Aura, Desktop, or self-managed) and the APOC plugin. Official configuration docs state that STDIO mode validates connectivity and APOC availability at startup. If Graph Data Science is absent, GDS tools are disabled and other tools remain. write-cypher is disabled when NEO4J_READ_ONLY is true. Zapier, Make, Power Automate, and n8n listings were not opened. Computer-use viability is unassessed. API scores 8 and is the best path because MCP requires APOC and can disable writes.

Best path today: api · Overall automatability: 8/10