"Using code execution to replace native tooling" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Connect Claude.ai, ChatGPT and MCP-compatible coding clients to aictrl engineering workflows. Check account readiness, find and run tasks, inspect workflow progress and approvals, review pull-request findings, and query repository context. Uses OAuth and your aictrl organisation's permissions.
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.
Understand who uses your MCP servers, what they’re trying to accomplish, and where workflows get stuck. Analyze tool adoption, user journeys, reported outcomes, and business signals directly from your AI assistant, with evidence from individual sessions.
Read-only access to an ET Ducky organization's Windows and Linux agents, alerts, and fleet summary. Four tools list agents, get one agent with its latest health sample, list alerts, and summarize the fleet. Hosted Streamable HTTP endpoint, authenticated with an organization API token sent as a Bearer header.
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.
Fixter's MCP provides a stream-lined agentic way to onboard, setup and use the Fixter monitoring and observability platform. Check out more at https://fixter.dev/
Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
Trace events to function runs to the failing step, and bulk-cancel runs.
Read-only access to an ET Ducky organization's agents, alerts, and fleet summary
Bounded authorization and independently verifiable execution evidence for agents.
Matches sanitized business needs to fixed-price services and routes authorized agents to purchase.
Read-only WooCommerce checkout and revenue incident diagnosis using privacy-safe store signals and public release evidence.
Read-only watchtower for AI agents on-chain: decoded receipts, plan vs execution, Safe audits.
Read-only MCP access to sessions, funnels, campaigns, errors, live visitors, and anomalies.
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
Report-To group count, body discarded
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.
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.
MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.
Hash-chained HMAC-signed audit log MCP for A2A (agent-to-agent) calls. Every tool-call, agent-ha...
