Ask AI about local-ydb-toolkit
Open an AI assistant with product, install, MCP, and project context.Quickstart
Install the local MCP server where YDB runs
Use the hosted site for discovery and the local stdio MCP server for Docker, SSH, config files, password files, and actual local-ydb operations.
npx @astandrik/local-ydb-mcp@latestSafety model
Hosted discovery, local execution
Remote promo MCP
The remote promo MCP is read-only. It explains the product, install paths, workflows, routing guidance, and public links.
Local stdio MCP
Actual local-ydb operations stay in the local stdio MCP server. Mutating tools return a plan first and execute only when confirm: true is supplied by an approved user workflow.
Credentials stay local
Private local-ydb config files, SSH settings, password files, and database credentials stay on the user's machine or CI runner.
Agent access
Install paths for different jobs
MCP server via npx
Run the local stdio MCP server where Docker, SSH profiles, and local-ydb credentials are available.
npx @astandrik/local-ydb-mcp@latestCodex skill
Install the local-ydb skill so Codex has task-specific runbooks, topology guidance, and safety constraints.
$skill-installer install https://github.com/astandrik/local-ydb-toolkit/tree/main/skills/local-ydbGitHub Action
Bootstrap tenant, root-only, or auth-enabled local-ydb in GitHub Actions and export connection metadata for later steps.
uses: astandrik/setup-local-ydb@v1Codex Agent Plugin (repo marketplace)
Install the skill and pinned local stdio MCP server together. Requires Node.js 20.19+ and npm; use an absolute configPath or LOCAL_YDB_TOOLKIT_CONFIG because MCP starts from the plugin root.
codex plugin marketplace add astandrik/local-ydb-toolkit --ref main
codex plugin add local-ydb-toolkit@local-ydb-toolkitExternal listings
Verify package identity and metadata
Canonical GitHub Release, npm, and Official MCP Registry records define the current release. The remaining pages are dated external observations; stale, misleading, unverified, or unavailable entries are retained for transparency and are not security attestations.
Official MCP Registry
Canonical Registry record for the current published MCP server identity.
- Useful for
- Confirm the server ID, npm package, and canonical repository before installing.
Confirmed
- The published server ID is io.github.astandrik/local-ydb-mcp.
- Version 0.18.0 points to @astandrik/local-ydb-mcp and the canonical GitHub repository.
Limitations
- Registry publication confirms identity metadata; it does not verify runtime behavior or security.
ModelScope MCP Plaza
Marketplace discovery page for Local YDB MCP installation guidance.
- Useful for
- Find the marketplace installation entry and its npx stdio configuration.
Confirmed
- The marketplace entry links the canonical repository and exposes an npx stdio configuration for @astandrik/local-ydb-mcp@latest.
Limitations
- The Tools section is empty, the release version is absent, and LOCAL_YDB_MCP_CONTENT_FORMAT is missing from the environment configuration.
- The page reports Verified=false and provides no independent runtime or security validation.
mcpindex.ai
Older Registry metadata and description-drift observation for Local YDB MCP.
- Useful for
- Check install metadata and whether the public description changed between crawls.
Confirmed
- The page shows version 0.17.0 and both LOCAL_YDB_TOOLKIT_CONFIG and LOCAL_YDB_MCP_CONTENT_FORMAT.
- Its semantic screen is dated 2026-07-08.
Limitations
- The semantic screen does not cover version 0.18.0 or validate runtime behavior.
- Quality and drift labels describe directory observations, not security findings.
Guides
Answer-first pages for agents and developers
Examples
Projects using local-ydb
Coverage
Workflow summaries agents can route to tools
Diagnostics
Inventory Docker state, inspect database and tenant health, read logs, and route focused node, scheme, or GraphShard checks.
- local_ydb_inventory
- local_ydb_database_status
- local_ydb_healthcheck
Managed SQL
Run bounded YQL against the selected configured local-ydb profile: SnapshotRO query, non-executing explain, or plan-first confirmed execution.
- local_ydb_sql
Schema
Generate strict YDB table DDL, validate it through the official SDK, and apply only after explicit confirmation.
- local_ydb_generate_schema
- local_ydb_apply_schema
Auth hardening
Inspect permissions, verify auth posture, run a compatibility preflight, apply native auth by recreating configured dynamic nodes, and rotate the root password through reviewed plans.
- local_ydb_permissions
- local_ydb_auth_check
- local_ydb_prepare_auth_config
Bootstrap and lifecycle
Check prerequisites, create root or tenant topologies, bootstrap every configured node from dynamicNodeCount, and use restart or bootstrap to restore declarative topology before reviewed teardown.
- local_ydb_check_prerequisites
- local_ydb_bootstrap_root_database
- local_ydb_bootstrap
Dynamic nodes
Add or remove one-off nodes above the configured dynamicNodeCount; explicitly removing a configured suffix creates drift that restart or bootstrap restores.
- local_ydb_add_dynamic_nodes
- local_ydb_remove_dynamic_nodes
Storage
Inspect storage placement and leftovers, add or reduce groups while preserving exact one-off node ports, stop on incomplete node definitions, and clean exact reviewed targets only after verification.
- local_ydb_storage_placement
- local_ydb_storage_leftovers
- local_ydb_add_storage_groups
Backup/restore
List available dumps, dump tenant-relative paths, and restore with optional scheme and bounded count-query verification.
- local_ydb_list_dumps
- local_ydb_dump_tenant
- local_ydb_restore_tenant
Version upgrades
Discover image tags, track local_ydb_pull_status.progressPercent as monotonic layer-based progress (0-99 while running, 100 after success, last value after error; not byte progress), and upgrade while preserving exact one-off ports and stopping on incomplete node definitions.
- local_ydb_list_versions
- local_ydb_pull_image
- local_ydb_pull_status
Routing
Complementary to ydb/ydb-mcp
Use local-ydb-toolkit when the user needs to operate Docker-based local-ydb environments: prerequisite checks, bootstrap, diagnostics, managed SQL, schema DDL generation/validation/application, auth hardening, storage workflows, dump listing, path-level dump/restore, or version upgrades.
Use local_ydb_sql for bounded managed YQL against the selected configured local-ydb profile: query is SnapshotRO, explain returns plan/AST without execution, and execute stays plan-first until confirm: true.
Use ydb/ydb-mcp when the user has an arbitrary reachable YDB endpoint and needs general database-level SQL, directory listing, path inspection, or query-oriented exploration outside the configured local-ydb lifecycle context.