Local YDB Toolkit vs Local YDB MCP
Local YDB Toolkit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
Local YDB Toolkit is a plugin bundle for AI coding tools published by astandrik. No marketplace we read lists it any more. Local YDB MCP is an MCP server published by astandrik. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Local YDB MCP | |
|---|---|---|
| Community marketplace astandrik/local-ydb-toolkit | Removed on 2026-10-19 Version: 0.1.8 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.19.0 Downloads/month (npm): 615 Downloads/week (npm): 374 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Local YDB Toolkitno longer listed · | Local YDB MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 4 | 5 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs | On your machine (@astandrik/local-ydb-mcp) | On your machine (@astandrik/local-ydb-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository | github.com/astandrik/local-ydb-toolkit | github.com/astandrik/local-ydb-toolkit |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Local YDB Toolkit
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Deploy and run apps, workers, jobs, Postgres, and Valkey on Ownkube from your coding agent.
-
Deploy Docker Compose apps, databases, and domains on Dokploy Cloud or self-hosted.
-
Deploy local apps, add managed Postgres, and inspect logs from your AI coding agent.
-
Sealos agent skills for deploying, configuring, monitoring, and troubleshooting apps on Sealos Cloud from Claude Code. Deploy from the template store, official Docker images, or…
-
Local and cloud workflows for running ClickHouse with clickhousectl — local development (install ClickHouse, start a server, create schemas, seed data) and ClickHouse Cloud…
-
Docker and Docker Compose expert with complete documentation. Generates Dockerfiles, compose configs, database containers, SSL/TLS setup with Traefik or Nginx, and provides…
What each says it does
Local YDB Toolkit
Operate Docker-based local YDB deployments with reusable safety guidance and an optional local stdio MCP server.
Local YDB MCP
Operate local-ydb deployments through local or SSH-backed MCP tools.
How to run each
Local YDB Toolkit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Local YDB MCP As a local MCP server: npm package
claude mcp add --transport stdio local-ydb-mcp -- npx -y @astandrik/local-ydb-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Local YDB Toolkit publish no settings it asks for, so we do not compare settings.
What it can do: Local YDB Toolkit · What it can do: Local YDB MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.