GateOSSign in

One gate in front of every MCP server.

GateOS is a self-hosted gateway between your MCP clients and the servers they use. Connect Notion, GitHub, or anything that speaks MCP once — then hand each person a scoped credential instead of the keys.

Sign inSee how it works

How it works

  1. 1

    Connect an upstream

    Register any MCP server with its own credentials. They are sealed with AES-256-GCM before they ever touch the database.

  2. 2

    Mint a gateway credential

    Issue a token per person or per app. Shown once, stored as a SHA-256 verifier, revocable in one click.

  3. 3

    Point your client at the gate

    Tools arrive namespaced as connection__tool — nothing collides, and every call lands in the audit trail.

What the gate enforces

Per-user isolation
Connections and credentials belong to one account. Sessions are bound to users and the gate enforces it per request, not by convention.
Hardened egress
Every upstream connection passes a scheme and port policy plus a DNS-level SSRF filter before it leaves the building.
Full audit trail
Sign-ins, credential issues, tool calls — the activity feed records who did what, and when.
Any MCP client
Claude, Cursor, or your own code. The gate speaks MCP over Streamable HTTP; there is nothing client-side to install.

Under the hood

AES-256-GCM

Envelope encryption with an external master key.

256-bit tokens

CSPRNG-issued, stored as SHA-256 verifiers, shown once.

Rate limited

Per-token limits and a 1 MiB body cap on /mcp.

Origin checked

Origin validation and session binding on the endpoint.

Your servers are already speaking MCP. Put a gate in front of them.

Sign in