Skip to main content
Glama
st3v0rr

Neo4j MCP Server

by st3v0rr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Neo4j MCP Server

No user-submitted related servers found.

    Related Servers

    • Neo4j MCP Server

      Tobarrientos2
      A
      license
      B
      quality
      D
      maintenance
      An implementation for managing Neo4j graph database operations through the Model Context Protocol, enabling users to execute Cypher queries against their Neo4j database via AI assistants like Cursor and Claude Desktop.
      1
      5 npm
      4
      ISC

    • Neo4j MCP Server

      alvaropaco
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Neo4j that provides abstract graph operations for LLMs, enabling safe and consistent interaction with Neo4j databases through tools like search, insert, update, delete, and schema introspection.
      8
      MIT

    • Neo4j GraphRAG MCP Server

      neo4j-field
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables LLMs to perform semantic and fulltext searches within Neo4j while executing complex, search-augmented Cypher queries for GraphRAG applications. It provides tools for database schema discovery and supports multi-provider embeddings to facilitate advanced graph traversals.
      5
      3
      MIT
    • Memgraph MCP Server by memgraph

      Memgraph MCP Serverofficial

      memgraph
      A
      license
      C
      quality
      Not graded
      maintenance
      A lightweight server implementation of the Model Context Protocol that connects Memgraph database with LLMs, allowing users to interact with graph databases through natural language.
      1
      25
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: write_neo4j_cypher for mutations, read_neo4j_cypher for queries, and get_neo4j_schema for metadata. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent verb_neo4j_noun pattern (write/read/get). The naming is predictable and the verb clearly indicates the operation type.

    Tool Count5/5

    With three tools, the server is well-scoped for its purpose: read, write, and schema introspection. Each tool covers an essential need without redundancy.

    Completeness5/5

    The surface covers the core operations for a Neo4j MCP server: fetching schema, executing read queries, and executing write queries. Since write Cypher can handle create, update, and delete, there are no major gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources