update_status_page_components — UpHeron MCP Tool Mutating
update_status_page_components
(update status page components) is one of 59 tools on the
UpHeron
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call update_status_page_components from your client
- Claude Code UpHeron update_status_page_components run in your project directory
- Claude Desktop UpHeron update_status_page_components ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor UpHeron update_status_page_components ~/.cursor/mcp.json
- VS Code UpHeron update_status_page_components .vscode/mcp.json
- Zed UpHeron update_status_page_components ~/.config/zed/settings.json
- Windsurf UpHeron update_status_page_components ~/.codeium/windsurf/mcp_config.json
- Cline UpHeron update_status_page_components ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI UpHeron update_status_page_components ~/.gemini/settings.json
- Grok UpHeron update_status_page_components .mcp.json (in your project root)
- ChatGPT UpHeron update_status_page_components Settings → Connectors → Advanced → Developer mode
- Claude.ai UpHeron update_status_page_components Settings → Connectors → Add custom connector
- LangChain UpHeron update_status_page_components pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http upheron https://upheron.com/mcpOther tools on this server
- check_website
- get_account
- list_locations
- list_monitors
- get_monitor
- get_monitor_results
- get_uptime_history
- get_sla_report
- get_error_budgets
- list_incidents
- acknowledge_incident
- list_escalation_policies
- list_on_call_schedules
- get_incident
- post_incident_update
- comment_on_incident
- open_incident
- update_incident
- resolve_incident
- write_postmortem
- list_status_pages
- create_on_call_schedule
- update_on_call_schedule
- delete_on_call_schedule
- add_on_call_override
- remove_on_call_override
- create_escalation_policy
- update_escalation_policy
- delete_escalation_policy
- list_maintenance_windows
- create_maintenance_window
- update_maintenance_window
- change_maintenance_occurrence
- delete_maintenance_window
- get_audit_log
- create_monitor
- preview_monitor_import
- import_monitors
- update_monitor
- pause_monitor
- resume_monitor
- delete_monitor
- add_notification_contact
- confirm_notification_contact
- list_notification_contacts
- test_notification_contact
- get_vulnerabilities
- import_software
- add_software
- remove_software
- mark_vulnerability_fixed
- get_ports
- verify_host
- get_website_changes
- accept_page_change
- scan_ports
- get_domain_watch
- scan_website_software
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.