trigger_test_alert — Monitor Hub MCP Tool
trigger_test_alert
(trigger test alert) is one of 25 tools on the
Monitor Hub
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call trigger_test_alert from your client
- Claude Code Monitor Hub trigger_test_alert run in your project directory
- Claude Desktop Monitor Hub trigger_test_alert ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Monitor Hub trigger_test_alert ~/.cursor/mcp.json
- VS Code Monitor Hub trigger_test_alert .vscode/mcp.json
- Zed Monitor Hub trigger_test_alert ~/.config/zed/settings.json
- Windsurf Monitor Hub trigger_test_alert ~/.codeium/windsurf/mcp_config.json
- Cline Monitor Hub trigger_test_alert ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Monitor Hub trigger_test_alert ~/.gemini/settings.json
- Grok Monitor Hub trigger_test_alert .mcp.json (in your project root)
- ChatGPT Monitor Hub trigger_test_alert Settings → Connectors → Advanced → Developer mode
- Claude.ai Monitor Hub trigger_test_alert Settings → Connectors → Add custom connector
- LangChain Monitor Hub trigger_test_alert pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http monitorhub https://mcp.monitorhubs.com/mcpOther tools on this server
- list_monitors
- get_monitor_details
- read_monitor_status
- read_server_status
- get_server_metrics
- read_incidents
- read_uptime_statistics
- read_alerts
- list_status_pages
- search_monitors
- list_recent_outages
- list_notification_channels
- create_monitor
- update_monitor
- pause_monitor
- resume_monitor
- delete_monitor
- test_endpoint
- resolve_server_warning
- get_incident_details
- acknowledge_incident
- resolve_incident
- update_status_page
- get_monitor_history
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.