local-ydb-toolkit MCP server

This is a helper for people who run a local YDB database inside Docker on their own computer or on a server they reach over SSH. It lets your AI assistant do the boring setup and checking work for you, like starting the database, looking at logs, and taking backups. It is handy if you already work with YDB and want less typing.

What this MCP server does

You ask your AI something like check if my local YDB is healthy. The AI uses this helper, which runs commands against your Docker setup or over SSH to a remote machine. The helper talks to Docker and to the YDB database, gathers the answers, and hands them back to the AI. The AI then explains the result to you in the chat. Anything that changes your database is done in two steps: first a plan, then a confirmation.

Click to zoom

What you can do with it

• Check whether your local YDB Docker containers are running
• Look at recent container logs when something fails
• Run a health check on your database and see the issues
• Generate or apply table creation scripts
• Dump and restore your database data
• Add or remove dynamic nodes
• Upgrade your local YDB to a newer version

Try asking your AI

• “Check the status of my local YDB setup”
• “Show me the last 100 lines of the container logs”
• “Run a health check on the tenant /local/test”
• “List the available versions of the local-ydb image”

What it gives back to you

You get back plain answers in the chat: whether things are healthy, lists of containers or nodes, log excerpts, generated SQL scripts, and short summaries of what was found. For changes, you first see a plan describing what would happen, and nothing runs until you confirm. After a confirmed change, you get a short report of what was done.

Before you start

Who it's for

Developers and database people who run a local YDB in Docker and want their AI assistant to handle the routine setup, checks, and backups.