Interact with Opik prompts, traces, datasets and metrics through the Model Context Protocol.
{
"mcpServers": {
"opik": {
"args": [
"-y",
"opik-mcp",
"--apiKey",
"YOUR_API_KEY"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Interact with Opik prompts, traces, datasets and metrics through the Model Context Protocol.
Is it safe?
No known CVEs for opik-mcp.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 22 days ago. 204 stars.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'opik-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.comet-ml/opik-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol (MCP) server for Opik, with both local stdio and remote streamable-http transports.
Website • Slack community • Twitter • Documentation
[!IMPORTANT] This repository ships the MCP server implementation only. We do not currently provide a hosted remote MCP service for Opik. If you run
streamable-httpremotely, authentication is fail-closed by default.
Opik MCP Server gives MCP-compatible clients one interface for:
# Opik Cloud
npx -y opik-mcp --apiKey YOUR_API_KEY
For self-hosted Opik, pass --apiUrl (for example http://localhost:5173/api) and use your local auth strategy.
Cursor (.cursor/mcp.json):
{
"mcpServers": {
"opik": {
"command": "npx",
"args": ["-y", "opik-mcp", "--apiKey", "YOUR_API_KEY"]
}
}
}
VS Code / GitHub Copilot (.vscode/mcp.json):
{
"inputs": [
{
"type": "promptString",
"id": "opik-api-key",
"description": "Opik API Key",
"password": true
}
],
"servers": {
"opik-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "opik-mcp", "--apiKey", "${input:opik-api-key}"]
}
}
}
Windsurf (raw config):
{
"mcpServers": {
"opik": {
"command": "npx",
"args": ["-y", "opik-mcp", "--apiKey", "YOUR_API_KEY"]
}
}
}
More client-specific examples: docs/ide-integration.md
git clone https://github.com/comet-ml/opik-mcp.git
cd opik-mcp
npm install
npm run build
Optional local config:
cp .env.example .env
Start the server:
npm run start:stdio
npm run start:http
| Transport | Use case | Command |
| --- | --- | --- |
| stdio | Local MCP integration (same machine as client) | npm run start:stdio |
| streamable-http | Remote/self-hosted MCP endpoint (`