Opik MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPIK_API_KEY | Yes | Your Opik API key | |
| OPIK_API_BASE_URL | No | The base URL for the Opik API | https://www.comet.com/opik/api |
| OPIK_WORKSPACE_NAME | No | The name of your Opik workspace | default |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-promptsC | Get a list of Opik prompts |
| create-promptC | Create a new prompt |
| create-prompt-versionC | Create a new version of a prompt |
| get-prompt-by-idC | Get a single prompt by ID |
| update-promptC | Update a prompt |
| delete-promptC | Delete a prompt |
| list-projectsC | Get a list of projects/workspaces |
| get-project-by-idC | Get a single project by ID |
| create-projectC | Create a new project/workspace |
| update-projectC | Update a project |
| delete-projectC | Delete a project |
| list-tracesC | Get a list of traces |
| get-trace-by-idC | Get a single trace by ID |
| get-trace-statsC | Get statistics for traces |
| get-metricsC | Get metrics data |
| get-server-infoB | Get information about the Opik server configuration |
| get-opik-helpB | Get contextual help about Opik Comet's capabilities |
| get-opik-examplesC | Get examples of how to use Opik Comet's API for specific tasks |
| get-opik-tracing-infoC | Get information about Opik's tracing capabilities and how to use them |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| workspace-info | |
| projects-list |
TDQS
Scored across 19 tools
Each tool has a clearly distinct purpose targeting specific resources (projects, prompts, traces, metrics, help) and actions (create, get, list, update, delete). There is no overlap or ambiguity between tools, making it easy for an agent to select the right one for any operation.
All tools follow a consistent verb_noun pattern with hyphens (e.g., create-project, get-project-by-id, list-projects). The naming is uniform across all 19 tools, using clear verbs like create, get, list, update, and delete paired with specific nouns.
With 19 tools, the count is slightly high but reasonable for a comprehensive server covering projects, prompts, traces, metrics, and help. It feels well-scoped for the Opik domain, though it borders on being heavy compared to typical 3-15 tool ranges.
The tool set provides complete CRUD/lifecycle coverage for projects and prompts (create, get, list, update, delete), with additional tools for traces, metrics, and help. There are no obvious gaps; agents can perform all core operations without dead ends in this domain.