FalkorDB MCP Server

What it does

FalkorDB MCP Server connects an assistant to a FalkorDB graph database, either one you run yourself or one on FalkorDB Cloud. The assistant can list the graphs on the instance, send OpenCypher queries that read or change data, and delete whole graphs. Queries can take a separate params object, so values are passed as $name instead of being pasted into the Cypher text.

FalkorDB has no fixed schema, so three tools help the assistant find its way around before it queries. One returns node labels, relationship types and which labels connect to which, worked out from a sample of 10,000 relationships by default (up to 100,000). The other two sample 100 nodes or relationships of a given label or type by default (up to 10,000) and rank their property keys by how often they appear. All three always run as read-only queries.

By default it talks over stdio. Set MCP_TRANSPORT=http to serve Streamable HTTP instead, optionally protected by a bearer key in MCP_API_KEY. In version 1.3.0 the code falls back to port 3000 when neither MCP_PORT nor PORT is set (src/config/index.ts), while the README examples all use 8080. The same file reads FALKORDB_STRICT_READONLY, which the README never mentions. When it is true, the server refuses any write query and any delete_graph call, even if a call asks for write mode. FALKORDB_DEFAULT_READONLY, by contrast, only changes the default, and a single query can override it (src/mcp/tools.ts).

What it needs

Node.js 18 or later and a FalkorDB instance it can reach: local, remote or FalkorDB Cloud. By default it connects to localhost:6379 with no password. The Docker image falkordb/mcpserver and the repository's docker-compose.yml run it in HTTP mode on port 8080. Start the container with -p 8080:8080, then point the client at http://localhost:8080.

Limits

Works only with FalkorDB; it cannot reach other graph or SQL databases. In version 1.3.0, the release on npm, the connection code has no TLS option. The FALKORDB_TLS setting the README describes is not read by that version, so an instance that only accepts TLS connections, such as FalkorDB Cloud behind TLS, cannot be reached until a later release. Schema topology comes from a sample and may be incomplete on large graphs. FalkorDB does not accept parameters in LIMIT or SKIP. The README says files written by the bundled docker-compose FalkorDB do not yet survive docker compose down.

Who it suits

Suits developers who already keep data in FalkorDB and want an assistant to explore it and write Cypher against it. It is published by FalkorDB itself and runs on your own machine. It can change and delete data, so for production or replica instances set FALKORDB_STRICT_READONLY=true, which blocks writes for every call. If your database is Neo4j, or a FalkorDB instance that requires TLS, this release is the wrong choice. FalkorDB's QueryWeaver, which we also list, is a separate product that turns plain questions into SQL for relational databases. It does not work on FalkorDB graphs.