MCP comparison

local-ydb-mcp vs ydb-platform/ydb-mcp

Use local-ydb-mcp for operating Docker-based local-ydb environments, including managed YQL against the selected configured profile. Use the official ydb-platform/ydb-mcp server for general database-level work against arbitrary reachable YDB endpoints.

Use @astandrik/local-ydb-mcp for

Docker inventory, local-ydb readiness, YDB healthcheck, tenant state, node registration, GraphShard checks, auth posture, storage placement, and logs.
Root /local bootstrap or CMS tenant bootstrap with dynamic nodes.
YDB table DDL generation, validation, plan-only application, and confirmed application.
Managed YQL with local_ydb_sql: SnapshotRO query, non-executing explain, or plan-first confirmed execution.
Auth hardening, dump listing, path-level dump/restore, storage group workflows, cleanup, and version upgrades.

Use ydb-platform/ydb-mcp for

General SQL and query exploration against an arbitrary already running YDB endpoint.
Database-level directory listing, path inspection, and query-oriented exploration.
General YDB interaction that does not need Docker local-ydb lifecycle control.

Safety model

@astandrik/local-ydb-mcp is plan-first: mutating tools return planned commands, risk, rollback, and verification unless the caller supplies confirm: true. That matters when an agent can touch containers, volumes, auth files, storage pools, and dumps.