strad

strad is a self-hosted MCP platform. It is one endpoint in front of many MCP servers: a client asks for the servers it wants, presents a token, and strad returns exactly the tools that token is entitled to — merged, namespaced, and brokered server-side. The core ships with zero servers baked in. You attach them through a single config interface, and that config is the whole product surface.

What it does

One endpoint, many servers

A client hits https://your-strad/mcp?servers=granola,deepwiki, and strad merges those upstreams into one toolset. Every tool is namespaced server__tool, so granola__list_meetings never collides with anyone else.

The query proposes, the token disposes

?servers= can only ever narrow what a token is entitled to. It is a selection hint, never an authorization boundary — entitlement is computed server-side from the caller’s roles.

It fails closed

Ask for a server you can’t have and you get a 424 Failed Dependency naming exactly what’s missing and where to authorize — not a 401 that marches your client into a pointless OAuth loop against the gateway.

Stateless and spec-conformant

A fresh MCP server and transport is built per request and torn down when it closes. The toolset is a pure function of (token, URL), which is what keeps ?servers= conformant with the 2026-07-28 MCP spec revision.

These docs describe what was built

Everything here is re-derived from strad’s own source — the config schema, the gateway router, the auth code, and the deploy spec. Where something is a known gap or a temporary shim, it is written down, inline where it bites and aggregated on Known limitations. Read that page before you trust anything as finished.

Where to go next

What strad isThe one endpoint, the one rule, 424 fail-closed, statelessness, and why it's a platform rather than a bundle of integrations.

ArchitectureThe core gateway, internal-only bundles over the private network, App Platform, ghcr images, and GCP Secret Manager.

The server-config interfaceThe four kinds — remote-http, local-tunnel, supplementary-image, builtin — with the one-line-to-add-a-server examples.

AuthGoogle Workspace OAuth for humans, static system tokens for agents, and why the two doors never cross.

Deploy modelThe OSS repo mints the image; tadasant-internal consumes it plus its own config for prod. The zimmer→internal pattern.

Known limitationsEvery shim, gap, and piece of debt in the current build, straight from HACKS.md. Read this before you trust anything else.