NestJS Observe MCP: production telemetry for your coding agent

Connect NestJS Observe to Cursor, Claude or ChatGPT

1. 1Click Connect NestJS Observe free and sign in to NestJS Observe.
2. 2All tools are on after connecting, and the list appears then. Keep the trace and error tools for debugging, and switch off anything that changes alerts if your on-call setup should only be changed by hand.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Ask Cursor why an endpoint got slower after yesterday's deploy, using NestJS Observe traces, then open Activity to see the call.

Debug with production data

• Pull traces for a slow request while you look at the handler in Cursor.
• List recent errors and the regressions behind them.
• Check how your background jobs are running.
• Review alerts from a chat.

Telemetry with guardrails

• Traces and errors can contain user data; a policy can hide personal data before your AI app sees it.
• Activity records each telemetry query.
• Switch off any NestJS Observe tool you don't want your agent calling.

What you get with NestJS Observe and ContextGate

• Your AI apps can use NestJS ObserveClaude, Cursor, ChatGPT and other AI apps reach NestJS Observe through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any NestJS Observe tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

NestJS Observe tools

NestJS Observe's own MCP server shows its tools once you sign in. When you connect it, they are listed and synced in your workspace.