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