search_venues — Yenta Directory MCP Tool Read-only
search_venues
(search venues) 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 search_venues from your client
- Claude Code Yenta Directory search_venues run in your project directory
- Claude Desktop Yenta Directory search_venues ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Yenta Directory search_venues ~/.cursor/mcp.json
- VS Code Yenta Directory search_venues .vscode/mcp.json
- Zed Yenta Directory search_venues ~/.config/zed/settings.json
- Windsurf Yenta Directory search_venues ~/.codeium/windsurf/mcp_config.json
- Cline Yenta Directory search_venues ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Yenta Directory search_venues ~/.gemini/settings.json
- Grok Yenta Directory search_venues .mcp.json (in your project root)
- ChatGPT Yenta Directory search_venues Settings → Connectors → Advanced → Developer mode
- Claude.ai Yenta Directory search_venues Settings → Connectors → Add custom connector
- LangChain Yenta Directory search_venues pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http directory https://yentaknows.ai/mcpOther tools on this server
- 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_events
- 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.