mcpdirectory.dev
9,129 servers · updated 23 Sept

Labby MCP server

community Active last commit 12 d
{
  "mcpServers": {
    "dinglebear-labby": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/labby@latest"
      ],
      "env": {
        "LABBY_MCP_HTTP_TOKEN": "<labby_mcp_http_token>",
        "LABBY_SERVER_URL": "https://...",
        "LABBY_GOOGLE_CLIENT_SECRET": "<labby_google_client_secret>",
        "LABBY_PUBLIC_URL": "https://...",
        "LABBY_GOOGLE_CLIENT_ID": "<labby_google_client_id>",
        "LABBY_AUTHELIA_ISSUER_URL": "https://..."
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @dinglebear/labbyversion 1.20.1

What it does

Labby is a Rust MCP gateway that connects upstream MCP servers (HTTP and stdio) and exposes their tools, resources, and prompts over protected routes. It offers authentication (bearer, OAuth, Tailscale), a web UI for operators, CLI tools, HTTP API access, and Code Mode for running JavaScript snippets against the catalog.

  • Proxy a single stdio MCP server to loopback or Tailscale Serve with authentication and route-scoped access control.
  • Inspect and filter tools, resources, and prompts from multiple upstream MCP servers through a single gateway.
  • Author and run reusable JavaScript snippets against the upstream MCP catalog with persisted artifacts.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.