unsubscribe — Eventbrite MCP Tool
unsubscribe
(unsubscribe) is one of 43 tools on the
Eventbrite
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call unsubscribe from your client
- Claude Code Eventbrite unsubscribe run in your project directory
- Claude Desktop Eventbrite unsubscribe ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Eventbrite unsubscribe ~/.cursor/mcp.json
- VS Code Eventbrite unsubscribe .vscode/mcp.json
- Zed Eventbrite unsubscribe ~/.config/zed/settings.json
- Windsurf Eventbrite unsubscribe ~/.codeium/windsurf/mcp_config.json
- Cline Eventbrite unsubscribe ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Eventbrite unsubscribe ~/.gemini/settings.json
- Grok Eventbrite unsubscribe .mcp.json (in your project root)
- ChatGPT Eventbrite unsubscribe Settings → Connectors → Advanced → Developer mode
- Claude.ai Eventbrite unsubscribe Settings → Connectors → Add custom connector
- LangChain Eventbrite unsubscribe pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http eventbrite https://gateway.pipeworx.io/eventbrite/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- company_register_search
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- archive_evidence
- archive_compare
- research_row
- classify_row
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- eventbrite_city_events
- eventbrite_event
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 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.