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