get_venue — Yenta Directory MCP Tool Read-only
get_venue
(get venue) 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 get_venue from your client
- Claude Code Yenta Directory get_venue run in your project directory
- Claude Desktop Yenta Directory get_venue ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Yenta Directory get_venue ~/.cursor/mcp.json
- VS Code Yenta Directory get_venue .vscode/mcp.json
- Zed Yenta Directory get_venue ~/.config/zed/settings.json
- Windsurf Yenta Directory get_venue ~/.codeium/windsurf/mcp_config.json
- Cline Yenta Directory get_venue ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Yenta Directory get_venue ~/.gemini/settings.json
- Grok Yenta Directory get_venue .mcp.json (in your project root)
- ChatGPT Yenta Directory get_venue Settings → Connectors → Advanced → Developer mode
- Claude.ai Yenta Directory get_venue Settings → Connectors → Add custom connector
- LangChain Yenta Directory get_venue 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_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.