Tallwatch
Tallwatch MCP
Public install wrapper for the Tallwatch MCP server. The server is hosted at https://api.tallwatch.com/mcp. There is no npm package and no local npx process.
Check org status, list monitors, triage incidents, see who is on call, and (with a write key) pause monitors or ack/resolve incidents. Same ops surface as the CLI. Guide: docs.tallwatch.com/integrations/mcp.
This repo holds the Cursor plugin files. The server code lives in the Tallwatch API (packages/mcp).
Install
Create a key in Settings → API keys. The
tw_live_…secret is shown once. Copy prompt on that page pastes client-specific setup into the agent.Merge the block for this client. Prefer user-level config so the key is not git-tracked. The URL field name is not the same in every client; the wrong key is ignored or falls back to SSE.
Cursor (~/.cursor/mcp.json). Remote entries use url and headers. Do not set type.
{
"mcpServers": {
"tallwatch": {
"url": "https://api.tallwatch.com/mcp",
"headers": {
"Authorization": "Bearer tw_live_your_key_here"
}
}
}
}You can put the secret in the environment instead: "Authorization": "Bearer ${env:TALLWATCH_API_KEY}". Reload MCP in Cursor Settings.
Client | Config |
Cursor |
|
VS Code | Command Palette → MCP: Open User Configuration, or |
Claude Code |
|
Claude Desktop |
|
Codex |
|
Devin Desktop |
|
Devin CLI |
|
Gemini CLI |
|
Cline |
|
Continue |
|
VS Code:
{
"servers": {
"tallwatch": {
"type": "http",
"url": "https://api.tallwatch.com/mcp",
"headers": {
"Authorization": "Bearer tw_live_your_key_here"
}
}
}
}Codex:
[mcp_servers.tallwatch]
url = "https://api.tallwatch.com/mcp"
bearer_token_env_var = "TALLWATCH_API_KEY"Full snippets: docs.tallwatch.com/integrations/mcp.
Related MCP server: Drumbeats MCP
Tools
Prefer get_status when asking what is broken. Same capability set as the CLI (minus browser login / browse / import).
Scope | Tools |
|
|
|
|
This server cannot be deployed
Maintenance
Related MCP Connectors
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.
MCP uptime, schema, auth, and SLA receipt monitoring.
AI-powered website change monitoring - manage monitors and alerts via MCP.
Related MCP Servers
- AlicenseBqualityBmaintenanceRun NRQL, NerdGraph, and REST v2 operations to query data, manage incidents, create synthetics, and annotate deployments — all from your MCP client.18712 npm15MIT

Drumbeats MCPofficial
AlicenseAqualityAmaintenanceMCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.1610 npm2Apache 2.0- AlicenseNot gradedqualityCmaintenanceMCP server for investigating cloud incidents and managing approvals. Provides read-only tools to list incidents, investigate incidents, and list approvals, keeping remediation behind human approval.MIT
- FlicenseNot gradedqualityDmaintenanceMonitors MCP server uptime, auth failures, schema drift, and SLA evidence.-