Independent monitoring: status, monitors, and incidents from your StackWitness workspace.
Connect Remote server
claude mcp add --transport http mcp https://mcp.stackwitness.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"{
"mcpServers": {
"mcp": {
"url": "https://mcp.stackwitness.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.stackwitness.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://mcp.stackwitness.com/mcpReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | OAuth 2.1 bearer token from StackWitness (WorkOS AuthKit). Obtained automatically by MCP clients via the advertised OAuth flow; no API key. |
Details
| Endpoint | https://mcp.stackwitness.com/mcp (Streamable HTTP) |
| First published | 1 Sep 2026 |
| Last updated | 1 Sep 2026 |
| Registry name | com.stackwitness/mcp |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.