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_queryC | Run a SQL query against YDB database |
| ydb_query_with_paramsC | Run a 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 has a distinct purpose: describing a path, explaining queries (with or without params), listing directory contents, running queries (with or without params), and checking status. No overlap or confusion.
All tools follow a consistent 'ydb_<verb>' pattern with snake_case. The verb is specific and the 'with_params' suffix is applied uniformly for parameterized variants.
Seven tools is well-scoped for a database query server. It covers query execution, query explanation, schema exploration, and status without being too sparse or bloated.
The tool set covers core read operations (query, explain, describe, list) and status. Missing write operations like insert or update, which may be intentional for a read-only server, but slightly limits completeness for full database interaction.