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