unsubscribe — Dpla MCP Tool
unsubscribe
(unsubscribe) is one of 39 tools on the
Dpla
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call unsubscribe from your client
- Claude Code Dpla unsubscribe run in your project directory
- Claude Desktop Dpla unsubscribe ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dpla unsubscribe ~/.cursor/mcp.json
- VS Code Dpla unsubscribe .vscode/mcp.json
- Zed Dpla unsubscribe ~/.config/zed/settings.json
- Windsurf Dpla unsubscribe ~/.codeium/windsurf/mcp_config.json
- Cline Dpla unsubscribe ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dpla unsubscribe ~/.gemini/settings.json
- Grok Dpla unsubscribe .mcp.json (in your project root)
- ChatGPT Dpla unsubscribe Settings → Connectors → Advanced → Developer mode
- Claude.ai Dpla unsubscribe Settings → Connectors → Add custom connector
- LangChain Dpla unsubscribe pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dpla https://gateway.pipeworx.io/dpla/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
- dpla_search_items
- dpla_item
- dpla_collections
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.