Operate local-ydb deployments through local or SSH-backed MCP tools.
Local YDB MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Operate local-ydb deployments through local or SSH-backed MCP tools.
Toolkit for operating local-ydb deployments across Codex, MCP clients, and GitHub Actions CI.
Once Local YDB MCP is connected, these are the calls the assistant has available:
Checks — The Checks tool exposed by this serverSchema — The Schema tool exposed by this serverAuth — The Auth tool exposed by this serverStorage — The Storage tool exposed by this serverLifecycle — The Lifecycle tool exposed by this serverOperations — Read-only tools collect inventory, tenant state, YDB healthcheck/self-check output, schema objects, generated table DDL, schema permissions, node@astandrik/local-ydb-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 3 environment variables: LOCAL_YDB_TOOLKIT_CONFIG, LOCAL_YDB_MCP_CONTENT_FORMAT, LOCAL_YDB_MONITORING_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Local YDB MCP's toolset — Checks, Schema, Auth and 3 more — is a fair guide to whether it matches your workflow. It is maintained by astandrik; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Checks | The Checks tool exposed by this server. |
| Schema | The Schema tool exposed by this server. |
| Auth | The Auth tool exposed by this server. |
| Storage | The Storage tool exposed by this server. |
| Lifecycle | The Lifecycle tool exposed by this server. |
| Operations | Read-only tools collect inventory, tenant state, YDB healthcheck/self-check output, schema objects, generated table DDL, schema permissions, node state, GraphShard state, auth posture, storage placement, leftover storage |
{
"mcpServers": {
"local-ydb": {
"command": "npx",
"args": ["-y", "--prefer-online", "@astandrik/local-ydb-mcp@latest"],
"env": {
"LOCAL_YDB_TOOLKIT_CONFIG": "/path/to/local-ydb.config.json",
"LOCAL_YDB_MCP_CONTENT_FORMAT": "toon"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOCAL_YDB_TOOLKIT_CONFIG | Configuration value read at startup. | Optional |
| LOCAL_YDB_MCP_CONTENT_FORMAT | Configuration value read at startup. | Optional |
| LOCAL_YDB_MONITORING_URL | Endpoint or connection string the server talks to. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.