Opik Mcp

Created By
comet-mla year ago
Model Context Protocol (MCP) implementation for Opik enabling seamless IDE integration and unified access to prompts, projects, traces, and metrics.
Overview

What is Opik MCP Server?

Opik MCP Server is an open-source implementation of the Model Context Protocol for the Opik platform, designed to query and analyze telemetry and observability metrics, traces, and logs from LLM applications.

How to use Opik MCP Server?

To use Opik MCP Server, clone the repository, install dependencies, configure your environment, and start the server using either standard input/output or Server-Sent Events transport.

Key features of Opik MCP Server?

  • Prompts Management: Create, list, update, and delete prompts.
  • Projects/Workspaces Management: Organize and manage projects efficiently.
  • Traces: Track and analyze trace data for better insights.
  • Metrics: Gather and query metrics data for performance monitoring.

Use cases of Opik MCP Server?

  1. Integrating with IDEs like Cursor for seamless development.
  2. Managing LLM applications and their performance metrics.
  3. Analyzing telemetry data for debugging and optimization.

FAQ from Opik MCP Server?

  • Can Opik MCP Server be used with any IDE?

Yes! It supports integration with various IDEs, including Cursor.

  • Is the SSE transport stable for production use?

Currently, SSE transport is experimental; for production, it's recommended to use standard input/output transport.

  • How can I manage my projects and prompts?

You can manage them through the unified API access provided by Opik MCP Server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
comet-ml
Star
86
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago