Labby MCP Server

Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI. It runs locally over stdio via the published package.

People connecting automation tools to Claude, Cursor, VS Code, or another MCP client. The project is written in Rust.

VERIFIED ACTIVE

LAST COMMIT 2026-08-24 · ★ 5 · #44 OF 194 MAINTAINED AUTOMATION · VERIFIED 2026-08-25

AGPL-3.0 · Rust servers · how we verify → /methodology

01 · Install Labby

before you install - you'll need

The README does not document required environment variables for a basic install.

Claude Code

claude mcp add dinglebear-ai-labby -- npx -y @dinglebear/labby

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "dinglebear-ai-labby": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/labby"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license AGPL-3.0 - declared in the repository

npm package @dinglebear/labby - the @dinglebear scope differs from the repo owner (dinglebear-ai); confirm it's the project's official package

registry vendor namespace ai.dinglebear - domain-verified with the official MCP registry

03 · What Labby can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v1.13.3 · 2026-08-18

1.13.3 (2026-08-18) · Fixed · stop unsupported subscription retries · refresh patched Debian base packages

labby-incus-latest · 2026-06-29

Rolling pointer to v1.13.3 from 3818875d422dd46adb4c5cdeb44d85a19c0d2db2.

v1.13.1 · 2026-08-15

1.13.1 (2026-08-15) · Fixed · surface nested apps from Code Mode

04 · Who maintains Labby

Labby is maintained by dinglebear-ai. We track 11 MCP servers from dinglebear-ai - 11 actively maintained, 33 combined GitHub stars, oldest repo from Mar 2026. Full record: all servers from dinglebear-ai.

05 · Facts

repository: github.com/dinglebear-ai/labby
website: https://github.com/dinglebear-ai/labby
category: automation - ranked #44 of 194 actively-maintained automation servers as of 2026-08-25.
release cadence: 10+ releases in the last 90 days (latest 2026-08-18)
registry: ai.dinglebear/labby (active, first published 2026-07-12 · 5 versions)
packages: npm:@dinglebear/labby

06 · Labby FAQ

What is Labby?

Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI. It runs locally over stdio via the published package.

Is Labby still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-24 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Labby?

Run `npx -y @dinglebear/labby`. The README does not document required environment variables for a basic install. You can also paste the ready-made client config above.

Does Labby run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Labby

Alternatives to Labby

Maintained automation servers if Labby isn't the fit.

More automation MCP servers · Apprise RMCP · UniFi RMCP (dinglebear-ai) · Yarr MCP (dinglebear-ai) · Computer Use · Dotted Sign

More Rust MCP servers · Synapse RMCP (dinglebear-ai) · Memory Rs · see all