manage_alert_delivery — Local Events Tracker MCP Tool
manage_alert_delivery
(manage alert delivery) is one of 11 tools on the
Local Events Tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call manage_alert_delivery from your client
- Claude Code Local Events Tracker manage_alert_delivery run in your project directory
- Claude Desktop Local Events Tracker manage_alert_delivery ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Local Events Tracker manage_alert_delivery ~/.cursor/mcp.json
- VS Code Local Events Tracker manage_alert_delivery .vscode/mcp.json
- Zed Local Events Tracker manage_alert_delivery ~/.config/zed/settings.json
- Windsurf Local Events Tracker manage_alert_delivery ~/.codeium/windsurf/mcp_config.json
- Cline Local Events Tracker manage_alert_delivery ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Local Events Tracker manage_alert_delivery ~/.gemini/settings.json
- Grok Local Events Tracker manage_alert_delivery .mcp.json (in your project root)
- ChatGPT Local Events Tracker manage_alert_delivery Settings → Connectors → Advanced → Developer mode
- Claude.ai Local Events Tracker manage_alert_delivery Settings → Connectors → Add custom connector
- LangChain Local Events Tracker manage_alert_delivery pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http local-events https://localeventstracker.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 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.