Skip to main content
hc
Submit
2 compared

LLM observability MCP servers compared

LLM observability MCP servers that give Claude access to traces, evals, and prompt management, compared on trust, setup, and safety.

Open in the interactive comparison tool
Field
Arize Phoenix MCP Server for Claude

Inspect LLM traces and spans, manage prompts, explore datasets, and review evaluation experiments from Claude — with the official Arize Phoenix MCP server, built into the open-source Phoenix AI observability platform.

Open dossier
Opik MCP Server for Claude

Debug, evaluate, and monitor LLM applications from Claude — read traces and spans, score outputs, save prompts, run evaluation experiments, and query project metrics — with the official Opik MCP server by Comet.

Open dossier
Trust
Install riskReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand——
Categorymcpmcp
Sourcesource-backedsource-backed
AuthorArize AIComet
Added2026-06-182026-06-18
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo——
Safety notes✓The `write` and upsert tools can create or modify prompts and add dataset examples — review Claude's proposed changes before confirming. For self-hosted deployments, ensure your Phoenix instance is accessible from the machine running the MCP server.✓The `write` tool can create traces, spans, scores, and prompts in your Opik workspace — review any write operations before confirming. The `run_experiment` tool executes evaluation experiments end-to-end, which may incur LLM API costs depending on your experiment configuration.
Privacy notes✓LLM traces (including prompts and completions), evaluation annotations, session data, datasets, and experiment results from your Phoenix workspace are surfaced in Claude's context. Your `PHOENIX_API_KEY` is passed as an environment variable — store it in a secrets manager rather than plaintext shell config.✓LLM traces (including prompts and completions), evaluation scores, experiment results, and prompt library contents from your Opik workspace are surfaced in Claude's context. Your `OPIK_API_KEY` is passed as an environment variable — store it in a secrets manager rather than plaintext shell config.
Prerequisites
  • An Arize Phoenix account (cloud at app.phoenix.arize.com) or self-hosted Phoenix instance.
  • A Phoenix API key from your account settings.
  • Node.js 18+ for `npx`.
  • An MCP client such as Claude Code or Claude Desktop.
  • An Opik account (cloud at comet.com or self-hosted) and an API key from your workspace settings.
  • Python with `uv` installed: `pip install uv` or `brew install uv`.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add phoenix -e PHOENIX_HOST=https://app.phoenix.arize.com -e PHOENIX_API_KEY=your-key -- npx -y @arizeai/phoenix-mcp@latest
claude mcp add opik -e OPIK_API_KEY=your-api-key -- uvx opik-mcp
Config
{
  "mcpServers": {
    "phoenix": {
      "command": "npx",
      "args": ["-y", "@arizeai/phoenix-mcp@latest"],
      "env": {
        "PHOENIX_HOST": "https://app.phoenix.arize.com",
        "PHOENIX_API_KEY": "your-api-key"
      }
    }
  }
}
{
  "mcpServers": {
    "opik": {
      "command": "uvx",
      "args": ["opik-mcp"],
      "env": {
        "OPIK_API_KEY": "your-api-key",
        "OPIK_WORKSPACE": "default"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimed
More comparisons, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.