Skip to Content
MCP ServersOfficial vs Custom

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 are seeded into the database with their URL, icon, and authentication type. They appear under an Official section on the MCP Servers page with an Install button.

ServerAuthOAuth style
NotionOAuth 2.0DCR
AtlassianOAuth 2.0DCR
LinearOAuth 2.0DCR
SentryOAuth 2.0DCR
StripeOAuth 2.0DCR
CanvaOAuth 2.0DCR
IntercomOAuth 2.0DCR
DeepWikiNone
SupabaseOAuth 2.0DCR
AmplitudeOAuth 2.0DCR
GitHubOAuth 2.0Static credentials
HubSpotOAuth 2.0Static credentials
BigQueryOAuth 2.0Static credentials
SlackOAuth 2.0DCR

Installing an official server creates a workspace MCP server entry pointing at the correct URL with the correct auth type.

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:

FieldRequiredDescription
URLyesMCP endpoint (must support Streamable HTTP)
NameyesDisplay name
DescriptionnoShort description shown on the server card
Icon URLnoIcon displayed on the card
Auth Typeyesnone, api_key, or oauth2
API keyif api_keySent as Authorization: Bearer <key>
OAuth credsif 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