OAuth MCP Servers¶
Alpha Feature
OAuth MCP server support is a new feature and will experience rapid improvements. Configuration and behavior may change between releases.
Some MCP servers support OAuth-based authentication natively — you only need to set oauth.enabled: true and Holmes handles the rest. When Holmes connects to an OAuth-enabled MCP server, it automatically discovers the server's OAuth endpoints, opens a browser for login, and persists the token for future use.
Setup¶
To add an OAuth MCP server, set mode: streamable-http and oauth.enabled: true in the server's config:
Set the CUSTOM_TOOLSET_LOCATION environment variable pointing to a YAML file with your MCP server configuration:
In that file, define your OAuth MCP servers:
Example: Atlassian¶
Before configuring Holmes, set up the Atlassian side:
- Go to https://admin.atlassian.com/ and select your organization
- Navigate to Rovo → Rovo MCP Server
-
Click Add domain and enter your Robusta platform URL, matching your region:
Region URL US (default) https://platform.robusta.dev/**EU https://eu.platform.robusta.dev/**AP https://ap.platform.robusta.dev/**
Update your values and helm install or upgrade:
How It Works¶
- Holmes detects that the MCP server has
oauth.enabled: true - Holmes discovers the server's OAuth configuration automatically via the MCP protocol
- The user is prompted to authenticate via their browser
- After login, Holmes exchanges the authorization code for an access token
- The token is persisted and refreshed automatically — users only need to authenticate once