Prism

A drop-in telemetry bridge that sits between any chat or agent and any MCP server, streaming OpenTelemetry spans for every JSON-RPC turn: tool calls, resource…

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Prism Info: Returns Prism's service identity and runtime state: version, transport, public URL, capture default, and the number of MCP sessions currently being traced. Use this to confirm which Prism
  • Prism Ping: Returns {"pong": true, "time": <unix seconds>} plus an optional echo of the 'echo' argument. Use to verify connectivity through the gateway before pointing it at an upstream MCP server.
  • Prism Metrics: Dumps Prism's in-process counters and gauges — spans shipped, upstream errors, rate-limit hits, queue depth. Two formats: 'prometheus' (default, scrape-ready text) or 'json' (a {"series

What data it sees

Do you need an account

No: the server works without sign-in

A drop-in telemetry bridge that sits between any chat or agent and any MCP server, streaming OpenTelemetry spans for every JSON-RPC turn: tool calls, resource reads, prompts, progress events, errors, and latency.

No SDK. No code changes. Point your client at Prism and you get distributed tracing.

  • Every call becomes a span: method, duration, status, payload size, session and trace correlation, redacted arguments
  • Fan-out telemetry: ship spans to Telinea (hosted dashboard, launching October 1st) or any OTLP endpoint: Jaeger, Honeycomb, Datadog, Grafana Tempo
  • Transparent relay: Streamable HTTP and legacy SSE pass through untouched; your server never knows Prism is there
  • Session-aware: spans group into traces per MCP session, so you see whole conversations, not isolated calls
  • Safe by default: secrets redacted at intake, SSRF-guarded upstreams, per-token rate limiting, dead-letter buffering so spans survive downstream outages

When you set telineaApiKey, Prism delivers your spans to Telinea's dedicated OTLP ingest at https://ingest.terradev.cloud/v1/traces — a high-throughput endpoint built for binary protobuf telemetry, landing in your dashboard in real time.

Already have OpenTelemetry producers like LangChain pipelines, CI/CD agents, vLLM servers? They can POST OTLP straight to the same ingest point, no Prism needed. One endpoint, one dashboard, all your spans. Telinea launches October 1st.

How to connect

How to connect Prism to Claude

The server address to paste into Claude settings:

https://prism--wolfendentheo.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Prism to ChatGPT

The server address to paste into ChatGPT settings:

https://prism--wolfendentheo.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Prism to Cursor

The server address to paste into Cursor settings:

https://prism--wolfendentheo.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (6)

Raw names from tools/list. Only developers need these.

prism_infoReturns Prism's service identity and runtime state: version, transport, public URL, capture default, and the number of MCP sessions currently being traced. Use this to confirm which Prism deployment you are talking to and whether it is healthy before configuring an upstream.
prism_pingReturns {"pong": true, "time": <unix seconds>} plus an optional echo of the 'echo' argument. Use to verify connectivity through the gateway before pointing it at an upstream MCP server.
prism_metricsDumps Prism's in-process counters and gauges — spans shipped, upstream errors, rate-limit hits, queue depth. Two formats: 'prometheus' (default, scrape-ready text) or 'json' (a {"series{labels}": value} object). Use 'prefix' to narrow to a metric family, e.g. 'prism_spans'.
prism_sessionsLists the MCP sessions Prism is currently tracing — session id prefix, upstream, client name, project, turn and error counts, and age in seconds. Use 'limit' to cap results (default 20, max 100) and 'upstream' to filter by upstream URL substring.
prism_configReturns Prism's effective runtime configuration — upstream allowlist, rate limit, capture default, batching and queue tunables, public URL, and configured ingest endpoints. Secrets (admin token, destination credentials) are never exposed — only whether they are set.
prism_helpReturns connection instructions: how to set the upstream MCP server (X-Prism-Upstream header or ?upstream= query param), the query-param config keys for header-less clients, how destinations and the borrowed-token model work, and example client configs. Start here if you are an agent discovering Prism for the first time.