On-Call Health
Burnout risk analysis for on-call engineering teams, queried from an AI assistant
- Pricing
- Open source
- Platforms
- CLI
- Runs
- Locally
- Version
- 0.4.1
- Listing updated
- 3 days ago
About On-Call Health
On-Call Health is an open-source MCP server for health and science. It runs locally on your machine and is started by your AI client.
The server turns On-Call Health data into answers about workload: team risk summaries, which responders are at risk, and daily health trends. It runs locally over stdio, started with uvx from the PyPI package oncallhealth-mcp, and needs an API key from oncallhealth.ai settings in the ONCALLHEALTH_API_KEY variable.
The README suggests a workflow. Begin with validate_integrations to confirm the data sources are connected, then analysis_current for the latest analysis or analysis_run to start a fresh one, then analysis_summary and the member-level tools. While a run is in progress, the server polls every five seconds by default, backing off to thirty. An optional Code Mode exposes the tool catalogue through meta-tools instead of listing every tool.
It implements MCP revision 2026-07-28 and still negotiates older revisions. Every tool publishes read-only, idempotent and open-world annotations plus a structured output schema. The product site describes an open source tool that looks for early signs of overload in on-call engineers, from Rootly AI Labs.
Install
Run in a terminal
claude mcp add oncallhealth-mcp --env ONCALLHEALTH_API_KEY='<ONCALLHEALTH_API_KEY>' -- uvx oncallhealth-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"oncallhealth-mcp": {
"command": "uvx",
"args": [
"oncallhealth-mcp"
],
"env": {
"ONCALLHEALTH_API_KEY": "<ONCALLHEALTH_API_KEY>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"oncallhealth-mcp": {
"command": "uvx",
"args": [
"oncallhealth-mcp"
],
"env": {
"ONCALLHEALTH_API_KEY": "<ONCALLHEALTH_API_KEY>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"oncallhealth-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"oncallhealth-mcp"
],
"env": {
"ONCALLHEALTH_API_KEY": "<ONCALLHEALTH_API_KEY>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"oncallhealth-mcp": {
"command": "uvx",
"args": [
"oncallhealth-mcp"
],
"env": {
"ONCALLHEALTH_API_KEY": "<ONCALLHEALTH_API_KEY>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"oncallhealth-mcp": {
"command": "uvx",
"args": [
"oncallhealth-mcp"
],
"env": {
"ONCALLHEALTH_API_KEY": "<ONCALLHEALTH_API_KEY>"
}
}
}
}Configuration
ONCALLHEALTH_API_KEYOn-Call Health API key from https://oncallhealth.ai/settings/api-keysRequired
Tools this server provides (4)
Taken from the project documentation; the running server may differ.
- validate_integrations
- Checks that the connected data sources are working.
- analysis_current
- Returns the current analysis.
- analysis_run
- Starts a fresh analysis and polls until it completes.
- analysis_summary
- Returns a summary of an analysis.
What it does
- Team risk summaries
- Overview of burnout risk across an on-call team.
- At-risk responders
- Identify members showing strong overload signals.
- Daily health trends
- Track how team health changes day by day.
- Fresh analyses
- analysis_run starts a new analysis and polls until it finishes.
- Integration check
- validate_integrations confirms connected sources first.
- Tool annotations
- Every tool declares read-only, idempotent and structured output.
- Local stdio server
- Runs with uvx and a single API key.
Good for
- Check which responders are at risk this week
- Compare team health day by day after a bad incident
- Run a new burnout analysis before a rota change
- Summarise on-call load in a retro
Pricing
Open source
Open source tool from Rootly AI Labs; account and API key required
Prices change. Check oncallhealth.ai before you buy.
On-Call Health FAQ
What do I need to use it?
An On-Call Health account and an API key from oncallhealth.ai/settings/api-keys.
How is it installed?
Run it with uvx oncallhealth-mcp, or pip install oncallhealth-mcp, with ONCALLHEALTH_API_KEY set.
Which tool should I call first?
validate_integrations, then analysis_current or analysis_run.
Which clients are documented?
Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Codex CLI and Gemini CLI.
Can I point it at another API URL?
Yes, set ONCALLHEALTH_API_URL; the default is https://api.oncallhealth.ai.
Is On-Call Health free?
Yes. On-Call Health is open source, so you can use and self-host it for free.
How do I add On-Call Health to Claude Code?
Run this command in your terminal: claude mcp add oncallhealth-mcp --env ONCALLHEALTH_API_KEY='<ONCALLHEALTH_API_KEY>' -- uvx oncallhealth-mcp
What are the best alternatives to On-Call Health?
The closest alternatives to On-Call Health are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to On-Call Health

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Agent-Native Analytics
MCP serverOpen-source analytics app where an AI agent builds charts and dashboards from your data
- Remote
- Open source
- 7.7K GitHub stars
- Analytics and data