Comet Opik MCP Server

Query and analyze your Opik logs, traces, prompts and all other telemtry data from your LLMs in natural language.

Remote serverstreamable-httpPython

What is the Comet Opik MCP server?

Comet opik mcp server lets Claude, Cursor and other MCP clients work with Comet Opik directly. Query and analyze your Opik logs, traces, prompts and all other telemtry data from your LLMs in natural language.

What Comet Opik does

Built for LLM engineers who already run Opik and want to drive it from the same AI assistant they code with.

Tools it exposes

Once connected, the assistant can call these 8 tools directly:

  • Cursor — Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project), or open Cmd+Shift+J → Features → Model Context Protocol:
  • read — One tool for any "show me X" question. Takes an entity_type plus an id (UUID or, for nameable types, a name) or a full opik:// URI. Composite reads (trace
  • list — Browse a collection with optional name filter and pagination. Project-scoped types (trace, test_suite_item, prompt_version) require their parent UUID
  • ask_ollie — For investigative questions, cross-entity synthesis, or anything that needs Opik domain expertise. Ollie has direct read access to your workspace and can
  • write — Universal write dispatcher. Pass operation + data and the dispatcher validates the payload, applies the right REST verb, and returns the backend response
  • schema — Inspect the exact JSON shape and required fields of any write operation before you call it — useful when you're not sure what data should look like. Returns
  • run_experiment — Run an evaluation experiment end-to-end via Ollie. Takes a single experiment_config dict that mirrors Opik's experiment shape (prompt, test suite, scorers)
  • Telemetry — Anonymous usage events (event type + timing only — no query content). A SHA-256 digest of your API key is included so support can find your account; the raw

Installing the comet opik mcp server

The server is distributed via npm as opik-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 8 environment variables: OPIK_API_KEY, OPIK_WORKSPACE, COMET_URL_OVERRIDE, OPIK_MCP_ANALYTICS_SOURCE, OPIK_URL, COMET_WORKSPACE_ID, OPIK_MCP_HOST, OPIK_MCP_AS_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Comet Opik sits in that group, and the shape of its toolset — Cursor, read, list among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • With 8 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Comet Opik.
  • Written in Python.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the comet opik mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
CursorEdit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project), or open **Cmd+Shift+J → Features → Model Context Protocol**:
readOne tool for any "show me X" question. Takes an entity_type plus an id (UUID or, for nameable types, a name) or a full opik:// URI. Composite reads (trace, prompt) inline their children so a single call returns the full
listBrowse a collection with optional name filter and pagination. Project-scoped types (trace, test_suite_item, prompt_version) require their parent UUID.
ask_ollieFor investigative questions, cross-entity synthesis, or anything that needs Opik domain expertise. Ollie has direct read access to your workspace and can execute writes (scores, comments, test-suite items, prompt version
writeUniversal write dispatcher. Pass operation + data and the dispatcher validates the payload, applies the right REST verb, and returns the backend response.
schemaInspect the exact JSON shape and required fields of any write operation before you call it — useful when you're not sure what data should look like. Returns the schema, OAuth scope, and one validated example. Pure lookup
run_experimentRun an evaluation experiment end-to-end via Ollie. Takes a single experiment_config dict that mirrors Opik's experiment shape (prompt, test suite, scorers); Ollie executes the run and writes results back as an Opik exper
TelemetryAnonymous usage events (event type + timing only — no query content). A SHA-256 digest of your API key is included so support can find your account; the raw key never leaves the process. **Opt out:** OPIK_MCP_ANALYTICS_E

How to install the Comet Opik MCP server

Or edit `~/.claude.json` directly:

```json
{
  "mcpServers": {
    "opik-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["opik-mcp"],
      "env": {
        "OPIK_API_KEY": "<your-key>",
        "OPIK_WORKSPACE": "<your-workspace>"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
OPIK_API_KEYCredential the server authenticates with.Yes
OPIK_WORKSPACEConfiguration value read at startup.Optional
COMET_URL_OVERRIDEEndpoint or connection string the server talks to.Yes
OPIK_MCP_ANALYTICS_SOURCEConfiguration value read at startup.Optional
OPIK_URLEndpoint or connection string the server talks to.Yes
COMET_WORKSPACE_IDConfiguration value read at startup.Optional
OPIK_MCP_HOSTEndpoint or connection string the server talks to.Optional
OPIK_MCP_AS_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Comet Opik to Cursor.
  • Use Comet Opik to read.
  • Use Comet Opik to list.

Frequently asked questions

It connects Comet Opik to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Cursor, read, list, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Comet Opik directly.