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.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS67 / 100 · C76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions14 / 2014 / 20
Maintenance18 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience12 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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)
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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)
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Cursor, VS Code, MCP InspectorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools615