Skip to directory

Opik MCP

Comet (official Opik project)

Streamable HTTP for hosted Opik Cloud; stdio for the local package.4+ documented tools0

About Opik MCP

Comet's official MCP integration for Opik lets an AI client inspect LLM traces and projects, record scores and comments, and manage prompts, datasets, and experiments in the connected Opik workspace.

What you can use it for

  • Review LLM traces and spans
  • Find projects, datasets, and experiments
  • Score or comment on traces
  • Save prompt versions and curate evaluation datasets
Connection and setup
Hosting
Comet-hosted remote service for Opik Cloud; local stdio server for self-hosted Comet or open-source Opik.
Transport
Streamable HTTP for hosted Opik Cloud; stdio for the local package.
Endpoint
https://www.comet.com/opik/api/v1/mcp
Authentication
Opik Cloud hosted endpoint uses browser OAuth; no API key or manual workspace setting is needed. Local open-source Opik generally needs no key unless authentication is enabled. Self-hosted Comet or local-server-to-Cloud setups may require OPIK_API_KEY and OPIK_WORKSPACE.

Requirements

  • An Opik Cloud account for the hosted endpoint, or a reachable self-hosted/open-source Opik deployment for the local server.
  • For the local package, uv/uvx; the current Python package requires Python 3.13 or newer, which uv can install on first use.
  • Only configure the local package for a deployment you control or have permission to access.

Setup steps

  1. For Opik Cloud, add the remote MCP URL https://www.comet.com/opik/api/v1/mcp in an MCP client that supports remote Streamable HTTP, then complete the browser sign-in and select the intended workspace. No API key is required for this hosted path.
  2. For self-hosted or open-source Opik, install uv and configure a local stdio process with command `uvx` and args `["opik-mcp"]`. For local open-source Opik set OPIK_URL to the documented API URL (the local default example is http://localhost:5173/api). For self-hosted Comet set COMET_URL_OVERRIDE, OPIK_WORKSPACE, and the secret OPIK_API_KEY using the client’s secure environment mechanism.
  3. Reconnect the client and inspect its tools. The official docs suggest asking to list Opik projects. For local deployments, validate the same environment first with `uvx opik-mcp@latest --check`; do not treat an MCP connection indicator alone as proof that the deployment or credentials work.
  4. Use the official setup guide at https://www.comet.com/docs/opik/mcp-server for client-specific installation and troubleshooting. Do not use the legacy `npx opik-mcp` package for a new setup; the current supported local package is `opik-mcp` via uvx.
Tools 4+

The current official README lists the complete four-tool surface: read, list, write, and schema. These are documentation-derived names, not a live tools/list result. `write` can make changes in the connected Opik workspace; inspect operation schemas and obtain user approval before write operations.

  • read

    Read an Opik entity by ID, name, or Opik URI.

    01
  • list

    List and filter Opik entities with pagination.

    02
  • write

    Create or update traces, spans, scores, comments, prompts, datasets, experiments, and selected agent-insights records.

    03
  • schema

    Inspect the required shape, scope, and example for supported operations without calling the backend.

    04

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Hosted Cloud usage requires the user to complete OAuth in the MCP client; no authentication was performed during catalog research.
  • The local package currently requires Python 3.13 or newer via uvx.
  • The `write` tool can mutate connected project data; operation-specific side effects should be reviewed and approved before use.
  • Documentation and logo were reviewed; connection, tools/list, and functionality were not tested.
Original sources
  • official repository documentation

    Identifies the maintained official Opik MCP, distinguishes hosted Cloud OAuth and local stdio paths, documents the hosted endpoint, current uvx package, setup flow, Python requirement, validation command, and the four tools read/list/write/schema.

  • official package metadata

    Current PyPI distribution is opik-mcp and requires Python >=3.13.

  • verified publisher organization avatar

    Comet organization image linked from the official Comet-owned MCP repository; downloaded, decoded, and reviewed individually and on light/dark contact sheets. Selection tier B: publisher/company logo because no dedicated standalone logo is published in the MCP repository.

  • discovery directory

    Opik MCP appeared in the awesome-mcp.tools observability search results; used for discovery only, with all product and setup facts checked against official Comet sources.

  • official or maintainer tool reference

    Official repository documents four tools: read/list/write/schema; catalog rows match.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.