Service catalog
Authoritative metadata lives in config/connectors.json. Runtime overrides (resource mapping, identity helpers) live in config/overrides/<name>.ts and are wired in server/utils/connector-loader.ts.
Adapters are registered at boot in server/plugins/init.ts. OAuth entrypoints for members sit under server/routes/oauth/. Some vendors add dedicated callback routes (e.g. Sentry-specific files alongside generic connect handlers).
Connector keys in this repository
| Key | Label (display) |
|---|---|
github | GitHub |
slack | Slack |
linear | Linear |
notion | Notion |
stripe | Stripe |
supabase | Supabase |
vercel | Vercel |
hubspot | HubSpot |
airtable | Airtable |
planetscale | PlanetScale |
atlassian | Atlassian |
sentry | Sentry |
cloudflare | Cloudflare |
prowler | Prowler |
huggingface | Hugging Face |
google |
Upstream URLs default per connector file but are overridden in deployment through Nuxt runtime settings that mirror the configKey fields in JSON (for example MCP base URL env names derived in nuxt.config.ts). Treat shipped defaults in the repo as examples, not as promises about your production routing—especially for connectors that rely on your own hosted MCP bridge.
Tool listings for policy UX come from each connector’s tools array; GET /api/tools/catalog aggregates. GET /api/connectors/meta exposes display metadata to the SPA.
GitHub specifics
GitHub combines user OAuth, optional GitHub App installation flows, and Copilot-class MCP endpoints. See GitHub App for installation APIs; credential headers for App-mode traffic are described in connector definitions.