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