mcpbeat Sign in

Labby MCP Server

local only

Labby runs on your own machine — the client starts it, so there is no endpoint to ping. 303 installs a week from npm. Last commit 31 Oct 2026.

Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.

Installs per day peak 300 · avg 54 · +209% w/w
a month agotoday
303
Installs / week
npm · @dinglebear/labby
9
Stars
22 open issues
31 Oct 2026
Last commit
13 releases in 90 days
AGPL-3.0
License
Rust

What the code does

We read the source, 1 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1
postinstall: node scripts/install.js
Package points at a different repository dinglebear-ai/labby
пакет labby-mcp ссылается на jmagar/labby
  const install = spawnSync(process.execPath, [installer], { stdio: "inherit" });
In the project's build, not in the package

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.

  depotProcess=spawn('mise',['exec','--','mix','run','--no-start',boot],{cwd:depotRoot,stdio:'ignore',env:{PATH:process.env.PATH,MISE_DATA_DIR:process.env.MISE_DATA_DIR||path.join(os.homedir(),'.local/share/mise'),HOME:root,MIX_ENV:'dev',DEPOT_DATA_DIR:path.join(root,'depot-data'…
Builds a database query by concatenation crates/labby/src/file_stash/schema.rs:126
…id,reserved_bytes,pending_files) VALUES(NEW.owner_principal_id,NEW.reserved_bytes,1) ON CONFLICT(owner_principal_id) DO UPDATE SET reserved_bytes=reserved_bytes+NEW.reserved_bytes,pending_files=pending_files+1; UPDATE stash_instance_usage SET reserved_bytes=reserved_bytes+NEW.res…
…nt=spec?spec.label:"Settings";sectionDescription.textContent=spec?spec.description:"";const list=currentFields();fields.innerHTML=list.length?list.map(f=>{const source=state&&state.sources&&state.sources[f.key];return `<article class="field"><div><div class="label">${esc(f.label)…
        std::fs::write(root.join(".ssh/id_rsa"), "key").unwrap();
  const env = Object.fromEntries(Object.entries(process.env).filter((entry): entry is [string, string] => entry[1] !== undefined))

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

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.

run in your terminal
claude mcp add labby -- npx -y @dinglebear/labby
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "labby": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/labby"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.labby]
command = "npx"
args = ["-y", "@dinglebear/labby"]
.cursor/mcp.json
{
  "mcpServers": {
    "labby": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/labby"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "labby": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/labby"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: LABBY_VERSION (Optional GitHub release tag override for the downloaded Labby binary), LABBY_REPO (Optional GitHub owner/repo override for release asset downloads), LABBY_LOG (Tracing filter for Labby runtime logs).

Alternatives to Labby

same job, measured the same way
Codex / OpenAI Image
by meet30997

Generate, edit and make matching sets of images with the Codex CLI or the OpenAI Images API

686 installs/wk local only
Perforce Agentic Gateway
by perforce

Local MCP gateway that proxies AI clients to many MCP servers with a token-efficient code mode

246 installs/wk local only
Heroku Code MCP
by dsouzaanush

Search and execute Heroku Platform API operations

local only
TokenZero
by tokenzero

LLM cost optimization gateway, repo token-waste auditor & model arbitrage MCP server.

3 345 installs/wk 6 tools answering
TokenZero
by tokenzero-ai

LLM cost optimization gateway, repo token-waste auditor & model arbitrage MCP server.

6 tools answering
CodeAtlas
by com-codeatlas

Read-only CodeAtlas service catalog: list, get and search services. No authentication.

4 tools answering
Codex ServerOps MCP
by cyyprezz

Stateful Windows OpenSSH server operations for Codex with local credential handling.

110 installs/wk local only
CodeInspectus
by synvoya

Local-first MCP security scanner and CLI for AI-generated applications.

211 installs/wk local only

Labby — questions

Answers built from our own checks of this server.

Why is there no uptime for Labby?
Labby runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @dinglebear/labby was installed 303 times last week.
How do I connect Labby?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @dinglebear/labby straight from npm; nothing to host, nothing to sign up for.
How many people use Labby?
The npm package @dinglebear/labby was installed 303 times in the last week. Week over week that is +209%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Labby open source?
Yes — it is published under the AGPL-3.0 licence, written in Rust, 9 stars on GitHub and 22 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.