Labby
Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.
Canonical remote: git@github.com:dinglebear-ai/labby.git.
The root README is the public entrypoint. The topic docs in docs/ own the detailed contracts; when this file and a topic doc disagree, fix the topic doc first and then refresh this summary.
Contents
- What Labby Does
- Quick Start
- Core Workflows
- Runtime Surfaces
- Configuration
- Current Catalogs
- Architecture
- Development
- Documentation
What Labby Does
Labby is centered on the current gateway/operator surface:
- MCP gateway - connect HTTP and stdio upstream MCP servers, inspect their
tools/resources/prompts, apply exposure filters, publish protected MCP routes, and optionally collapse the upstream catalog into Code Mode search and execute.
- Direct stdio proxy - launch one stdio MCP server with
labby proxy /path/to/dist.js and expose its unmodified MCP surface over loopback or an owned Tailscale Serve HTTPS port with tailnet, bearer, OAuth, or explicit no-auth policy.
- Authentication and protected routes - run bearer or OAuth authentication,
manage route-scoped access, authorize upstream OAuth connections, and publish protected MCP endpoints.
- Code Mode snippets - author, store, and run reusable JavaScript snippets
against the upstream catalog, with artifacts persisted under $LABBYHOME.
- Setup and doctor - bootstrap ~/.labby, provision the host service, and