Sign In

@dinglebear/labby

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@dinglebear/labby - npm Package Compare versions

Comparing version
1.8.6
to
1.8.8
+1
-1
package.json
{
"name": "@dinglebear/labby",
"version": "1.8.6",
"version": "1.8.8",
"description": "Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.",

@@ -5,0 +5,0 @@ "license": "MIT OR Apache-2.0",

@@ -31,2 +31,6 @@ # Labby

`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,

@@ -45,3 +49,4 @@ manage route-scoped access, authorize upstream OAuth connections, and publish

- **Generated discovery** - publish code-owned service, action, environment,
API route, OpenAPI, MCP help, CLI help, and feature-matrix artifacts under
proxy configuration, API route, OpenAPI, MCP help, CLI help, and
feature-matrix artifacts under
[docs/generated](./docs/generated/README.md).

@@ -59,2 +64,27 @@

### Proxy One Stdio MCP Server
After installing Labby, configure proxy defaults once and launch a JavaScript
stdio server without proxy flags:
```bash
labby setup proxy
labby doctor proxy
labby proxy /path/to/dist.js
```
The built-in zero-flag policy is Tailscale Serve plus tailnet authorization on
a random high port. Child flags follow the first child token unchanged, and an
explicit separator is available for unusual commands:
```bash
labby proxy /path/to/dist.js --workspace /srv/data --read-only
labby proxy -- npx -y @modelcontextprotocol/server-filesystem /srv/data
```
Use `labby proxy --local --auth none ...` for explicit loopback-only
development. Bearer and OAuth setup, exact-port resource audiences, safe Serve
ownership, configuration precedence, output modes, and recovery are covered in
the [stdio MCP proxy guide](./docs/guides/STDIO_MCP_PROXY.md).
### Install A Release

@@ -250,3 +280,5 @@

labby doctor auth # auth/OAuth env vars, files, permissions
labby doctor proxy # public Lab and protected MCP proxy endpoints
labby doctor proxy # zero-route stdio-proxy config/dependency preflight
labby doctor proxy --app-url URL --mcp-url URL --route /path
# routed public reverse-proxy checks remain available
labby doctor oauth-relay

@@ -253,0 +285,0 @@ labby health # lightweight liveness/readiness probe