Production Monitoring MCP
This server connects AI assistants to live production observability stacks (Sentry, GitHub, Vercel, Better Stack, Cloudflare) to investigate incidents, correlate deployments with errors, and diagnose performance issues.
Overall health checks —
get_production_healthandget_observability_statusgive a single-call pulse across uptime, error spikes, deployments, and 5xx rates, plus integration/credential status.Error investigation (Sentry) — List recent production errors with frequency and affected users (
get_recent_errors), fetch full stacktraces, code context, tags, and breadcrumbs (get_error_details), and find regressions tied to a release (find_regression).Deployment tracking (Vercel/GitHub) — Retrieve recent deployments with commit SHAs and authors (
get_deployments), fetch build/runtime logs for a deployment (get_deployment_logs), compare commit ranges or deployments (compare_deployments), and inspect commit stats and diffs (get_commit_details).Uptime & log analysis (Better Stack) — Check monitor availability/incidents (
check_uptime) and query structured application logs for anomalies (analyze_logs).Edge traffic analysis (Cloudflare) — Inspect status code distribution (2xx/4xx/5xx) and error rates (
analyze_api_latency).Automated incident triage — Cross-correlate deployments, git diffs, and Sentry stacktraces to pinpoint root cause (
correlate_incident), and generate a human-readable executive briefing with evidence and recommendations (explain_incident).
Provides tools for checking uptime and availability, monitor statuses (up/down), and active incidents, plus querying structured application logs for error spikes and log anomalies.
Provides tools for analyzing API latency and edge traffic, including response distribution (2xx/4xx/5xx) and error rates.
Provides tools for inspecting git commits and diffs: comparing two commit SHAs/tags to return commit logs and changed files, and retrieving commit details such as author, message, stats, and patch snippets.
Provides tools for querying production errors: recent errors with frequency counts and affected users, full stacktraces with code context, tags and breadcrumbs, and detection of regressions or issues introduced in a given release.
Provides tools for fetching recent production and preview deployments and retrieving runtime and build logs for a specific deployment ID.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Production Monitoring MCP why did checkout errors spike after yesterday's deploy?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🛰️ Production Monitoring MCP
A production-grade Model Context Protocol (MCP) server that connects AI assistants directly to live observability stacks: Sentry, GitHub, Vercel, Better Stack, and Cloudflare.
Empowers AI agents to investigate production incidents, correlate code diffs with stack traces, diagnose latency anomalies, and triage regressions end-to-end.
🏗️ Architecture
AI Agent (Antigravity / Claude / Cursor)
│
▼ [Model Context Protocol (JSON-RPC over stdio)]
┌────────────────────────────────────────────────────────┐
│ Production Monitoring MCP Server │
│ │
│ ┌──────────────────────────────────────────────────┐ │
│ │ Incident Correlation & Triage Engine │ │
│ └──────────────────────┬───────────────────────────┘ │
│ │ │
│ ┌─────────┬───────┴───────┬─────────┐ │
│ ▼ ▼ ▼ ▼ │
│ [Sentry] [GitHub] [Vercel] [Better Stack] │
│ (Errors & (Diffs & (Deploys (Uptime & │
│ Traces) Commits) & Logs) Logtail) │
└───────┬─────────┬───────────────┬─────────┬────────────┘
▼ ▼ ▼ ▼
Live Production APIs (Read-Only Authentication)Related MCP server: agent-debugger
🛠️ Tools Exposed to AI Agents
Tool Name | Provider | Description |
| Pulse Engine | Single-call operational pulse across uptime, Sentry error spikes, latest deployments, and 5xx rates. |
| MCP Core | Verifies health of all integrations and surfaces missing keys. |
| Sentry | Lists recent production errors, frequency count, and affected users. |
| Sentry | Returns full stacktrace, code context, tags, and breadcrumbs. |
| Sentry | Identifies regressed errors or issues introduced in a given release. |
| Vercel / GitHub | Fetches recent production deployments, commit SHAs, and authors. |
| Vercel / GitHub | Alias for |
| Vercel | Fetches runtime and build logs for a specific deployment ID. |
| GitHub | Compares two commit SHAs/tags: returns commit log and changed file diffs. |
| GitHub | Retrieves author, commit message, stats, and patch snippets. |
| Better Stack | Checks availability, monitor statuses ( |
| Better Stack Logs | Queries structured application logs for error spikes and log anomalies. |
| Cloudflare | Queries edge traffic, response distribution (2xx/4xx/5xx), and error rates. |
| Correlation Engine | Cross-correlates deployment commits with Sentry stacktraces and telemetry for root cause analysis. |
| Synthesis Engine | Generates a human-readable executive briefing with suspected root cause, evidence chain, and recommendation. |
🚀 How the Incident Triage Flow Works
When an engineer asks:
"Why did checkout conversion drop after yesterday's deployment?"
The agent executes the following multi-system triage chain:
sequenceDiagram
autonumber
actor User as Engineer
participant Agent as AI Assistant
participant MCP as Monitoring MCP
participant Vercel as Vercel
participant GitHub as GitHub
participant Sentry as Sentry
User->>Agent: "Why did checkout fail after yesterday's deploy?"
Agent->>MCP: get_deployments(environment="production")
MCP->>Vercel: Fetch latest 2 deployments
Vercel-->>Agent: Deployment A (prev: 8a1f4b) & Deployment B (curr: 3c9e21)
Agent->>MCP: compare_deployments(base="8a1f4b", head="3c9e21")
MCP->>GitHub: Compare commit range
GitHub-->>Agent: 3 commits, modified: src/services/checkout.ts
Agent->>MCP: get_recent_errors(timeframe="24h")
MCP->>Sentry: Query unresolved errors
Sentry-->>Agent: TypeError: Cannot read properties of undefined (reading 'taxRate')
Agent->>MCP: get_error_details(issue_id="...")
MCP->>Sentry: Fetch stacktrace
Sentry-->>Agent: Frame: src/services/checkout.ts:142
Agent->>User: "Root Cause Identified: PR #182 by @dev modified checkout.ts:142 removing default tax fallback, causing 420 runtime TypeErrors."⚙️ Quick Start (Interactive Setup Wizard)
1. Run the Setup Wizard
Run the interactive setup wizard via npx with zero local configuration required:
npx production-monitoring-mcp initThe terminal wizard will:
Let you choose the services you want to connect (Sentry, GitHub, Vercel, Better Stack, Cloudflare).
Prompt for your tokens and test each API connection live with real-time feedback.
Save your credentials securely in your machine's user configuration directory (
conf).Automatically configure Claude Desktop and local AI clients with zero manual editing.
2. Verify Connection Health
Run the built-in diagnostic doctor at any time:
npx production-monitoring-mcp doctor🔌 Connecting to AI Clients
Automatic Configuration
If you didn't run the installer during init, configure your local AI clients with:
npx production-monitoring-mcp installManual Configuration
You can also add it manually to your client config:
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"production-monitoring": {
"command": "npx",
"args": ["-y", "production-monitoring-mcp"]
}
}
}Antigravity CLI / Gemini / Cursor (mcp_servers.json)
{
"mcpServers": {
"production-monitoring": {
"command": "npx",
"args": ["-y", "production-monitoring-mcp"]
}
}
}(You can also pass environment variables directly in the "env" block if you prefer not to use the local config store)
🛡️ Production Security
Read-Only Scopes: Only read permissions (
project:read,event:read,repo:read,deployments:read) are required.Local Execution: All requests are executed directly from your local machine over HTTPS with no third-party telemetry.
Graceful Degradation: Unconfigured services return clear guidance without failing the entire server.
Available Tools
14 toolsanalyze_api_latencyC
Analyze edge HTTP traffic, status codes (2xx, 4xx, 5xx), and error rates from Cloudflare Analytics.
Inputs: zone_id, timeframe_minutes.
analyze_logsB
Query structured application logs from Better Stack Logs to investigate log anomalies, errors, and traces.
Inputs: to, from, limit, query.
check_uptimeB
Query Better Stack Uptime monitors to check availability, status (up/down), and recent downtime incidents.
Inputs: no named parameters.
compare_deploymentsA
Compare two deployments or commit SHAs via GitHub to see all commits, authors, and exact files changed.
Inputs: base_sha (required), head_sha (required), repo, owner.
correlate_incidentC
Run automated triage correlating deployment timestamps, git diffs, and Sentry stacktraces to find the root cause.
Inputs: service_or_project (required), repo, owner, timeframe, +1 more.
explain_incidentB
Generates a human-readable executive briefing of an incident with root cause, evidence chain, confidence, and recommended action.
Inputs: service_or_project (required), repo, owner, timeframe, +1 more.
find_regressionC
Find errors in Sentry that have regressed or were first introduced in a specific release or timeframe.
Inputs: project, release, timeframe.
get_commit_detailsB
Inspect a specific GitHub commit's message, author, stats, and modified files with diff snippets.
Inputs: sha (required), repo, owner.
get_deployment_logsA
Fetch runtime and build logs for a specific Vercel deployment to diagnose deployment failures.
Inputs: deployment_id (required), limit.
get_deploymentsB
Fetch recent deployments from Vercel (or GitHub) with deployment state, commit SHA, branch, and timestamp.
Inputs: limit, project, environment.
get_error_detailsA
Fetch deep technical details for a specific Sentry issue including parsed in-app stack trace frames, code context, tags, and breadcrumbs.
Inputs: issue_id (required).
get_observability_statusA
Inspect the status of connected production monitoring providers (Sentry, GitHub, Vercel, Better Stack, Cloudflare) and list any missing credentials.
Inputs: no named parameters.
get_production_healthA
Single-call operational pulse across all connected services (Uptime, Sentry error spikes, latest Vercel deploy, Cloudflare 5xx). Returns lean status signals rather than verbose raw logs.
Inputs: project.
get_recent_errorsA
Fetch recent production errors from Sentry for a project or service, including frequency counts, first/last seen timestamps, and affected user counts.
Inputs: limit, query, project, timeframe.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools target distinct resource+action pairs (Sentry errors vs deployments vs uptime vs latency), and descriptions clarify boundaries. Slight overlap between get_production_health and get_observability_status (a pulse vs provider/credential status), and correlate_incident/explain_incident form a related triage/briefing pair, but each remains differentiable.
All 14 tools use snake_case with a consistent verb_noun pattern (get_recent_errors, check_uptime, analyze_logs, compare_deployments, explain_incident). No mixing of camelCase or vague bare verbs.
14 tools is well within the ideal 3-15 range and each earns its place across distinct monitoring and incident-response stages. No redundant or filler tools.
The surface covers the full incident lifecycle: detection (health, errors, uptime, latency), investigation (error details, deployment logs, commit details, regressions), correlation (correlate_incident), and reporting (explain_incident). No obvious dead ends for the stated production monitoring purpose.
Related MCP Connectors
AI SRE: investigate production incidents across your observability stack.
AI agent observability for production traces, natural-language insights, and improvement loops.
The AI orchestration agent for modern software teams.
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
Related MCP Servers
- AlicenseAqualityDmaintenanceCross-cloud observability for AI agents. Discover resources, correlate logs, and diagnose infrastructure issues across AWS, GCP, Vercel, and Cloudflare — without leaving your editor.464 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to investigate backend incidents by executing runbooks that gather evidence from observability and storage systems.9MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI-driven incident response by connecting Claude to monitoring tools like Prometheus, Grafana, Loki, PagerDuty, and Slack for automated investigation and runbook generation.9-
- AlicenseAqualityCmaintenanceLets AI agents query, manage, and operate their LLM observability data directly from the conversation. Provides 87 tools for cost analysis, alerting, anomaly detection, and runtime control gates.87260 npmMIT