MCP.so
Sign In

Opik Mcp

@comet-ml

About Opik Mcp

Model Context Protocol (MCP) implementation for Opik enabling seamless IDE integration and unified access to prompts, projects, traces, and metrics.

Basic information

Category

Developer Tools

License

Apache-2.0

Runtime

python

Transports

stdio

Publisher

comet-ml

Submitted by

Vincent Koc

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "opik-mcp": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/inspector",
        "uvx",
        "opik-mcp"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Opik Mcp?

Opik Mcp is a Model Context Protocol server that connects AI hosts (Claude Code, Cursor, VS Code Copilot, MCP Inspector) directly to an Opik workspace. It lets LLM engineers read traces, log scores, save prompt versions, and ask the Opik in-product assistant Ollie investigative questions — all from the chat interface of their AI coding tool.

How to use Opik Mcp?

Install the Python package (requires Python 3.13+) via uvx opik-mcp. Configure the OPIK_API_KEY and optionally OPIK_WORKSPACE environment variables, then add the server to your MCP client config (e.g., ~/.claude.json for Claude Code, .cursor/mcp.json for Cursor, or .vscode/mcp.json for VS Code Copilot). Restart your host and ask, for example: "list my Opik projects."

Key features of Opik Mcp

  • Six outcome-oriented tools: read, list, ask_ollie, write, schema, run_experiment
  • Universal read and list by id, name, or opik:// URI
  • In-workspace investigation via Ollie with YOLO-mode auto-approval
  • Write operations: log traces, spans, scores, comments, prompt versions, test suites, experiments
  • Schema introspection for constructing valid write payloads
  • End-to-end experiment execution via Ollie on Comet Cloud

Use cases of Opik Mcp

  • Investigate why an experiment regressed on factuality by asking Ollie in chat
  • Score a trace on helpfulness directly from the AI assistant without leaving the editor
  • Browse and filter Opik projects, experiments, and traces by name or parent
  • Save new prompt versions and manage test suites through conversational commands
  • Run evaluation experiments end-to-end by sending an experiment_config dict

FAQ from Opik Mcp

What does Opik Mcp require to run?

Python 3.13+, the uv tool, an OPIK_API_KEY from your Opik workspace, and optionally an OPIK_WORKSPACE name (defaults to default for local/OSS installs).

Where does Opik Mcp store data?

All data lives in your Opik workspace — either Comet Cloud (www.comet.com) or a self-hosted instance configured via COMET_URL_OVERRIDE. Opik Mcp is a stateless proxy; it doesn't persist data locally.

Are there known host limits?

Cursor enforces a 60-second tool-call timeout that doesn't reset on progress notifications, so long ask_ollie turns will fail on Cursor.

Which transports does Opik Mcp support?

It defaults to stdio (host-launched) and supports streamable-http to listen on a port. Set OPIK_MCP_TRANSPORT=streamable-http and configure OPIK_MCP_HOST/OPIK_MCP_PORT as needed.

Is ask_ollie or run_experiment available on self-hosted Opik?

No. Both ask_ollie and run_experiment are available on Comet Cloud only. On self-hosted installs, use read, list, schema, and write directly.

Comments

More Developer Tools MCP servers