Skip to main content
Glama
TraceOrb

traceorb-mcp

Official
by TraceOrb
README.md
# traceorb-mcp

MCP server for [Traceorb](https://traceorb.com). Any MCP client can query your org's telemetry through the same GETs the panel uses.

## Install

Node.js ≥ 22 and `npx` on `PATH`. Create a **read key** in Traceorb Settings. The secret is shown once. Do not commit it.

```bash
npx -y traceorb-mcp
```

The process speaks MCP over stdio. It does not start unless `TRACEORB_READ_KEY` is set.

## Environment

| Variable | Required | Default |
| --- | --- | --- |
| `TRACEORB_READ_KEY` | yes | — |
| `TRACEORB_API_URL` | no | `https://api.traceorb.com` |

## Configure

Point the client at this stdio server:

```json
{
  "command": "npx",
  "args": ["-y", "traceorb-mcp"],
  "env": {
    "TRACEORB_READ_KEY": "<token>",
    "TRACEORB_API_URL": "https://api.traceorb.com"
  }
}
```

Where that JSON lives depends on the client.

### Cursor

`~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this repo):

```json
{
  "mcpServers": {
    "traceorb": {
      "command": "npx",
      "args": ["-y", "traceorb-mcp"],
      "env": {
        "TRACEORB_READ_KEY": "<token>",
        "TRACEORB_API_URL": "https://api.traceorb.com"
      }
    }
  }
}
```

### Claude Desktop

macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`

Windows: `%APPDATA%\Claude\claude_desktop_config.json`

Same `mcpServers.traceorb` object as Cursor. Restart Claude Desktop.

### Claude Code

Project file `.mcp.json`, or:

```bash
claude mcp add --transport stdio --env TRACEORB_READ_KEY=<token> --env TRACEORB_API_URL=https://api.traceorb.com traceorb -- npx -y traceorb-mcp
```

### VS Code (Copilot)

`.vscode/mcp.json` in the workspace, or user MCP settings:

```json
{
  "servers": {
    "traceorb": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "traceorb-mcp"],
      "env": {
        "TRACEORB_READ_KEY": "<token>",
        "TRACEORB_API_URL": "https://api.traceorb.com"
      }
    }
  }
}
```

### Other MCP clients

Any client that runs a stdio server: `command` `npx`, `args` `["-y", "traceorb-mcp"]`, and the two env vars above. Restart the client after saving.

License: MIT.

TDQS

B3.2/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct resource and action: metrics, daily metrics, requests (list/get/compare), facets, and alert rules/incidents/firing-count. Even with similar descriptions, the names and endpoints make boundaries unambiguous.

Naming Consistency5/5

All tool names use a consistent verb_noun snake_case pattern: query_*, list_*, get_*, search_*, get_* with clear objects. The verb choice varies slightly but is semantically coherent and predictable.

Tool Count5/5

10 tools is well-scoped for a telemetry/observability server. It covers the primary data surfaces—metrics, requests, facets, and alerts—without unnecessary duplication or bloat.

Completeness4/5

The surface provides comprehensive read-only coverage for the domain: metrics variants, request lookups and comparison, facet search, alert rule listing, incident retrieval and firing counts. The only minor gap is lack of a get_alert_rule endpoint, but the listing makes this workable.

Maintenance

ActivityMaintained
ResponsivenessNo issues