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