Labby — Claude Code MCP server: what it does, how to install
Labby routes HTTP and stdio MCP servers through one gateway. Use it to filter exposed tools, protect routes, and run Code Mode actions.
claude mcp add --env LABBY_VERSION=<LABBY_VERSION> --env LABBY_REPO=<LABBY_REPO> --env LABBY_LOG=<LABBY_LOG> --transport stdio labby -- npx -y @dinglebear/labbyWhat Labby does
Labby is a Rust gateway for upstream MCP servers. It accepts HTTP and stdio connections, inspects available tools, resources, and prompts, applies exposure filters, and publishes protected MCP routes. The upstream catalog can also be reduced to Code Mode operations built around search and execute.
The package includes bearer and OAuth authentication, host setup, health checks, a CLI, an HTTP API, an operator web UI, and logs for labby serve. It can launch a single stdio server with labby proxy, expose scoped filesystem actions, and keep reusable JavaScript snippets under $LABBY_HOME.
Installing the binary does not finish onboarding. You still need to connect an agent provider, choose a discovered model, complete the starter Agent test, and register the client. The installer requires curl, tar, and sha256sum or shasum; macOS setup also uses unzip.
What it helps with
- route HTTP and stdio MCP servers through one gateway
- filter which upstream tools and resources are exposed
- secure MCP routes with bearer or OAuth authentication
- reduce an upstream catalog to Code Mode actions
- search and follow the
labby servelog stream
Example prompts for the agent
- Connect an upstream MCP server and inspect its tools, resources, and prompts.
- Expose the catalog through Code Mode, then find and run an action with
searchandexecute. - Check the gateway health and inspect recent errors from
labby serve.
How to install Labby
Platform CLI
claude mcp add --env LABBY_VERSION=<LABBY_VERSION> --env LABBY_REPO=<LABBY_REPO> --env LABBY_LOG=<LABBY_LOG> --transport stdio labby -- npx -y @dinglebear/labbyReplace <…> with your own values
Platform CLI
codex mcp add labby --env LABBY_VERSION=<LABBY_VERSION> --env LABBY_REPO=<LABBY_REPO> --env LABBY_LOG=<LABBY_LOG> -- npx -y @dinglebear/labbyReplace <…> with your own values
Config file
{
"mcpServers": {
"labby": {
"command": "npx",
"args": [
"-y",
"@dinglebear/labby"
],
"env": {
"LABBY_VERSION": "<LABBY_VERSION>",
"LABBY_REPO": "<LABBY_REPO>",
"LABBY_LOG": "<LABBY_LOG>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"labby": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dinglebear/labby"
],
"env": {
"LABBY_VERSION": "<LABBY_VERSION>",
"LABBY_REPO": "<LABBY_REPO>",
"LABBY_LOG": "<LABBY_LOG>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e LABBY_VERSION=<LABBY_VERSION> -e LABBY_REPO=<LABBY_REPO> -e LABBY_LOG=<LABBY_LOG> labby npx -y @dinglebear/labbyReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Labby
How do I install Labby in Claude Code?
Run claude mcp add labby -- npx -y @dinglebear/labby. Then complete Labby’s required setup checks in the browser flow.
What does Labby do?
Labby joins HTTP and stdio MCP servers behind a gateway, filters their exposed surface, and publishes protected routes. It also provides Code Mode, authentication, a CLI, and server logs.
What is required after installing Labby?
Connect an agent provider, select a discovered model, complete the starter Agent test, and register supported clients. Installing the binary alone does not complete onboarding.
