NebulaGraph MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEBULA_HOST | Yes | Your NebulaGraph server host | |
| NEBULA_PORT | Yes | Your NebulaGraph server port | |
| NEBULA_USER | Yes | Your NebulaGraph server user | |
| NEBULA_VERSION | No | NebulaGraph version (only v3 is supported) | v3 |
| NEBULA_PASSWORD | Yes | Your NebulaGraph server password |
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 |
|---|---|
| list_spacesC | List all available spaces Returns: The available spaces |
| get_space_schemaC | Get the schema information of the specified space Args: space: The space to get the schema for Returns: The schema information of the specified space |
| execute_queryC | Execute a query Args: query: The query to execute space: The space to use Returns: The results of the query |
| find_pathC | Find paths between two vertices Args: src: The source vertex ID dst: The destination vertex ID space: The space to use depth: The maximum path depth limit: The maximum number of paths to return Returns: The path results |
| find_neighborsC | Find the neighbors of the specified vertex Args: vertex: The vertex ID to query space: The space to use depth: The depth of the query, default is 1 Returns: The neighbors of the specified vertex |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: execute_query for general queries, find_neighbors for vertex adjacency, find_path for pathfinding, get_space_schema for schema inspection, and list_spaces for space enumeration. The descriptions reinforce these distinct functions, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern (e.g., execute_query, find_neighbors, list_spaces) with clear, descriptive verbs. There are no deviations in style or convention, making the naming predictable and easy to understand across the set.
With 5 tools, this server is well-scoped for graph database operations, covering essential functions like querying, traversal, pathfinding, and schema management. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides strong coverage for core graph operations, including query execution, neighbor and path finding, and space/schema inspection. A minor gap exists in CRUD operations for vertices or edges (e.g., create, update, delete), but agents can likely work around this with queries.