Opik MCP Server

Apache 2.0

160

Overview InspectNew Endpoints Schema Related Servers Reviews Score

get-trace-by-id

Retrieve a specific trace by its ID to analyze or debug workflows in the Opik MCP Server. Supports optional workspace customization for targeted trace fetching.

Instructions

Get a single trace by ID

Input Schema

Name	Required	Description	Default
`traceId`	Yes	ID of the trace to fetch
`workspaceName`	No	Workspace name to use instead of the default

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "traceId": {
      "description": "ID of the trace to fetch",
      "type": "string"
    },
    "workspaceName": {
      "description": "Workspace name to use instead of the default",
      "type": "string"
    }
  },
  "required": [
    "traceId"
  ],
  "type": "object"
}

This server cannot be installed

Other Tools from Opik MCP Server

Related Tools

list-traces
@comet-ml/opik-mcp
get-project-by-id
@comet-ml/opik-mcp
get-trace-stats
@comet-ml/opik-mcp
get_flow_by_id
@fortunto2/prefect-mcp-server
get_task_details
@mokafari/orchestrator-server
ticktick_get_task_details
@liadgez/ticktick-mcp-server

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/comet-ml/opik-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server