Comet Opik MCP server

What the model can do

Comet Opik, LLM observability and evaluation: projects, traces with latency, cost, token usage, errors, tags and feedback scores (never their inputs or outputs), experiments with status and scores, prompts and their version counts, datasets, and the workspace's cost for a period; when you ask, can comment on, score, tag or delete traces, create, update or delete projects, create prompts and commit prompt versions, delete prompts, create or delete datasets, and cancel or delete experiments.

Reads

• comet_list_projectsOpik projects in the workspace: id, name, description, visibility, when created, last updated and when the last trace arrived.
• comet_list_tracesTraces of an Opik project created in a time window: name, start and end, duration, time to first token, error type and message, tags, cost…
• comet_get_traceOne Opik trace by id, with its timings, error, tags, cost, usage, scores and span counts; never its input, output or metadata.
• comet_list_experimentsOpik experiments: name, dataset, project, type, status (running, completed, cancelled, failed), traces and items, cost…
• comet_list_promptsPrompts in the Opik prompt library: name, description, text or chat, tags, how many versions and when last updated.
• comet_list_datasetsOpik datasets and evaluation suites: name, type, description, tags, how many items and experiments, status, and when last updated and last used.
• comet_get_costsThe workspace's estimated LLM cost for a period, and for the same length of time before it, optionally for some projects only.

Acts, when you ask

These change something in Comet Opik. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• comet_add_trace_commentAdds a comment to an Opik trace, visible to everyone in the workspace who opens it.
• comet_score_traceSets a feedback score on an Opik trace, replacing any score of the same name.
• comet_delete_trace_scoreRemoves a feedback score, by name, from an Opik trace.
• comet_tag_traceAdds and removes tags on an Opik trace in a named project.
• comet_delete_tracesPermanently deletes the Opik traces named by id (at most 100).
• comet_create_projectCreates an Opik project in the workspace.
• comet_update_projectRenames an Opik project or changes its description or visibility (private or public, as Opik defines them).
• comet_delete_projectPermanently deletes an Opik project; treat the traces, spans and scores logged to it as gone with it.
• comet_create_promptCreates a prompt in the Opik prompt library, with its first version when a template is given.
• comet_commit_prompt_versionCommits a new version of an Opik prompt (creating the prompt if no prompt has that name).
• comet_delete_promptPermanently deletes an Opik prompt with all its versions; code that loads it by name will fail.
• comet_create_datasetCreates an empty Opik dataset or evaluation suite.
• comet_delete_datasetPermanently deletes an Opik dataset and its items.
• comet_cancel_experimentsStops the running Opik experiments named by id (at most 50): queued items are skipped and each is marked cancelled.
• comet_delete_experimentsPermanently deletes the Opik experiments named by id (at most 50) with their results.

Connect it

First connect Comet Opik on Dashboard → Connections, then add Memtro to your client once. The Comet Opik tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Comet Opik connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which traces in the support bot errored today?
• › What did the workspace spend on LLM calls this week compared with last week?
• › Which experiments on the refund dataset had the best pass rate?
• › How many versions does the triage prompt have?
• › Tag the slowest trace from this morning as needs-review.

Questions

Is this an official Comet Opik MCP server?

No. It is Memtro's MCP server with Memtro's Comet Opik connector behind it: the connector reads Comet Opik through its API with the credentials you connect on Dashboard → Connections, and Comet Opik publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Comet Opik?

Only when you ask, and only what it has been granted: add a comment to a trace; score a trace (adds or replaces a feedback score by name); remove a feedback score from a trace; add or remove tags on a trace; delete traces by id (permanent); create a project; rename a project or change its description or visibility; delete a project (permanent); create a prompt in the prompt library; commit a new version of a prompt; delete a prompt with its versions (permanent); create a dataset; delete a dataset (permanent); cancel running experiments; delete experiments by id (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server