In-depth architectural comparison of the Overspan MCP and Arcgis Sanclemente MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Overspan MCP
Location Services · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Arcgis Sanclemente
Location Services · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Overspan MCP if you need specialized Location Services tools running via a local process. Choose Arcgis Sanclemente if your workspace requires Location Services integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Overspan MCP when:
You need dedicated capabilities in the Location Services domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: OVERSPAN_API_KEY, OVERSPAN_API_URL, OVERSPAN_MAX_RESPONSE_CHARS.
Overspan MCP is categorized under Location Services and uses a local stdio subprocess. In contrast, Arcgis Sanclemente belongs to Location Services using local stdio subprocess. Select Overspan MCP when you need capabilities focused on location services and Arcgis Sanclemente when you require tools for location services.
Search City of San Clemente GIS open geospatial datasets (parcels, zoning, public works & city services) by keyword. Returns each dataset's name, summary, record_count, owner/org, and its Feature Service `url` — pass that url to query_layer / layer_info.
query_layer
Query an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like `where`, comma-separated `out_fields`, `order_by`, `limit`, `offset`. Returns attribute rows (and geometry). Use where="1=1" + out_fields="*" to sample.
layer_info
Get an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.