How to connect the Opik MCP server
To connect the official Opik MCP server, add https://www.comet.com/opik/api/v1/mcp to your MCP client as a Streamable HTTP server, then sign in with OAuth when your client prompts you. If you need an API key instead of browser sign-in, use the local server. Opik documents setup for Claude Code, Codex, Cursor and VS Code.
Docs reviewed 5 Nov 2026Not a tested connection.
Endpoint https://www.comet.com/opik/api/v1/mcp · Registry io.github.comet-ml/opik-mcp 3.0.8
Add Opik MCP to your client
claude mcp add --transport http opik https://www.comet.com/opik/api/v1/mcp
Connect Opik MCP step by step
Before you start
- An Opik Cloud (Comet) account. You pick the workspace the server works in when you sign in. comet.com/docsgithub.com/comet-ml
- For Cursor, Cursor Pro or higher; MCP isn't available on Cursor's Hobby plan. comet.com/docs
- This endpoint is for Opik Cloud. Dedicated or self-hosted Comet deployments offer the hosted-style flow only when the deployment runs the MCP OAuth server, which is off by default; otherwise use the local server. github.com/comet-mlcomet.com/docs
Authentication
- Your client → Opik MCP
- OAuth sign-in, handled by your MCP client. github.com/comet-mlcomet.com/docsmodelcontextprotocol.io/specification
- Opik MCP → Opik API
- The server acts on your account with the access you approve. github.com/comet-ml
Steps
- Open Opik's MCP server setup instructions
- Add the Opik MCP server to your client
Add https://www.comet.com/opik/api/v1/mcp as a remote MCP server that uses the HTTP transport. Opik publishes one-click installs for Cursor and VS Code, a Claude Code plugin, and a setup command that configures Claude Code, Codex, Cursor, VS Code and opencode. Clients that run only local commands can use the mcp-remote bridge.
- Sign in to Opik in the browser and pick a workspace
- If you need an API key instead of browser sign-in, use the local server
The hosted endpoint uses browser sign-in only. To authenticate with an Opik API key, run Opik's local server package instead and give it your API key and workspace name as described in Opik's documentation. The older TypeScript npm package (opik-mcp version 2) is deprecated and stops serving requests on 2026-11-15.
- List the server's tools
Your client should list the server's tools. That confirms the connection, not every API permission.
What we observed
- 5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://www.comet.com/.well-known/oauth-protected-resource, which names the authorization server https://www.comet.com/opik and the resource https://www.comet.com/opik/api/v1/mcp.
Opik MCP questions
What is the Opik MCP server URL?
The official Opik MCP server is at https://www.comet.com/opik/api/v1/mcp and uses the Streamable HTTP transport.
How do I authenticate with the Opik MCP server?
Sign in with OAuth when your client prompts you. If you need an API key instead of browser sign-in, use the local server: The hosted endpoint uses browser sign-in only. To authenticate with an Opik API key, run Opik's local server package instead and give it your API key and workspace name as described in Opik's documentation. The older TypeScript npm package (opik-mcp version 2) is deprecated and stops serving requests on 2026-11-15.
Which AI clients can use the Opik MCP server?
Opik's documentation covers Claude Code, Codex, Cursor and VS Code. Other clients that support remote Streamable HTTP MCP servers may also work.
What do I need before connecting Opik MCP?
An Opik Cloud (Comet) account. You pick the workspace the server works in when you sign in. For Cursor, Cursor Pro or higher; MCP isn't available on Cursor's Hobby plan. This endpoint is for Opik Cloud. Dedicated or self-hosted Comet deployments offer the hosted-style flow only when the deployment runs the MCP OAuth server, which is off by default; otherwise use the local server.
Has this Opik MCP guide been tested?
Opik's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work.
Sources and review
Opik's documentation was checked on the dates shown. This guide follows the MCP Connect connection-guide draft, bound to the exact Registry record it describes. It is not a tested connection: your account and permissions decide which tools work.
Guide source and binding
MCP connection guide (draft 0.1) for io.github.comet-ml/opik-mcp 3.0.8, bound to /remotes/0 of the Registry record by SHA-256 88787c189ca2….
- www.comet.com/docs/opik/mcp-server · checked 5 Nov 2026
- github.com/comet-ml/opik-mcp · checked 5 Nov 2026
- registry.modelcontextprotocol.io/v0.1/servers/io.github.comet-ml%2Fopik-mcp/versions/3.0.8 · checked 5 Nov 2026
- modelcontextprotocol.io/specification/2026-07-28/basic/authorization · checked 5 Nov 2026