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