"Debugging WebRTC SDK Implementation Issues in Visual Studio 2019" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Read LogBrew errors, slow traces, logs, and product analytics, and triage issues with consent.
AI-native observability and security for engineering teams and coding agents. Search production logs in plain language, investigate issues and root causes, and create or edit live dashboards in your Sazabi workspace. Requires a Sazabi account (OAuth, or a secret key via the X-Sazabi-Secret-Key header).
Uptime monitoring, status pages and on-call in one place. Create and tune monitors for HTTP, TCP, DNS, ping, TLS certificates, domain expiry, heartbeats and scripted browser logins. Run a check on demand, read uptime and response-time history, acknowledge and resolve incidents, post incident updates, schedule maintenance windows and edit public status pages. Read-only until you grant write access.
Project context, backlog tasks, and controlled workflows for coding agents. OAuth sign-in.
Live vendor incidents in your AI assistant. Hundreds of status pages, one feed. Free active-outage checks with no signup; sign in for history, watchlists, and monitoring tools. Setup: https://www.huntertech.io/vendor-mcp
Query your AI agents' traces, errors, cost and alerts in Rius, the agent observability platform.
Relia tells your AI assistant what broke in production, who it hit and how to fix it.
Game observability for Three.js, Phaser, Babylon.js, PlayCanvas, Unity, Godot, Unreal and GameMaker games. Ask what's wrong with your game and get ranked findings from real players' sessions: frame-time spikes by level, errors with the gameplay just before them, where players die, version comparisons, store reviews and each game's own dashboard. Sign in with your Glitchless account (OAuth); a new workspace can start on a demo game.
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.
Combined Server-Surface Census: identity, tool contract + skill digests in one signed snapshot.
Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.
Read your team's hosted journal from an AI agent: every machine's streams, in hub order.
Salvageability triage for agent fleets in a declared mass-failure mode.
Guardr keeps watch on the sites you manage. Check any domain from outside and get an A to F health grade for HTTP headers, TLS, DNS and cookies, with fix steps for configuration findings. Three tools: check_site runs a fresh check of one domain, list_sites lists the sites your account watches and get_site returns one watched site in detail. Read-only: Guardr proposes fixes and never changes a site. Needs a Guardr API key; the first site is free.
Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language.
Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
Uptime and website monitoring for AI agents. Query monitor status, incidents, heartbeats, domain expiry, and status pages in your Vantaj Uptime workspace.
RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
Check infrastructure health, manage incidents, and run runbooks in Faultline.
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.
Correlate GitHub releases with Sentry issues and PagerDuty incidents.
MCP-native AI SRE. Exposes your production OpenTelemetry problems, traces, and logs over the Model Context Protocol, plus an AI remediation loop that opens a reviewed GitHub fix PR and verifies in production (reopening on regression). Tools include list_problems, get_problem, query_traces, detect_anomalies, and request_problem_remediation. Human-in-the-loop by default — the merge button stays yours.
Read status pages, incidents and monitors, and post incidents and maintenance in StatusPage.me.
MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.
Watches your live app, explains every problem in plain language and writes the fix prompt.
Mezmo MCP is a remote Model Context Protocol (MCP) server that lets AI assistants and IDE chat agents interact with the Mezmo observability platform via the Model Context Protocol. Use it for streamlined observability, log analysis, and root-cause analysis in your favorite tools. Add Mezmo MCP and you can: 🕵️ Run advanced Root-cause analysis over recent logs 📦 List and describe Pipelines 📤 Export and filter Logs with powerful query syntax
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
