MCP OAuth clients
You can use the Polytomic MCP server with on-premises deployments. By default, Polytomic accepts any MCP client that identifies itself in one of two ways:
- Client ID Metadata Document (CIMD). The client's ID is an HTTPS URL that serves a JSON document describing the client. Polytomic fetches that document when a user signs in. Claude identifies itself this way.
- Dynamic Client Registration (DCR). The client registers itself by calling
/oauth/registeron your Polytomic URL. Registration doesn't grant access. The user must still sign in and approve the connection.
You can turn either method off, or accept only the CIMD clients you list. These settings affect OAuth sign-in only. Users can still connect with a Polytomic API key, using the Polytomic Connector or manual configuration.
Release requirementThese settings require Polytomic release
rel2026.10.21.02or later.
Settings
| Variable | Default | Effect |
|---|---|---|
OAUTH_DCR_DISABLED | false | When true, /oauth/register returns 404 and the OAuth discovery metadata no longer lists a registration endpoint. Polytomic rejects every client that registered through DCR, including clients that registered before you changed the setting. |
OAUTH_CIMD_CLIENT_IDS | empty (any client) | A comma-separated list of CIMD client ID URLs that may sign in. Polytomic rejects other client IDs without fetching their documents. URLs must match exactly, including any trailing slash. |
OAUTH_CIMD_DISABLED | false | When true, Polytomic rejects every CIMD client, and the discovery metadata reports that CIMD isn't supported. |
Mutually exclusive settingsYou can't use
OAUTH_CIMD_DISABLEDandOAUTH_CIMD_CLIENT_IDStogether. Polytomic doesn't start if both are set.
Allow only Claude
Claude uses two client IDs:
https://claude.ai/oauth/mcp-oauth-client-metadatafor claude.ai, Claude Desktop, Claude mobile, and Coworkhttps://claude.ai/oauth/claude-code-client-metadatafor Claude Code
To accept only Claude, turn off DCR and list both IDs:
OAUTH_DCR_DISABLED=true
OAUTH_CIMD_CLIENT_IDS=https://claude.ai/oauth/mcp-oauth-client-metadata,https://claude.ai/oauth/claude-code-client-metadataPolytomic fetches each client's metadata document while the user signs in, so the Polytomic containers must have outbound HTTPS access to claude.ai.
Turn off OAuth sign-in
Set both OAUTH_DCR_DISABLED=true and OAUTH_CIMD_DISABLED=true to stop accepting any OAuth client. Polytomic then serves no OAuth endpoints. Users connect with an API key through the Polytomic Connector or manual configuration.
Set the variables
With the Helm chart, add the variables under polytomic.extraEnv:
polytomic:
extraEnv:
OAUTH_DCR_DISABLED: "true"
OAUTH_CIMD_CLIENT_IDS: "https://claude.ai/oauth/mcp-oauth-client-metadata,https://claude.ai/oauth/claude-code-client-metadata"With the ECS Terraform module, use extra_environment:
extra_environment = {
OAUTH_DCR_DISABLED = "true"
OAUTH_CIMD_CLIENT_IDS = "https://claude.ai/oauth/mcp-oauth-client-metadata,https://claude.ai/oauth/claude-code-client-metadata"
}Existing connections
Changing a setting doesn't revoke access that users have already granted. Each OAuth sign-in issues a Polytomic API key, and those keys keep working until you revoke them. To cut off a client you've disallowed, revoke its keys under Settings → API keys.
Updated 7 days ago