destination_events — Yenta Directory MCP Tool
destination_events
(destination events) is one of 21 tools on the
Yenta Directory
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call destination_events from your client
- Claude Code Yenta Directory destination_events run in your project directory
- Claude Desktop Yenta Directory destination_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Yenta Directory destination_events ~/.cursor/mcp.json
- VS Code Yenta Directory destination_events .vscode/mcp.json
- Zed Yenta Directory destination_events ~/.config/zed/settings.json
- Windsurf Yenta Directory destination_events ~/.codeium/windsurf/mcp_config.json
- Cline Yenta Directory destination_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Yenta Directory destination_events ~/.gemini/settings.json
- Grok Yenta Directory destination_events .mcp.json (in your project root)
- ChatGPT Yenta Directory destination_events Settings → Connectors → Advanced → Developer mode
- Claude.ai Yenta Directory destination_events Settings → Connectors → Add custom connector
- LangChain Yenta Directory destination_events pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http directory https://yentaknows.ai/mcpOther tools on this server
- search_venues
- list_cities
- get_venue
- get_venues
- search_destinations
- search
- get_destination
- search_menus
- facet_vocabulary
- venue_profile
- venue_menu_search
- venue_dietary_options
- venue_faq
- venue_links
- destination_overview
- destination_facets
- destination_listings
- destination_listing
- destination_guide
- destination_faq
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.