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