compare_entities — Data Austin MCP Tool
compare_entities
(compare entities) is one of 39 tools on the
Data Austin
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 Data Austin compare_entities run in your project directory
- Claude Desktop Data Austin compare_entities ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Data Austin compare_entities ~/.cursor/mcp.json
- VS Code Data Austin compare_entities .vscode/mcp.json
- Zed Data Austin compare_entities ~/.config/zed/settings.json
- Windsurf Data Austin compare_entities ~/.codeium/windsurf/mcp_config.json
- Cline Data Austin compare_entities ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Data Austin compare_entities ~/.gemini/settings.json
- Grok Data Austin compare_entities .mcp.json (in your project root)
- ChatGPT Data Austin compare_entities Settings → Connectors → Advanced → Developer mode
- Claude.ai Data Austin compare_entities Settings → Connectors → Add custom connector
- LangChain Data Austin compare_entities pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data-austin https://gateway.pipeworx.io/data-austin/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
- austin_recent
- austin_query
- austin_datasets
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.