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