Read-only, tenant-scoped access to Tracelane agent traces and guardrail verdicts
Tracelane-mcp is an MCP integration. Read-only, tenant-scoped access to Tracelane agent traces and guardrail verdicts.
The published npm package is @tracelanedev/mcp, version 0.4.0. Its declared MCP transport is stdio.
The package declares TRACELANE_API_KEY (required): 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 through the gateway when CLICKHOUSE_URL is unset.; TRACELANE_GATEWAY_URL (required): 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: 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: ClickHouse username.; CLICKHOUSE_PASSWORD: ClickHouse password.; CLICKHOUSE_DB: ClickHouse database holding the spans table.; TRACELANE_MCP_TRANSPORT: Transport to serve. stdio (default) for desktop clients; http for the Streamable HTTP transport..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.4.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| TRACELANE_API_KEY | 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 through the gateway when CLICKHOUSE_URL is unset. | Yes |
| TRACELANE_GATEWAY_URL | 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. | Yes |
| CLICKHOUSE_URL | 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. | Check documentation |
| CLICKHOUSE_USER | ClickHouse username. | Check documentation |
| CLICKHOUSE_PASSWORD | ClickHouse password. | Check documentation |
| CLICKHOUSE_DB | ClickHouse database holding the spans table. | Check documentation |
| TRACELANE_MCP_TRANSPORT | Transport to serve. stdio (default) for desktop clients; http for the Streamable HTTP transport. | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.