Tracelane MCP

Name: Tracelane MCP
Author: tracelane

by tracelaneversion 0.4.0i★ –iRuns on your computer

Registry nameio.github.tracelane/tracelane-mcp

Install

Overview

Description from the maker (original English)

Read-only, tenant-scoped access to Tracelane agent traces and guardrail verdicts

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: TRACELANE_API_KEY, TRACELANE_GATEWAY_URL, CLICKHOUSE_PASSWORD

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: TRACELANE_API_KEY, TRACELANE_GATEWAY_URL, CLICKHOUSE_URL, CLICKHOUSE_USER, CLICKHOUSE_PASSWORD, CLICKHOUSE_DB, TRACELANE_MCP_TRANSPORT

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "tracelane": {
      "command": "npx",
      "args": [
        "-y",
        "@tracelanedev/mcp"
      ],
      "env": {
        "TRACELANE_API_KEY": "your-value",
        "TRACELANE_GATEWAY_URL": "your-value",
        "CLICKHOUSE_URL": "your-value",
        "CLICKHOUSE_USER": "your-value",
        "CLICKHOUSE_PASSWORD": "your-value",
        "CLICKHOUSE_DB": "your-value",
        "TRACELANE_MCP_TRANSPORT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add tracelane --env TRACELANE_API_KEY=your-value --env TRACELANE_GATEWAY_URL=your-value --env CLICKHOUSE_URL=your-value --env CLICKHOUSE_USER=your-value --env CLICKHOUSE_PASSWORD=your-value --env CLICKHOUSE_DB=your-value --env TRACELANE_MCP_TRANSPORT=your-value -- npx -y @tracelanedev/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "tracelane": {
      "command": "npx",
      "args": [
        "-y",
        "@tracelanedev/mcp"
      ],
      "env": {
        "TRACELANE_API_KEY": "your-value",
        "TRACELANE_GATEWAY_URL": "your-value",
        "CLICKHOUSE_URL": "your-value",
        "CLICKHOUSE_USER": "your-value",
        "CLICKHOUSE_PASSWORD": "your-value",
        "CLICKHOUSE_DB": "your-value",
        "TRACELANE_MCP_TRANSPORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "tracelane": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@tracelanedev/mcp"
      ],
      "env": {
        "TRACELANE_API_KEY": "your-value",
        "TRACELANE_GATEWAY_URL": "your-value",
        "CLICKHOUSE_URL": "your-value",
        "CLICKHOUSE_USER": "your-value",
        "CLICKHOUSE_PASSWORD": "your-value",
        "CLICKHOUSE_DB": "your-value",
        "TRACELANE_MCP_TRANSPORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

TRACELANE_API_KEY secret required env
Tracelane API key (tlane_…). Resolved to a tenant once at startup via the gateway's /v1/auth/whoami; the server refuses to start if the key is rejected. Also the credential used to read trace data th…
TRACELANE_GATEWAY_URL required env
Base URL of the Tracelane gateway. Validates TRACELANE_API_KEY, and — when CLICKHOUSE_URL is unset — is where every trace read goes. Must be https://…tracelane.dev outside development.
CLICKHOUSE_URL env
self-host only; when unset the server reads through the gateway. Set this to point the server at your own ClickHouse instead of Tracelane Cloud.
CLICKHOUSE_USER env
ClickHouse username.
CLICKHOUSE_PASSWORD secret env
ClickHouse password.
CLICKHOUSE_DB env
ClickHouse database holding the spans table.
TRACELANE_MCP_TRANSPORT env
Transport to serve. stdio (default) for desktop clients; http for the Streamable HTTP transport.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account tracelane, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32531 servers in this category
Published to the registry more recently than 58% of the other 32531 servers in this category
Basic checks equal to or better than 100% of the other 32531 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Tracelane MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TRACELANE_API_KEY, TRACELANE_GATEWAY_URL, CLICKHOUSE_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 28 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Reelsaw

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Reelsaw

by osbytes

Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

`@tracelanedev/mcp` — Tracelane MCP Server

Read-only MCP server exposing Tracelane trace data to any MCP-compatible client — Claude Desktop, Claude Code, Cursor, or any agent using the Model Context Protocol.

On npm since 2026-09-07: npx @tracelanedev/mcp installs the published version; the

config blocks below work as written. From-source is still documented under self-hosting.

The same run submits apps/mcp/server.json to the MCP registry; the name it will be listed under is io.github.tracelane/tracelane-mcp.

Default mode reads through the gateway — the same tenant-scoped /v1/* routes the dashboard uses — with just TRACELANE_API_KEY and TRACELANE_GATEWAY_URL. That is the Cloud-tenant path and needs no ClickHouse credentials. Set CLICKHOUSE_URL to switch to self-host mode, reading ClickHouse directly instead — see Self-hosting.

Quick start

Cloud (Tracelane-hosted tenant)

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows), or .mcp.json at your project root for Claude Code:

"mcpServers": { "tracelane": { "command": "npx", "args": ["@tracelanedev/mcp"], "env": { "TRACELANE_API_KEY": "tlane_YOUR_KEY", "TRACELANE_GATEWAY_URL": "https://gateway.tracelane.dev" } } } }

No CLICKHOUSE_URL — its absence is what selects gateway mode. Every read goes through the gateway's existing tenant-scoped routes, so a key from another tenant, or one lacking the read scope, gets a clear tool error rather than an empty result.

Run from a clone

Swap the two launch keys for a path into your clone — every env key is unchanged:

"command": "node",

"args": ["/path/to/tracelane/apps/mcp/dist/index.js"]

Build it first with pnpm install && pnpm --filter @tracelanedev/mcp build.

The Streamable HTTP transport ships in this package (TRACELANE_MCP_TRANSPORT=http, see Transports) — run it yourself. There is no hosted endpoint: https://mcp.tracelane.dev does not resolve, so a url-style client entry has nothing to connect to.

Self-host (ClickHouse)

Set CLICKHOUSE_URL to read ClickHouse directly instead of the gateway — for a self-hosted or local Tracelane stack:

"mcpServers": { "tracelane": { "command": "npx", "args": ["@tracelanedev/mcp"], "env": { "TRACELANE_API_KEY": "tlane_YOUR_KEY", "TRACELANE_GATEWAY_URL": "https://gateway.tracelane.dev", "CLICKHOUSE_URL": "http://localhost:8123", "CLICKHOUSE_USER": "default", "CLICKHOUSE_PASSWORD": "…" } } } }

TRACELANE_GATEWAY_URL is still needed in self-host mode — it is where TRACELANE_API_KEY is validated (/v1/auth/whoami) even though trace reads go to ClickHouse instead.

Tools

Tool	Description
`list_traces`	List recent traces for the tenant. Params: `limit` (default 20), `model_filter`, `has_error`
`get_trace`	Get all spans for a trace. Params: `trace_id`
`get_span`	Get full details for a span including all LLM GenAI attributes. Params: `span_id`, `trace_id` — required in Cloud (gateway) mode (no span-by-id gateway route; the span is picked out of the trace's span list), optional in self-host mode
`search_traces`	Free-text search across span names and attributes. Params: `query` (gateway mode requires ≥4 chars), `model_filter?`, `has_error?`, `limit`. Gateway mode returns content-filtered trace summaries; self-host mode returns per-span match detail (`matched_spans`, `first_match_*`)
`explain_guardrail_block`	Human-readable explanation of a guardrail signal. Self-host mode: `trace_id` + `span_id` (a detection-layer AFT flag on a recorded span). Gateway mode: EITHER `correlation_id` (from a block's 403 body, for a request blocked pre-flight with no trace) OR `trace_id` + `span_id` (same AFT-flag case, still available since spans carry the flag either way)
`list_evals`	List every pain-point + fault-tolerance eval id and count, read from the manifest bundled at build time from `evals/`. Params: none
`get_eval_result`	Read a specific eval's assertions. Needs a repo checkout for the source; says so when there is none. Params: `eval_id`
`replay_trace`	Return a recorded trace as-is (ordered spans with LLM/tool attributes) for offline step-through. Read-only — it does not re-execute any model or tool. Params: `trace_id`, `include_tool_calls?`

Example usage in Claude

Once connected, you can ask Claude:

"Show me the last 5 traces that had a guardrail block, and explain what fired."

"Compare the latency of traces using claude-haiku-4-5 vs claude-sonnet-4-6 in the last hour."

"Show me the assertions that eval makes."

Auth

TRACELANE_API_KEY environment variable passed via the MCP env block. The server resolves the tenant from the API key — tenant_id is never accepted as a tool argument.

Transports

Transport	How to select it	When to use
Stdio	default	Local use — Claude Desktop, Claude Code, Cursor. Zero network exposure.
Streamable HTTP	`TRACELANE_MCP_TRANSPORT=http TRACELANE_MCP_PORT=8081`	Self-run remote deployments. Every request must carry `Authorization: Bearer` ; the tenant is resolved per request through the gateway. No hosted endpoint is operated for you.

Security invariants

Read-only. No write tools are registered — the tool surface is the eight listed above, all of which only read.
Tenant isolation. Gateway mode: every read is a tenant-scoped gateway route (crates/gateway/src/trace_reads.rs) — the tenant comes from the bearer's claims server-side, this server never sends or sees a tenant id. Self-host mode: every ClickHouse query includes WHERE tenant_id = {tenantId: String} (parameter-bound, never string-interpolated).
`tenant_id` is never a tool parameter in either mode. Stdio resolves it once at startup from TRACELANE_API_KEY via the gateway and refuses to start if the key is rejected; HTTP resolves it per request from the bearer token and binds it through AsyncLocalStorage.
A non-2xx gateway response is a tool error, never an empty result. A revoked or wrong-tenant key, a key missing the read scope, or another tenant's trace id all read back as isError: true carrying the gateway's own status and message — not [].
No eval id reaches the filesystem. get_eval_result looks the id up in the bundled manifest and uses the manifest's path, so a traversal string cannot name a file.
`TRACELANE_GATEWAY_URL` is SSRF-checked before any bearer is sent to it, in both modes: https-only outside development, tracelane.dev hosts only, private/CGNAT/IMDS ranges refused.

Operator note: span content is returned as stored. Scope the API key you give this server to workspaces whose spans you are comfortable handing to the connected model.

Self-hosting

# From source, against your own stack

pnpm dev:mcp

No container image is published for the MCP server — ghcr.io/tracelane/mcp does not exist. Run it from source or from the npm package.

Stack

@modelcontextprotocol/sdk — official MCP SDK (stdio + Streamable HTTP)
@clickhouse/client — parameter-bound ClickHouse queries
TypeScript 5.5 strict, noUncheckedIndexedAccess: true
Biome for lint + format

License

Apache 2.0 — see LICENSE.

Tracelane MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Reelsaw

README from the maker

@tracelanedev/mcp — Tracelane MCP Server

Quick start

Cloud (Tracelane-hosted tenant)

Run from a clone

Self-host (ClickHouse)

Tools

Example usage in Claude

Auth

Transports

Security invariants

Self-hosting

Stack

License

`@tracelanedev/mcp` — Tracelane MCP Server