set_route — LastPing MCP Tool Mutating
set_route
(set route) is one of 39 tools on the
LastPing
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_route from your client
- Claude Code LastPing set_route run in your project directory
- Claude Desktop LastPing set_route ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LastPing set_route ~/.cursor/mcp.json
- VS Code LastPing set_route .vscode/mcp.json
- Zed LastPing set_route ~/.config/zed/settings.json
- Windsurf LastPing set_route ~/.codeium/windsurf/mcp_config.json
- Cline LastPing set_route ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LastPing set_route ~/.gemini/settings.json
- Grok LastPing set_route .mcp.json (in your project root)
- ChatGPT LastPing set_route Settings → Connectors → Advanced → Developer mode
- Claude.ai LastPing set_route Settings → Connectors → Add custom connector
- LangChain LastPing set_route pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lastping https://mcp.lastping.devOther tools on this server
- add_incident_note
- create_api_key
- create_destination
- create_monitor
- create_status_page
- declare_run_expectations
- delete_agent
- delete_destination
- delete_monitor
- delete_status_page
- discover_monitors_reconcile
- export_terraform
- get_agent
- get_alert_templates
- get_incident
- get_monitor
- get_ping_instructions
- get_run
- get_run_history
- list_agents
- list_api_keys
- list_deliveries
- list_destinations
- list_incidents
- list_monitors
- list_open_incidents
- list_status_pages
- pause_monitor
- register_agent
- resume_monitor
- revoke_api_key
- set_alert_template
- snooze_monitor
- test_destination
- update_agent
- update_destination
- update_monitor
- update_status_page
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.