StackWitness MCP

Why this is different

• Independent measurement, not vendor self-report alone

  When you ask “is Stripe down?” the tools surface what our regions measured for hosts you track, alongside a read of the vendor status feed. That is the StackWitness wedge: an outside clock, not only the operator's story.

• OAuth, not API keys

  Authentication is OAuth 2.1 through WorkOS AuthKit. Your MCP client discovers the flow from the server's advertised metadata (RFC 9728). No long-lived API keys to mint, rotate, or leak into config files.

• Scoped to your organization

  Every tool call runs in your signed-in org. Monitors, status pages, and incidents you see are the ones that org owns.

What you can do

These are the live tools on the StackWitness MCP server today, phrased as jobs your assistant can take on:

• Ask if a dependency is down

  Call get_dependency_status for independently measured readings on providers your monitors declare, or list monitors and open one for latest state. Pair that with the vendor feed context your workspace already tracks.

• List open incidents and act on them

  list_incidents returns recent incidents with attribution and alert verdicts when available. open_incident, post_incident_update, and resolve_incident let you run the incident lifecycle from the assistant with the same rules as the dashboard.

• Spin up or manage a monitor

  create_monitor runs the same multi-sample probe and plan-limit checks as the UI. update_monitor, pause_monitor, resume_monitor, and delete_monitor keep the fleet honest without leaving your editor.

• Read status pages

  list_status_pages and get_status_page surface the pages your org publishes, so the assistant can answer “what are we showing customers?” from the source of truth.

How to connect

1. Have a StackWitness workspace on a paid plan. MCP is included with your StackWitness plan. If you are new, start monitoring and complete checkout.
2. Add the StackWitness MCP server in your client. Point a streamable-HTTP MCP server at:

   https://mcp.stackwitness.com/mcp

   In Claude Code, Cursor, and other clients that support remote MCP, add a server with that URL (often under MCP / tools settings). Prefer streamable HTTP when the client offers a transport choice.
3. Complete the OAuth sign-in when the client prompts you. The server advertises OAuth metadata. Your client discovers authorization automatically (RFC 9728). Sign in with the same WorkOS-backed account you use for StackWitness. After consent, tool calls are authorized for your organization.
4. Ask a real question. Examples: “List my StackWitness monitors.” “What does get_dependency_status show right now?” “Open incidents for my org.” “Create a monitor for https://example.com/health.”

Endpoint: https://mcp.stackwitness.com/mcp. Protocol: Model Context Protocol over streamable HTTP. Auth: OAuth 2.1 via WorkOS. No API keys.

Questions