"Better Stack" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Production errors your coding agent can read: search, stack traces, releases, resolve, setup.
Vigilia watches your live app, explains every problem in plain language and writes the fix prompt. Your AI fixes it; Vigilia confirms with real traffic. Vigilia watches web apps that are live with real users, including apps built with Lovable, Bolt, v0, Cursor and Claude Code. It catches errors, failed requests and downtime, explains each problem in plain language, and writes a fix prompt for it. Connect Vigilia to Claude and ask what's broken. Claude lists your open incidents worst first. For each one it reads the plain-language diagnosis, who it affects, the technical evidence (error, page, failing request, stack frames and what the visitor did right before) and Vigilia's fix prompt. In Claude Code or another coding agent, Claude can then fix the cause in your own codebase. Once you've deployed, it marks the incident fixed, and Vigilia watches real traffic to confirm the error stayed away. If it comes back, the incident reopens as a regression. You can also ask how an app is doing (uptime, open incidents, today's traffic), get the exact install snippet for a new project, and check that a live site is running Vigilia. Vigilia never reads or changes your code: the fixing happens in your session, by your AI, in front of you. The only tool that changes anything is marking an incident fixed (the install check just records its result on the app), and you can connect with read-only access. Your data is stored in the EU. Emails, tokens and card numbers are stripped from what visitors' browsers send, and only that scrubbed error context is sent to Anthropic to write the diagnosis. Requires a Vigilia account. The free plan covers one app; reporting backend errors (Supabase, Next.js routes, Workers) is part of Pro.
Exception tracking for .NET. Let your AI coding agent search and triage errors and stack traces.
Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.
Observable Backend Stack Generator
Postgres + Grafana Stack Generator
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Read Epure error tracking issues from Claude Code, Cursor or Codex: stack, release and count.
AI SRE: investigate production incidents across your observability stack.
Investigate production issues: what changed, logs, metrics, dependencies and fixes in your stack.
Production errors and incidents for your agent: stack traces, breadcrumbs, likely causes, triage.
Production bugs with replay, network, console and stack, ranked for your coding agent to fix.
Kafka and Postgres Monitoring Stack
Monitor, troubleshoot, and optimize your technology stack with Intelligent Observability.