nebula-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEBULA_MAX_ROWS | No | Maximum number of result rows to include in the MCP context. Does not prevent the database from computing large results. | |
| NEBULA_PASSWORD | Yes | Password for the NebulaGraph database. Required. Note: stored in plaintext in ~/.codex/config.toml by Codex Desktop. | |
| NEBULA_USERNAME | Yes | Username for the NebulaGraph database. Required. | |
| NEBULA_ADDRESSES | Yes | One or more HOST:PORT addresses of the NebulaGraph database. Required. | |
| NEBULA_ALLOW_MUTATIONS | No | Set to 'true' to allow mutation statements via the dedicated nebula_execute_mutation tool. Defaults to 'false'. | false |
| NEBULA_CONNECT_TIMEOUT_MS | No | Connection timeout in milliseconds. Recommended: 30000. | 30000 |
| NEBULA_REQUEST_TIMEOUT_MS | No | Per-request timeout in milliseconds for individual query execution. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nebula_test_connectionA | Test the configured YueShu connection and return only redacted settings. |
| nebula_list_graphsA | List persistent graphs before choosing schema and graph context. |
| nebula_get_graph_schemaC | Read a Graph Type schema; optionally include a UTF-8 byte-bounded DDL string. |
| nebula_validate_gqlA | Validate YueShu 5.3 GQL for placeholders, dialect residuals, policy, and optional EXPLAIN. This never executes the original statement. |
| nebula_execute_queryA | Execute one approved read-only GQL statement and optionally return table, cytoscape-elements-v1 graph, deterministic analysis, and vega-lite-v5 charts. |
| nebula_execute_mutationA | Execute one mutation only when NEBULA_ALLOW_MUTATIONS=true and confirm_mutation=true. This tool is destructive and returns no charts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| nebula-connection | Redacted YueShu connection status and server version. |
TDQS
Scored across 6 tools
Each tool targets a distinct action and resource: connection testing, graph listing, GQL validation, schema retrieval, read queries, and mutations. There is no meaningful overlap, even between validate and execute, since the former never executes and the latter is read-only or mutation-specific.
All tools follow the same nebula_verb_noun pattern, with clear verbs like test, list, validate, get, and execute. The naming is consistent, predictable, and hierarchical.
Six tools is well-scoped for a graph database server covering connection, discovery, validation, schema, and execution. Each tool has a clear purpose without unnecessary bloat.
The tool surface covers the core workflow: connect, discover graphs, validate, inspect schema, execute reads, and execute mutations. Minor gaps exist, such as no explicit tool for listing all schemas or managing graphs, but these are likely outside the server's intended scope.