Official vs Custom MCP Servers
auxilia distinguishes two categories of MCP servers: official (pre-configured in the catalog) and custom (user-registered by URL).
Official MCP servers
Official servers come from a catalog auxilia hosts as a single file, listing each server’s URL, icon, and authentication type. Click Add MCP server to search the catalog and pick one — it prefills the form for you. Servers your workspace already runs are left out of the list.
| Server | Auth | OAuth style |
|---|---|---|
| Amplitude | OAuth 2.0 | DCR |
| Atlassian | OAuth 2.0 | DCR |
| BigQuery | OAuth 2.0 | Static credentials |
| Calendar | OAuth 2.0 | Static credentials |
| Canva | OAuth 2.0 | DCR |
| DeepWiki | None | — |
| Drive | OAuth 2.0 | Static credentials |
| Gmail | OAuth 2.0 | Static credentials |
| GitHub | OAuth 2.0 | Static credentials |
| HubSpot | OAuth 2.0 | Static credentials |
| Intercom | OAuth 2.0 | DCR |
| Kahoot | OAuth 2.0 | DCR |
| Linear | OAuth 2.0 | DCR |
| Notion | OAuth 2.0 | DCR |
| PandaDoc | OAuth 2.0 | DCR |
| Pennylane | OAuth 2.0 | DCR |
| Praiz | OAuth 2.0 | DCR |
| Sentry | OAuth 2.0 | DCR |
| Slack | OAuth 2.0 | Static credentials |
| Stripe | OAuth 2.0 | DCR |
| Supabase | OAuth 2.0 | DCR |
| Tavily | API key | — |
Installing an official server creates a workspace MCP server entry pointing at the correct URL with the correct auth type.
Keeping the catalog current
Because the catalog is a hosted file rather than part of the release, new servers become available without upgrading auxilia — but the file is cached, so an admin decides when to pull changes in: Sync catalog on the MCP Servers page fetches it immediately and reports what changed. A malformed or unreachable file changes nothing; the last known-good catalog keeps being served.
Self-hosted deployments can point MCP_CATALOG_URL at their own file to publish an internal list of approved servers instead, or set it empty to pin the catalog bundled with the release.
DCR servers
Servers that support Dynamic Client Registration handle OAuth automatically. When a user clicks Connect, auxilia registers itself as an OAuth client on the fly — no client ID or secret needed.
Static-credential servers
Some providers (GitHub, HubSpot, BigQuery, …) require you to register an OAuth application yourself in their dashboard and supply the client ID and secret to auxilia at install time.
See the step-by-step guides:
Custom MCP servers
You can add any remote MCP server by URL. Click Add MCP Server and fill in:
| Field | Required | Description |
|---|---|---|
| URL | yes | MCP endpoint (must support Streamable HTTP) |
| Name | yes | Display name |
| Description | no | Short description shown on the server card |
| Icon URL | no | Icon displayed on the card |
| Auth Type | yes | none, api_key, or oauth2 |
| API key | if api_key | Sent as Authorization: Bearer <key> |
| OAuth creds | if oauth2 (and no DCR) | Client ID + Secret |
When to use a custom server
- Self-hosted MCP servers inside your own infrastructure
- MCP servers not yet in the official catalog
- Static API-key servers (not in the official list)
- Temporary / experimental servers