get_on_call_schedule — hyperping MCP Tool Read-only
get_on_call_schedule
(get on call schedule) is one of 26 tools on the
hyperping
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_on_call_schedule from your client
- Claude Code hyperping get_on_call_schedule run in your project directory
- Claude Desktop hyperping get_on_call_schedule ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor hyperping get_on_call_schedule ~/.cursor/mcp.json
- VS Code hyperping get_on_call_schedule .vscode/mcp.json
- Zed hyperping get_on_call_schedule ~/.config/zed/settings.json
- Windsurf hyperping get_on_call_schedule ~/.codeium/windsurf/mcp_config.json
- Cline hyperping get_on_call_schedule ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI hyperping get_on_call_schedule ~/.gemini/settings.json
- Grok hyperping get_on_call_schedule .mcp.json (in your project root)
- ChatGPT hyperping get_on_call_schedule Settings → Connectors → Advanced → Developer mode
- Claude.ai hyperping get_on_call_schedule Settings → Connectors → Add custom connector
- LangChain hyperping get_on_call_schedule pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hyperping https://api.hyperping.io/v1/mcpOther tools on this server
- list_monitors
- get_monitor
- create_monitor
- update_monitor
- pause_monitor
- resume_monitor
- search_monitors_by_name
- get_status_summary
- list_outages
- get_outage
- get_outage_timeline
- get_monitor_outages
- list_recent_alerts
- get_monitor_uptime
- get_monitor_response_time
- get_monitor_mttr
- get_monitor_mtta
- get_monitor_anomalies
- get_monitor_http_logs
- list_on_call_schedules
- list_escalation_policies
- get_escalation_policy
- list_team_members
- list_integrations
- get_integration
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.