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