YDB MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YDB_LOGIN | No | Login for login-password authentication | |
| YDB_DATABASE | No | YDB database path, e.g., /local | |
| YDB_ENDPOINT | No | YDB endpoint, e.g., grpc://localhost:2136 | |
| YDB_PASSWORD | No | Password for login-password authentication | |
| YDB_AUTH_MODE | No | Authentication mode (optional, defaults to anonymous) | |
| YDB_SA_KEY_FILE | No | Path to service account key file | |
| YDB_ACCESS_TOKEN | No | Access token for token-based authentication |
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 |
|---|---|
| ydb_queryB | Run a read-only SQL query against YDB database |
| ydb_query_with_paramsC | Run a read-only parameterized SQL query with JSON parameters |
| ydb_explain_queryC | Explain a SQL query against YDB |
| ydb_explain_query_with_paramsC | Explain a parameterized SQL query against YDB |
| ydb_statusA | Get the current YDB connection status |
| ydb_list_directoryC | List directory contents in YDB |
| ydb_describe_pathC | Get detailed information about a YDB path |
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 7 tools
Each tool targets a clearly distinct purpose: executing vs explaining queries, with vs without parameters, and separate tools for status, directory listing, and path details. No two tools are ambiguous or likely to be confused during selection.
All tools share the ydb_ prefix, and most follow a verb_noun pattern (list_directory, describe_path) with a consistent with_params modifier. Minor deviations like the noun-only ydb_status and ydb_query are still predictable and do not hinder readability.
Seven tools is well-scoped for a database server focused on read-only operations, covering queries, explanations, status, and structural navigation without overflow or sparse coverage.
The server's read-only scope is fully covered: plain and parameterized queries, explain plans for both, connection status, and directory/path inspection. No obvious missing operations are needed for the intended use case.