get_restaurant_menus — Filipe Coffee MCP Tool Read-only
get_restaurant_menus
(get restaurant menus) is one of 26 tools on the
Filipe Coffee
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_restaurant_menus from your client
- Claude Code Filipe Coffee get_restaurant_menus run in your project directory
- Claude Desktop Filipe Coffee get_restaurant_menus ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Filipe Coffee get_restaurant_menus ~/.cursor/mcp.json
- VS Code Filipe Coffee get_restaurant_menus .vscode/mcp.json
- Zed Filipe Coffee get_restaurant_menus ~/.config/zed/settings.json
- Windsurf Filipe Coffee get_restaurant_menus ~/.codeium/windsurf/mcp_config.json
- Cline Filipe Coffee get_restaurant_menus ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Filipe Coffee get_restaurant_menus ~/.gemini/settings.json
- Grok Filipe Coffee get_restaurant_menus .mcp.json (in your project root)
- ChatGPT Filipe Coffee get_restaurant_menus Settings → Connectors → Advanced → Developer mode
- Claude.ai Filipe Coffee get_restaurant_menus Settings → Connectors → Add custom connector
- LangChain Filipe Coffee get_restaurant_menus pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http filipe-coffee https://www.filipe.coffee/mcp
Other tools on this server
- get_site_info
- list_categories
- search_places
- get_place
- list_events
- list_guides
- list_booking_services
- get_availability
- create_booking
- reserve_event_tickets
- request_reservation
- rsvp_event
- get_event_tickets
- list_products
- create_checkout
- search_dishes
- list_pricing_plans
- get_reviews
- list_blog_posts
- list_faqs
- list_forms
- submit_form
- get_loyalty_info
- list_offers
- list_profiles
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.