Labby
Local-first Rust gateway for connecting, filtering, securing, and operating MCP servers through CLI, HTTP, and web interfaces.
Install Labby
Pick your client, then add it in one click or paste the config.
~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"labby": {
"command": "npx",
"args": [
"-y",
"@dinglebear/labby"
]
}
}
}
Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.
Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.
Overview
Use cases
- Connect HTTP and stdio MCP servers behind one gateway
- Filter upstream tools before exposing them to clients
- Protect MCP routes with bearer or OAuth authentication
- Proxy a single stdio MCP server over loopback or Tailscale
- Audit gateway health, configuration, and local server logs
Key features
- HTTP and stdio MCP gateway
- Direct stdio proxy mode
- Bearer and OAuth route protection
- Code Mode search and execute
- Scoped filesystem operations
- CLI, HTTP API, and operator web UI
How Labby works
Security & health
What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.
ActiveLast checked 5d ago
Recent health check succeeded.
16/16 checks healthy over the last 67d
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 12d ago via OSV.dev · @dinglebear/labby (npm)
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars8Stargazers on the source repository.
npm downloads2.6kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Reviews
No reviews yet — be the first to share how it worked for you.
Frequently Asked Questions about Labby
Labby is an MCP server that connects HTTP and stdio upstream MCP servers through a Rust gateway. Its main tools and services include gateway routing, direct stdio proxying, Code Mode search and execute, protected routes with bearer or OAuth authentication, scoped filesystem actions, setup checks, and local server-log access.
Install it with the reviewed `labby-install.sh` script, then run the documented setup flow. The README also provides an npm launcher using `npx -y @dinglebear/labby mcp` and an Agent Package Manager option. Installation alone is not complete onboarding; native service setup and first-use checks still need to pass.
The provided README does not specifically name Cursor. It describes Labby as exposing stdio and HTTP MCP surfaces and says the setup interface can register selected supported clients, but it does not establish Cursor-specific configuration or support details.
Yes. Labby supports OAuth authentication for protected routes and can authorize upstream OAuth connections. It also supports bearer authentication, route-scoped access, and an explicit no-auth policy for the direct stdio proxy in the documented deployment options.
Yes. Direct proxy mode launches one stdio MCP server, such as with `labby proxy /path/to/dist.js`, and exposes its unmodified MCP surface over loopback or an owned Tailscale Serve HTTPS port.
Related MCP servers
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/labby)HTML Embed
<a href="https://allmcps.com/mcp/labby"><img src="https://allmcps.com/api/badge/labby?style=directory" alt="Labby on AllMCPs" /></a>