Labby
ai.dinglebearPublished by dinglebear.aiv2.6.2Updated Oct 26, 2026
Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.
The publisher's own server: Tailscale RMCP
Overview
Labby is a local Rust-based MCP gateway with a Code Mode, authentication, setup, logs, CLI, HTTP API and operator web UI, run via npx.
- What you can do
- Acts as a gateway that fronts MCP servers, with a Code Mode for working with them.
- Handles authentication and initial setup for the gateway.
- Exposes logs and a command-line interface for operating it.
- Offers an HTTP API and an operator web UI for management.
- Downloads a Labby binary from GitHub release assets at startup.
- When to use it
- Worth considering if you want a single local gateway to manage and operate several MCP servers, with authentication, logging and a web UI, rather than wiring each server into the assistant separately.
- Requirements
- Runs as a local process on the user's machine, started with npx from the npm package @dinglebear/labby over stdio; desktop only, not web-executable. It downloads a Labby binary from GitHub release assets, so network access to GitHub is needed. Optional environment variables LABBY_LOG, LABBY_REPO and LABBY_VERSION adjust logging and which release asset is fetched. No authentication is declared in the manifest.
Installation
In SourceWeft
- Open Labby in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
6- v2.6.2LatestOct 10, 2026
- v2.6.0Oct 4, 2026
- v2.5.0Oct 2, 2026
- v2.3.2Sep 25, 2026
- v2.2.1Sep 23, 2026
- v1.20.1Sep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Dinglebear integrations
Tailscale RMCP
ai.dinglebearOfficial publisher
Bridges a Tailscale tailnet to an assistant: list devices, inspect routes, DNS, ACLs, keys and users, and authorize or delete devices.
Yarr MCP
ai.dinglebear
MCP and CLI server that lets an assistant query and control a self-hosted media stack such as Sonarr, Radarr, Prowlarr, Plex and Jellyfin.
Yarr MCP
ai.dinglebear
MCP server and CLI that gives an assistant one consistent tool surface to query and control a self-hosted media fleet such as Sonarr, Radarr and Plex.
Unraid MCP
ai.dinglebear
Python MCP server that lets an assistant query and manage an Unraid server through its GraphQL API.
Soma
ai.dinglebear
Soma is a local Rust runtime that exposes one compact MCP tool, letting an assistant call built-in actions and dropped-in provider tools over stdio or HTTP.