Memgraph MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_queryC | Run a query against Memgraph |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema://main |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'run_query' follows a clear verb_noun pattern.
One tool is too few for a database server's apparent scope, as it severely limits functionality (e.g., no schema management, data manipulation beyond queries, or connection handling). This is a significant mismatch for the domain.
The tool surface is severely incomplete for a database server. It only supports running queries, lacking essential operations like creating/dropping databases, managing schemas, listing tables, or handling transactions, which will cause frequent agent failures.