MCP OAuth

Opik's MCP server lets a coding agent read and write your workspace. On Opik Cloud the agent signs in through the browser and stores no API key. A self-hosted deployment can offer the same thing, but the MCP OAuth authorization server is off by default — until you turn it on, the endpoint has no sign-in routes, and agents must use the local server with an API key in their config instead.

Turn it on

Enable mcpOAuth.enabled in the Helm chart, together with these on the backend:

Setting	Value
`MCP_OAUTH_ENABLED`	`true`
`OPIK_BASE_URL`	The public deployment root, without `/api`

Point clients at it

Once it is on, the MCP server URL is your own Opik API base plus /v1/mcp — for the example above, https://opik.example.com/opik/api/v1/mcp. Users run uvx opik mcp configure, which detects the hosted server and registers it, or configure it by hand from Advanced setup.