purchase_ticket_order — events MCP Tool
purchase_ticket_order
(purchase ticket order) is one of 30 tools on the
events
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call purchase_ticket_order from your client
- Claude Code events purchase_ticket_order run in your project directory
- Claude Desktop events purchase_ticket_order ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor events purchase_ticket_order ~/.cursor/mcp.json
- VS Code events purchase_ticket_order .vscode/mcp.json
- Zed events purchase_ticket_order ~/.config/zed/settings.json
- Windsurf events purchase_ticket_order ~/.codeium/windsurf/mcp_config.json
- Cline events purchase_ticket_order ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI events purchase_ticket_order ~/.gemini/settings.json
- Grok events purchase_ticket_order .mcp.json (in your project root)
- ChatGPT events purchase_ticket_order Settings → Connectors → Advanced → Developer mode
- Claude.ai events purchase_ticket_order Settings → Connectors → Add custom connector
- LangChain events purchase_ticket_order pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http events https://eventchat-events-mcp-production.up.railway.app/mcp
Other tools on this server
- get_preference_onboarding
- create_event_preference_profile
- save_event_preferences
- get_event_preferences
- delete_event_preferences
- record_event_feedback
- get_event_feedback_prompt
- get_event_search_followups
- list_cities
- find_scene_entities
- get_artist
- get_venue
- search_events
- recommend_events
- recommend_events_for_user
- plan_night
- get_daily_roundup
- get_artist_events
- get_artist_page
- get_city_pulse
- get_event
- get_ticket_purchase_policy
- get_ticket_offers
- quote_ticket_order
- get_taste_profile
- bin_event
- save_event
- add_to_dizko_plan
- create_event_calendar_file
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.