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