list_my_events — livedot MCP MCP Tool Read-only

list_my_events (list my events) 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 list_my_events from your client

Claude Code livedot MCP list_my_events run in your project directory
Claude Desktop livedot MCP list_my_events ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor livedot MCP list_my_events ~/.cursor/mcp.json
VS Code livedot MCP list_my_events .vscode/mcp.json
Zed livedot MCP list_my_events ~/.config/zed/settings.json
Windsurf livedot MCP list_my_events ~/.codeium/windsurf/mcp_config.json
Cline livedot MCP list_my_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI livedot MCP list_my_events ~/.gemini/settings.json
Grok livedot MCP list_my_events .mcp.json (in your project root)
ChatGPT livedot MCP list_my_events Settings → Connectors → Advanced → Developer mode
Claude.ai livedot MCP list_my_events Settings → Connectors → Add custom connector
LangChain livedot MCP list_my_events pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http mcp https://livedot.me/mcp

Other tools on this server

find_person
where_is
event_status
club_in_race
event_weather
fly_route
tour_route
tour_notes
tap_on_the_back
find_clubs
find_events
find_coaches
plan_route
create_event
update_event
add_tour_notes
publish_event
post_club_ride
invite_members

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.

livedot MCP MCP server