list_local_event_alerts — Local Events Tracker MCP Tool Read-only
list_local_event_alerts
(list local event alerts) 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 list_local_event_alerts from your client
- Claude Code Local Events Tracker list_local_event_alerts run in your project directory
- Claude Desktop Local Events Tracker list_local_event_alerts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Local Events Tracker list_local_event_alerts ~/.cursor/mcp.json
- VS Code Local Events Tracker list_local_event_alerts .vscode/mcp.json
- Zed Local Events Tracker list_local_event_alerts ~/.config/zed/settings.json
- Windsurf Local Events Tracker list_local_event_alerts ~/.codeium/windsurf/mcp_config.json
- Cline Local Events Tracker list_local_event_alerts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Local Events Tracker list_local_event_alerts ~/.gemini/settings.json
- Grok Local Events Tracker list_local_event_alerts .mcp.json (in your project root)
- ChatGPT Local Events Tracker list_local_event_alerts Settings → Connectors → Advanced → Developer mode
- Claude.ai Local Events Tracker list_local_event_alerts Settings → Connectors → Add custom connector
- LangChain Local Events Tracker list_local_event_alerts 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.