MCP server for interacting with LLM traces - search, analyze, and debug your AI agent executions
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"021-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# 021-mcp MCP server for interacting with LLM traces. Search, analyze, and debug your AI agent executions through any MCP-compatible client. ## Installation ```bash pip install 021-mcp ``` Or with [uvx](https://docs.astral.sh/uv/): ```bash uvx 021-mcp ``` ## Configuration ### Environment Variables | Variable | Required | Description | |----------|----------|-------------| | `TRACES_API_KEY` | Yes | Your API key for authentication | | `TRACES_BASE_URL` | No | Base URL of the traces API (default: `https://api.021labs.ai`) | ### Claude Desktop Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json`): ```json { "mcpServers": { "traces": { "command": "uvx", "args": ["021-mcp"], "env": { "TRACES_API_KEY": "your-api-key-here" } } } } ``` ### Manus Add to your Manus MCP configuration: ```json { "servers": { "traces": { "command": "uvx", "args": ["021-mcp"], "env": { "TRACES_API_KEY": "your-api-key-here" } } } } ``` ### Cursor / Other MCP Clients Most MCP clients support a similar configuration format. The key elements are: - **command**: `uvx` (or `python -m mcp_traces.server` if installed via pip) - **args**: `["021-mcp"]` - **env**: Must include `TRACES_API_KEY` ## Available Tools ### `list_traces` List traces with optional filters. **Parameters:** - `status` - Filter by status: SUCCESS, ERROR, or RUNNING - `search` - Full-text search query - `start_time` - Filter traces after this ISO timestamp - `end_time` - Filter traces before this ISO timestamp - `session_id` - Filter by session ID - `user_id` - Filter by user ID - `project_id` - Filter by project ID - `limit` - Maximum results (1-100, default 20) **Example usage:** > "Show me the last 10 traces that failed" > "Find traces from yesterday that mention 'database'" ### `get_trace` Get detailed information about a specific trace. **Parameters:** - `trace_id` - The …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.