Neo4j MCP Integrations

Why STEADY

STEADY (74) because vendor-official documentation from an established database company carries a high continuity floor, the MCP explanation is accurate and non-promotional, and the candid statement of the protocol's open security problems is a genuine trust signal. Held below the 80s because the reviewed surface is an orientation guide rather than a server specification: the tool inventory, scoping model and write-access boundary — the details that decide whether this is safe to give an agent — are not resolved here.

Public-surface checklist

• PASS Homepage loads (required)
• PASS Primary value prop (required) — Model Context Protocol (MCP) Integrations for the Neo4j Graph Database
• PASS Cta present (required) — Get Started Free
• FAIL Pricing or access — No pricing or access terms on the reviewed guide surface; a 'Get Started Free' path exists but terms are elsewhere
• PASS Evidence or demo — 3 screenshots captured; guide links to comprehensive overview with examples

What we saw

3 screenshots captured by the Hlido engine during the reviewed run (run-c703bb83d24db4c2-neo4j-com). Our own captures — not vendor marketing material.

×

←→

What it does well

• Names MCP's open problems (security, discovery, trusted deployment, permission control) rather than glossing them
• Accurate, non-promotional explanation of the MCP host/server/client architecture
• Situates Neo4j within the ecosystem instead of overclaiming ownership of the category
• Vendor-official surface from an established database company — high continuity floor
• Links onward into GraphRAG guides, examples and the wider GenAI ecosystem

What it fails at

• No inventory of the actual tools the Neo4j MCP servers expose
• Read-only versus read-write scoping is not resolved on this surface
• No security guidance specific to giving an agent Cypher access to a production graph
• Cookie-consent interstitial is the first content encountered — a real friction for automated readers
• Reviewed surface is a guide, not a product page, so version and release state are absent

Pricing & access

• Pricing findable on the public surfaceFAIL No pricing or access terms on the reviewed guide surface; a 'Get Started Free' path exists but terms are elsewhere (tested 2026-08-23)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-23.

Compared to

• @langchain/mcp-adapters expose-vs-consume

  LangChain's adapters are framework-side plumbing for consuming any MCP server; this is a database vendor's guidance for exposing one. Read the Neo4j page to decide what to expose, the adapters to wire it in.

• BioMCP specification-clarity

  BioMCP is a domain-specific server with a concrete published tool surface; the Neo4j page is general integration guidance without one. BioMCP is easier to evaluate; Neo4j has the stronger vendor floor.

Agent relevance

API MCP SDK

Agentic-Commerce Readiness 67/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Neo4j publishes MCP server integrations for the graph database, and this guide is the vendor's entry point to them. The page itself is prose rather than a machine-readable manifest, so an agent must follow onward links to reach an installable server; the tool surface and permission scoping are not discoverable from here.

Agent-friendly score: 6/10

Evidence

• Vendor-official Neo4j developer guide for MCP integrations — source (2026-08-23) verified
• States open issues remain in MCP around security, discovery, trusted deployment and permission control — source (2026-08-23) verified
• Names major cloud and framework MCP adopters — source (2026-08-23) verified
• No tool inventory or permission model published on this surface — source (2026-08-23) verified