"Creating an Automation System Using n8n" matching MCP connectors:
Matching Connector Tools:
Read-only triage for n8n, MCP, webhook, and AI agent workflow production failures.
Run a prompt through a LangChain (system + human) chain over Gemini on Vertex AI; optional LangSmith
Public MCP digital twin with synthetic systems and an agent firewall. No customer data.
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.
DORA OS Conductor — 16-tool meta-orchestrator for DORA compliance workflow automation.
An MCP server giving access to Grafana dashboards, data and more.
High-performance array aggregation and metrics clearing engine. Cleans and bucket-groups noisy metric streams via an $O(N)$ single-pass data sweep. Operates natively with the pay-per-call x402 micropayment framework.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Know when your n8n workflows, URLs, and AI apps break, before your customers do.
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.
Paid remote MCP for agent design system guard MCP, structured receipts, audit logs, and reviewer-rea
System self-awareness, health monitoring, and autonomous self-repair
Debug production issues using Shipbook logs and Loglytics error insights.
The Buildkite MCP server exposes Buildkite product data (pipelines, builds, jobs, and test data) to AI tools, editors, and agents through the Model Context Protocol. It provides capabilities including pipeline creation and management, build monitoring with specialized tools like 'wait_for_build', efficient log querying using Apache Parquet conversion and caching, and OAuth-based authentication for both read-write and read-only access to Buildkite's REST API.