unsubscribe — Ena MCP Tool
unsubscribe
(unsubscribe) is one of 39 tools on the
Ena
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call unsubscribe from your client
- Claude Code Ena unsubscribe run in your project directory
- Claude Desktop Ena unsubscribe ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ena unsubscribe ~/.cursor/mcp.json
- VS Code Ena unsubscribe .vscode/mcp.json
- Zed Ena unsubscribe ~/.config/zed/settings.json
- Windsurf Ena unsubscribe ~/.codeium/windsurf/mcp_config.json
- Cline Ena unsubscribe ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ena unsubscribe ~/.gemini/settings.json
- Grok Ena unsubscribe .mcp.json (in your project root)
- ChatGPT Ena unsubscribe Settings → Connectors → Advanced → Developer mode
- Claude.ai Ena unsubscribe Settings → Connectors → Add custom connector
- LangChain Ena unsubscribe pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ena https://gateway.pipeworx.io/ena/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
- 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
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- ena_search
- ena_filereport
- ena_results_types
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.