Local YDB MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 144 installs a week from npm. Last commit 10 Sep 2026.
Operate local-ydb deployments through local or SSH-backed MCP tools.
We read the source, 23 h ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
specs.push(bash(`rm -rf ${shellQuote(ctx.profile.bindMountPath)}`, {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Validate published MCP and update plugin pin
id: publication
env:
RELEASE_TAG: ${{ needs.publish-existing-release.outputs.tag_name || needs.release-please.outputs.tag_name }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Local YDB MCP and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add local-ydb-mcp -- npx -y @astandrik/local-ydb-mcp
{
"mcpServers": {
"local-ydb-mcp": {
"args": [
"-y",
"@astandrik/local-ydb-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.local-ydb-mcp]
command = "npx"
args = ["-y", "@astandrik/local-ydb-mcp"]
{
"mcpServers": {
"local-ydb-mcp": {
"args": [
"-y",
"@astandrik/local-ydb-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"local-ydb-mcp": {
"args": [
"-y",
"@astandrik/local-ydb-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
LOCAL_YDB_TOOLKIT_CONFIG (Optional path to a local-ydb-toolkit config JSON file.), LOCAL_YDB_MCP_CONTENT_FORMAT (Optional LLM-facing tool response text format. Use toon to prefer TOON for the second text content block, with JSON fallback if TOON cannot round-trip losslessly; omit or set json for pretty JSON. MCP JSON-RPC and structuredContent stay JSON.).
The author declared them in the registry entry; get the values from the project itself.
Remote MCP for RunComfy: ComfyUI deployments, hosted models, LoRA training. 31 tools.
Local Sapiom developer MCP for authoring, testing, deploying, and inspecting agents.
Build, test, deploy, and operate Connic agents.
Deploy repositories or local folders to private Pocketnook URLs from any MCP client.
Mock OpenAPI specs locally, or log in to deploy hosted mocks on mockzilla.org from your MCP client.
MCP server for Node-RED — safe deploy, optimistic locking, smart search, 13 tools
Remote MCP server to integrate and validate self-hosted PayRam deployments.
Manage CloudPepper servers, Odoo instances, backups, and deployments over MCP.
Answers built from our own checks of this server.