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