Opik MCP Server

Opik MCP Server

A unified Model Context Protocol server for Opik with multi-transport IDE integration.

182
Stars
27
Forks
182
Watchers
29
Issues
Opik MCP Server is an open-source implementation of the Model Context Protocol (MCP) designed for the Opik platform. It enables seamless integration with compatible IDEs and provides a unified interface to manage Opik's features such as prompts, projects, traces, and metrics. Supporting multiple transport mechanisms like stdio and experimental SSE, it simplifies workflow integration and platform management for LLM applications. The tool aims to streamline development and monitoring by offering standardized access and control over Opik's capabilities.

Key Features

Open-source Model Context Protocol server
Supports integration with Cursor and other IDEs
Unified API for Opik capabilities
Management of prompts (create, list, update, delete)
Project and workspace organization
Trace data tracking and analysis
Metrics data gathering and querying
Multiple transport mechanisms (stdio, SSE)
Platform management for LLM applications
Experimental SSE (Server-Sent Events) support

Use Cases

Integrating Opik with development environments like Cursor IDE
Centralized management of prompts, projects, and workspaces
Tracking and analyzing LLM application traces
Gathering and querying application metrics
Facilitating standardized access to Opik's capabilities for tooling
Automating workflow integration with Opik via MCP
Monitoring and organizing LLM development and production workflows
Providing a consistent interface for IDE and tool integrations
Supporting multiple integration scenarios with various transport options
Enhancing productivity for teams working on LLM-based applications

README

License Node.js Version TypeScript DOI

⚠️ 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

Cursor Integration

To integrate with Cursor IDE, open to the Cursor settings page and navigate to the Features tab. If you scroll down to the MCP section you will see the button + Add new MCP server that will allow you to add the Opik MCP server.

Once the New MCP server modal is open, select command as the server type and enter the command: npx -y opik-mcp --apiKey YOUR_API_KEY.

Alternatively, you can create a .cursor/mcp.json in your project and add:

json
{
  "mcpServers": {
    "opik": {
      "command": "npx",
      "args": [
        "-y",
        "opik-mcp",
        "--apiKey",
        "YOUR_API_KEY"
      ]
    }
  }
}

Note: If you are using the Open-Source version of Opik, you will need to specify the apiBaseUrl parameter as http://localhost:5173/api.

Windsurf Installation

To install the MCP server in Windsurf, you will need to open the Windsurf settings and navigate to the MCP section. From there, click on View raw config and update the configuration object to be:

json
{
    "mcpServers": {
      "opik": {
        "command": "npx",
        "args": [
          "-y",
          "opik-mcp",
          "--apiKey",
          "YOUR_API_KEY"
        ]
      }
    }
  }

Note: If you are using the Open-Source version of Opik, you will need to specify the apiBaseUrl parameter as http://localhost:5173/api.

Manual Installation

bash
# Clone the repository
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:

bash
cp .env.example .env
# Edit .env with your specific configuration

Starting the Server

bash
# Start with stdio transport (default)
npm run start:stdio

# Start with SSE transport for network access (experimental)
npm run start:sse

Transport Options

Standard Input/Output

Ideal for local integration where the client and server run on the same machine.

bash
make start-stdio

Server-Sent Events (SSE)

Enables remote access and multiple simultaneous clients over HTTP. Note that this transport option is experimental.

bash
make start-sse

For detailed information about the SSE transport, see docs/sse-transport.md.

Development

Testing

bash
# Run all tests
npm test

# Run specific test suite
npm test -- tests/transports/sse-transport.test.ts

Pre-commit Hooks

This project uses pre-commit hooks to ensure code quality:

bash
# Run pre-commit checks manually
make precommit

Documentation

Citation

If you use this project in your research, please cite it as follows:

Comet ML, Inc, Koc, V., & Boiko, Y. (2025). Opik MCP Server. Github. https://doi.org/10.5281/zenodo.15411156

Or use the following BibTeX entry:

bibtex
@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.

License

Apache 2.0

Star History

Star History Chart

Repository Owner

comet-ml
comet-ml

Organization

Repository Details

Language TypeScript
Default Branch main
Size 356 KB
Contributors 6
License Apache License 2.0
MCP Verified Nov 12, 2025

Programming Languages

TypeScript
92.86%
HTML
4.7%
JavaScript
1.29%
Makefile
0.87%
Dockerfile
0.27%

Tags

Topics

generative-ai mcp-server modelcontextprotocol typescript

Join Our Newsletter

Stay updated with the latest AI tools, news, and offers by subscribing to our weekly newsletter.

We respect your privacy. Unsubscribe at any time.

Related MCPs

Discover similar Model Context Protocol servers

  • PostHog MCP

    PostHog MCP

    Easily deploy and manage Model Context Protocol servers across multiple platforms.

    PostHog MCP provides a server implementation for the Model Context Protocol, now maintained within the PostHog monorepo. It enables quick deployment for enhanced model context management across editors like Cursor, Claude, Claude Code, VS Code, and Zed. Users can install the MCP server with a single command, streamlining integration for large language model workflows. Documentation and further details are provided through official PostHog resources.

    • 138
    • MCP
    • PostHog/mcp
  • Teamwork MCP Server

    Teamwork MCP Server

    Seamless Teamwork.com integration for Large Language Models via the Model Context Protocol

    Teamwork MCP Server is an implementation of the Model Context Protocol (MCP) that enables Large Language Models to interact securely and programmatically with Teamwork.com. It offers standardized interfaces, including HTTP and STDIO, allowing AI agents to perform various project management operations. The server supports multiple authentication methods, an extensible toolset architecture, and is designed for production deployments. It provides read-only capability for safe integrations and robust observability features.

    • 11
    • MCP
    • Teamwork/mcp
  • Neovim MCP Server

    Neovim MCP Server

    Connect AI assistants to Neovim via the Model Context Protocol.

    Neovim MCP Server enables seamless integration between Neovim instances and AI assistants by implementing the Model Context Protocol (MCP). It allows for multi-connection management, supports both stdio and HTTP server transport modes, and provides access to structured diagnostic information via URI schemes. With LSP integration, plugin support, and an extensible tool system, it facilitates advanced interaction with Neovim for context-aware AI workflows.

    • 20
    • MCP
    • linw1995/nvim-mcp
  • Insforge MCP Server

    Insforge MCP Server

    A Model Context Protocol server for seamless integration with Insforge and compatible AI clients.

    Insforge MCP Server implements the Model Context Protocol (MCP), enabling smooth integration with various AI tools and clients. It allows users to configure and manage connections to the Insforge platform, providing automated and manual installation methods. The server supports multiple AI clients such as Claude Code, Cursor, Windsurf, Cline, Roo Code, and Trae via standardized context management. Documentation and configuration guidelines are available for further customization and usage.

    • 3
    • MCP
    • InsForge/insforge-mcp
  • MCP Server for Milvus

    MCP Server for Milvus

    Bridge Milvus vector database with AI apps using Model Context Protocol (MCP).

    MCP Server for Milvus enables seamless integration between the Milvus vector database and large language model (LLM) applications via the Model Context Protocol. It exposes Milvus functionality to external LLM-powered tools through both stdio and Server-Sent Events communication modes. The solution is compatible with MCP-enabled clients such as Claude Desktop and Cursor, supporting easy access to relevant vector data for enhanced AI workflows. Configuration is flexible through environment variables or command-line arguments.

    • 196
    • MCP
    • zilliztech/mcp-server-milvus
  • Godot MCP

    Godot MCP

    A Model Context Protocol (MCP) server implementation using Godot and Node.js.

    Godot MCP implements the Model Context Protocol (MCP) as a server, leveraging the Godot game engine along with Node.js and TypeScript technologies. Designed for seamless integration and efficient context management, it aims to facilitate standardized communication between AI models and applications. This project offers a ready-to-use MCP server for developers utilizing Godot and modern JavaScript stacks.

    • 1,071
    • MCP
    • Coding-Solo/godot-mcp
  • Didn't find tool you were looking for?

    Be as detailed as possible for better results