Local YDB MCP
Related Servers
Alternatives to Local YDB MCP
AlicenseBqualityAmaintenanceModel Context Protocol server for YDB databases that enables AI-powered database operations and natural language interactions with YDB instances from any LLM that supports MCP.729Apache 2.0
Related Servers
- FlicenseNot gradedqualityDmaintenanceA TypeScript server that fully implements the Model Context Protocol (MCP) standard, providing API access to Docker CLI operations like build, run, stop, and image management through compatible AI clients.-
- AlicenseBqualityDmaintenanceProduction-ready TypeScript MCP server exposing utility, GitHub, and Microsoft Teams tools over stdio.141MIT
- FlicenseNot gradedqualityDmaintenanceA demonstration MCP server built in TypeScript that shows how to implement stdio-based communication for integration with MCP clients. Serves as a template for building custom MCP servers with strong typing and maintainability.-
- FlicenseAqualityDmaintenanceA TypeScript MCP server for launching, tracking, and managing external coding-agent runs across local and remote backends like Codex and Claude Code. It allows top-level agents to orchestrate subagents through tools for spawning tasks, polling events, and handling interactive sessions.72-
- FlicenseBqualityDmaintenanceA basic TypeScript implementation of the Model Context Protocol (MCP) server designed as a starting point for MCP development. Provides a minimal foundation for building custom MCP servers with stdio configuration for local integration with VS Code and GitHub Copilot.1-
- AlicenseAqualityAmaintenanceUniversal Docker MCP server for AI assistants (Cursor, Claude Desktop). Manage Docker containers, execute commands, query databases, and handle environment configurations — all through natural language.10140 npmMIT
TDQS
Scored across 39 tools
Each tool targets a distinct resource and action, and the descriptions explicitly cross-reference related tools (e.g., database_status vs tenant_check vs healthcheck; bootstrap vs bootstrap_root_database; start_dynamic_node vs add_dynamic_nodes). Even the many check/status tools are separated by clear purpose and usage guidance.
All tools share the local_ydb_ prefix and snake_case, and most mutations follow verb_noun (add_storage_groups, restore_tenant, set_root_password). A few read-only tools are bare nouns or noun phrases (inventory, healthcheck, scheme, sql, permissions, storage_placement), so the verb_noun pattern is not universal but remains readable.
39 tools is well beyond the 16-25 heavy band and the typical 3-15 well-scoped range. Although the domain is broad and the tools are individually distinct, the size makes the surface difficult for an agent to navigate efficiently, especially when status_report already aggregates several checks.
The set covers the full local YDB lifecycle: prerequisites, image management, bootstrap, tenants, dynamic nodes, schema/SQL, permissions, auth hardening, storage, dumps/restore, upgrade, restart, destroy, and diagnostics. Minor gaps include no stop-only operation and limited user/tenant management beyond the configured profile, but these can be worked around with SQL or bootstrap/destroy.