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