mcp-memgraph

# 🚀 Memgraph MCP Server Memgraph MCP Server is a lightweight server implementation of the Model Context Protocol (MCP) designed to connect Memgraph with LLMs and different clients. ## 🔧 Tools The default `server` implementation exposes the following seven tools over MCP. (`memgraph-experimental` — see [Multi-Server Architecture](#multi-server-architecture) — exposes a different, smaller set, documented there.) ### run_cypher_query(query: str) Run any arbitrary Cypher query against the connected Memgraph database. Returns one row per result, with each value in a **type-preserving** form: nodes, relationships and paths come back as `_type`-tagged objects carrying their `id`, `labels`/`type`, endpoints and `properties`; primitives, lists, maps, temporals and points keep their shape. A single node looks like: ```json { "n": { "_type": "node", "id": "<element_id>", "labels": ["Person"], "properties": { "name": "Alice" } } } ``` Because rows are preserved, a query can mix graph entities with scalars — e.g. `MATCH (n)-[e]->() RETURN n, count(e) AS out_deg` returns each node alongside its count. To get a **deduplicated, ready-to-render graph** (each node and relationship once — useful for visualization), let Cypher do the dedup and return the two lists directly: ```cypher MATCH (n)-[r]->(m) WITH collect(DISTINCT r) AS relationships, collect(DISTINCT n) + collect(DISTINCT m) AS ns UNWIND ns AS nx RETURN collect(DISTINCT nx) AS nodes, relationships ``` Each collected node and relationship comes back in the same typed form as above, so the result is a compact graph payload without repeating shared nodes per row. **Read-Only Mode:** By default, the server runs in read-only mode to prevent accidental data modifications. Write operations (CREATE, MERGE, DELETE, SET, DROP, REMOVE) are automatically blocked and will return an error. Set `MCP_READ_ONLY=false` to enable write operations. Parameters: - `query`: A valid Cypher query string. ### sear…