gate · your own MCP gateway

Your local MCP servers — published, shared, revocable.

Your notes, your home automation, your database: MCP servers that only work on your machine. One command gives each a real URL your agents can reach from anywhere — and that you can hand to the people you choose, by email, tool by tool.

npx @browserid-ng/gate --admin you@example.com
No accounts to create, no API keys anywhere — people connect as themselves, by email
The gate admin console: an MCP server published at a shareable URL, its tools, and who can reach it The gate admin console, dark theme
Why this and not a tunnel + an API key

Exposing a local server usually means a bearer token in somebody's config — unscoped, unattributed, and revocable only by breaking everyone. Gate replaces that with identity.

People, not keys

Whoever connects signs in as themselves. Nothing to paste, nothing to leak, nothing to rotate — access is a fact about a person, not a string.

Per-server, per-tool

Roles decide exactly which tools each person gets — your partner can read your notes without being able to write them.

A real kill switch

Every call is logged with who made it and which tool they used. Cut one person off and their agent's very next call fails; nobody else notices.

Sharing

Hand your server to a person, not a key to the world.

Add someone by email, put them in a role, and check the tools that role gets — per server, per tool. They connect from their own claude.ai with their own identity; you see who did what, and you can take it back at any time without touching anyone else.

  • Works with any email they already have — Gmail included.
  • Their agent connects by URL; MCP's own sign-in flow does the rest.
  • Every call is logged: who made it, and which tool they used.
A role granting four of eight tools on one server and two of four on another, per person Role-based per-tool grants, dark theme
Five minutes, honestly

From laptop-only to anywhere.

1

Run the gateway

one command

It provisions its own identity (approve one link, first run only) and prints your console URL. With Tailscale Funnel it's public automatically at https://your-machine.ts.net — without it, gate runs locally and works with any tunnel you point at it.

2

Add a server, in the web console

name · path · command

Sign in with BrowserID — only the admin email you launched with gets in. Paste the same command you'd put in an MCP config; gate runs it and publishes it at https://<host>/<path>/mcp.

3

Copy the URL — or share it

claude.ai · phone · a friend

Add it to claude.ai as a connector and your agent has your tools everywhere you go. Grant a friend a role and the same URL works for them — as themselves, with exactly the tools you checked.

Get it

It's a hundred-kilobyte npm package that runs on your own machine, built on the open BrowserID protocol — open source (MPL-2.0), top to bottom.

npx @browserid-ng/gate --admin you@example.com
README → npm → All demos →