Opik MCP vs Git
A side-by-side look at the Opik MCP and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Opik MCP for monitoring work as a local process; choose Git for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Opik MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPIK_API_KEY, OPIK_WORKSPACE, COMET_WORKSPACE, COMET_URL_OVERRIDE, OPIK_URL, OPIK_MCP_ANALYTICS_SOURCE. - You want tools like
read_skill.
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Other Tools and Integrations |
| Quality signal | 61/100 · Good | 89/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | OPIK_API_KEYOPIK_WORKSPACECOMET_WORKSPACECOMET_URL_OVERRIDEOPIK_URLOPIK_MCP_ANALYTICS_SOURCE | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 220 | 91,289 |
| Directory activity | 2 views 0 installs 0 upvotes | 39 views 0 installs 0 upvotes |
| Tools | 1 | 9 |
| Full listing | View Opik MCP | View Git |
Tools & capabilities
Opik MCP tools 1
read_skillRead one of the Opik agent skills bundled with this server
Git tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Opik MCP
{
"mcpServers": {
"comet-ml-opik-mcp": {
"command": "npx",
"args": [
"-y",
"opik-mcp"
],
"env": {
"OPIK_API_KEY": "YOUR_OPIK_API_KEY_HERE",
"OPIK_WORKSPACE": "YOUR_OPIK_WORKSPACE_HERE",
"COMET_WORKSPACE": "YOUR_COMET_WORKSPACE_HERE",
"COMET_URL_OVERRIDE": "YOUR_COMET_URL_OVERRIDE_HERE",
"OPIK_URL": "YOUR_OPIK_URL_HERE",
"OPIK_MCP_ANALYTICS_SOURCE": "YOUR_OPIK_MCP_ANALYTICS_SOURCE_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Frequently asked questions
Opik MCP is categorized under Monitoring and uses a local stdio subprocess. Git belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Opik MCP for monitoring work and Git for other tools and integrations.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Opik MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add comet-ml-opik-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Opik MCP has a quality signal of 61/100 (Good) with 2 views, 0 installs and 220 GitHub stars. Git has 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars.