Connector Catalog
The catalog (Governance → MCP Gateway → Catalog) is a curated directory of 160+ MCP upstreams: productivity (Notion, Linear, Asana, Monday), communication (Slack, Intercom), data (Snowflake, Databricks, Mixpanel, Amplitude), finance (Stripe, Ramp, Brex, FactSet, Moody's, PitchBook), dev tools (Sentry, Postman, Supabase, Vercel), and more — alongside any custom upstreams your team adds.
Reading the badges
| Badge | Meaning | Setup required |
|---|---|---|
| Auto OAuth (green) | The vendor's server implements the MCP authorization spec — endpoints are discovered and a client is registered automatically | None. Install, then each user clicks Connect |
| Open (blue) | Open server, no authentication at all (e.g. Microsoft Learn, PubMed, AWS Marketplace) | None. Install and it works |
| No setup | Waxell-substrate upstream — your existing Waxell auth flows through | None |
| (no badge) | Classic OAuth or token-based — a platform admin registers credentials first | Admin setup, see Authentication |
| Verified | A human has connected this upstream and confirmed real tools respond | — |
Entries without the Verified badge are probe-verified (the endpoint advertises the right protocol) but haven't had a human smoke test yet. They generally just work; the badge tells you someone proved it.
Three steps, three roles
Install — admin, once per tenant
Catalog → connector → Install. This copies the template into your tenant's upstream registry. For Auto OAuth and Open connectors there is nothing to configure — no client IDs, no secrets, no vendor developer consoles. The gateway picks up new installs within about a minute.
Connect — each user, once
Per-user OAuth upstreams run calls as the individual user, so each person authorizes their own account: Governance → MCP Gateway → Connections → Connect. A vendor sign-in window opens; approve and you're done. Open-badge connectors skip this entirely.
This per-user model is the point: when an agent acting for Alice writes to Notion, it writes as Alice, with Alice's permissions, attributed to Alice in both Notion's audit log and Waxell's.
Verify — see your tools
Governance → MCP Gateway → My Tools shows which upstreams are live for you, with a Refresh button that forces a fresh tool discovery against the upstream. The tenant-wide view (every tool, regardless of your connections) is at → Registry.
Custom upstreams
Any MCP server — internal or vendor — can be added directly at Governance → MCP Gateway → Upstreams without a catalog entry: name, URL, auth mode. If the server implements the MCP authorization spec, pick MCP OAuth and it self-configures exactly like an Auto OAuth catalog entry. Stdio (subprocess) upstreams are supported for self-hosted gateways.
Tags
Upstreams carry free-form tags (crm, data, support, …) used by tool subsetting to control which tools pre-load into which agents' context.