M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionOpik MCP ServerConnect your AI host directly to your Opik workspace: read traces, log scores, and manage prompts.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS67 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance18 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • LLM engineers already using Opik
  • Developers who want to manage LLM observability directly from their coding environment
  • Workflows needing deep integration with the Opik platform
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users not using Opik
  • Those not interested in LLM observability
  • Users needing offline or non-cloud features (ask_ollie and run_experiment are Comet Cloud only)
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Read access to Opik projects, traces, spans, test suites, experiments, and prompts
  • Write access to traces, spans, scores, comments, prompt versions, and experiments
  • Access to Opik API key (required)
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Requires API key, which poses security risks if exposed
  • ask_ollie and run_experiment are limited to Comet Cloud; not available for self-hosted
  • Cursor enforces a 60-second tool-call timeout; long operations may fail
  • Default YOLO mode auto-approves Ollie's writes, potentially leading to unintended modifications
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Code, Cursor, VS Code, MCP InspectorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools60