development
documentation
public
IDE integration
transport mechanisms
What is Opik MCP Server is an open-source implementation of the Model Context Protocol for the Opik platform.?
Opik MCP Server is an open-source implementation of the Model Context Protocol for the Opik platform with support for multiple transport mechanisms, enabling seamless integration with IDEs and providing a unified interface for Opik's capabilities. It allows for managing prompts, projects, traces, and metrics through a consistent interface.
Documentation
⚠️ Notice: SSE (Server-Sent Events) transport support is currently experimental and untested. For production use, we recommend using the direct process execution approach shown in the IDE integration examples.
🚀 What is Opik MCP Server?
Opik MCP Server is an open-source implementation of the Model Context Protocol for the Opik platform. It provides a unified interface for interacting with Opik's capabilities, supporting multiple transport mechanisms for flexible integration into various environments.
You can use Opik MCP Server for:
IDE Integration:
Seamlessly integrate with Cursor and other compatible IDEs
Provide direct access to Opik's capabilities from your development environment
Unified API Access:
Access all Opik features through a standardized protocol
Leverage multiple transport options (stdio, SSE) for different integration scenarios
Platform Management:
Manage prompts, projects, traces, and metrics through a consistent interface
Organize and monitor your LLM applications efficiently
Features
Prompts Management: Create, list, update, and delete prompts
Projects/Workspaces Management: Organize and manage projects
Traces: Track and analyze trace data
Metrics: Gather and query metrics data
Quick Start# Installation
Manual Installation
git clone https://github.com/comet-ml/opik-mcp.git
cd opik-mcp
# Install dependencies and build
npm install
npm run build
Configuration
Create a .env file based on the example:
cp .env.example .env\n\n# Edit .env with your specific configuration
Starting the Server
npm run start:stdio
# Start with SSE transport for network access (experimental)
npm run start:sse
IDE Integration# Cursor Integration
To integrate with Cursor IDE, create a .cursor/mcp.json file in your project directory with the following configuration:
Replace /path/to/node with the path to your Node.js executable and /path/to/opik-mcp with the path to your opik-mcp installation. Also replace YOUR_API_KEY with your actual Opik API key.
Available Commands
The project includes a Makefile for common operations:
make help
# Run tests
make test
# Run transport-specific tests
make test-transport
# Start the server with SSE transport (experimental)
make start-sse
# Start the server with stdio transport
make start-stdio
Transport Options# Standard Input/Output
Ideal for local integration where the client and server run on the same machine.
make start-stdio
Server-Sent Events (SSE)
Enables remote access and multiple simultaneous clients over HTTP. Note that this transport option is experimental.
@software{CometML_Opik_MCP_Server_2025,
author = {{Comet ML, Inc} and Koc, V. and Boiko, Y.},
title = {{Opik MCP Server}},
year = {2025},
publisher = {GitHub},
url = {https://doi.org/10.5281/zenodo.15411156},
doi = {10.5281/zenodo.15411156}
}
You can also find citation information in the CITATION.cff file in this repository.