reserve_event_tickets — Filipe Coffee MCP Tool
reserve_event_tickets
(reserve event tickets) 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 reserve_event_tickets from your client
- Claude Code Filipe Coffee reserve_event_tickets run in your project directory
- Claude Desktop Filipe Coffee reserve_event_tickets ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Filipe Coffee reserve_event_tickets ~/.cursor/mcp.json
- VS Code Filipe Coffee reserve_event_tickets .vscode/mcp.json
- Zed Filipe Coffee reserve_event_tickets ~/.config/zed/settings.json
- Windsurf Filipe Coffee reserve_event_tickets ~/.codeium/windsurf/mcp_config.json
- Cline Filipe Coffee reserve_event_tickets ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Filipe Coffee reserve_event_tickets ~/.gemini/settings.json
- Grok Filipe Coffee reserve_event_tickets .mcp.json (in your project root)
- ChatGPT Filipe Coffee reserve_event_tickets Settings → Connectors → Advanced → Developer mode
- Claude.ai Filipe Coffee reserve_event_tickets Settings → Connectors → Add custom connector
- LangChain Filipe Coffee reserve_event_tickets pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http filipe-coffee https://www.filipe.coffee/mcpOther tools on this server
- get_site_info
- list_categories
- search_places
- get_place
- list_events
- list_guides
- list_booking_services
- get_availability
- create_booking
- request_reservation
- rsvp_event
- get_event_tickets
- list_products
- create_checkout
- get_restaurant_menus
- 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.