"Information about using cursors in Supabase" matching MCP connectors:
GET /v1/connectors ā MCP directory API referenceMatching Connector Tools:
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.
Read your team's hosted journal from an AI agent: every machine's streams, in hub order.
Ask your AI about your EventSend events, delivery health and usage.
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.
Oviond brings data from 100+ marketing platforms into one reporting platform. Through the Oviond MCP server, AI assistants can securely access and work with Oviond clients, projects, reports, dashboards, widgets, and marketing data. Ask questions about your reporting data, analyze marketing performance, and manage reporting workflows directly through your AI assistant.
MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.
Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.
Read-only WooCommerce checkout and revenue incident diagnosis using privacy-safe store signals and public release evidence.
Uptime and website monitoring for AI agents. Query monitor status, incidents, heartbeats, domain expiry, and status pages in your Vantaj Uptime workspace.
Know when cron jobs and AI agents stop running: create monitors and check in from your agent.
Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language.
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
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
- Session Replay MCPOAuth unavailablecom.session-replay
MCP for retrieving information about recorded session replays.
- aictrlOAuthdev.aictrl
Governance and grounding layer for engineering teams running AI coding agents (Claude Code, Cursor, Codex). Grounds agents in your codebase's knowledge graph, and adds session audit, policy controls and cost/token visibility.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Connect engineering metrics, DORA performance, and deploy risk scoring to any AI assistant. Score PRs for deployment risk using a 36-signal model, query team health, incidents, coverage, and more.
MCP server for 0001SENSATIONS: 107-level textual descent, append-only trace logging
Proxy Gemini (Vertex AI) completions wrapped in OpenTelemetry trace spans; returns the answer plus t
