Mapsmith vs MCP Server
A side-by-side look at the Mapsmith and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mapsmith for location services work as a local process; choose MCP Server for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mapsmith when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
describe_dataset, buffer_layer, clip_layer.
Choose MCP Server when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
STHAN_API_KEY. - You want tools like
sthan_verify_address, sthan_parse_address, sthan_autocomplete_address.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 53/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | STHAN_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 28 | 8 |
| Full listing | View Mapsmith | View MCP Server |
Tools & capabilities
Mapsmith tools 28
describe_datasetCRS, schema/bands, extent, nodata and statistics of any vector or raster datasetbuffer_layerMetric buffer with automatic UTM estimation for geographic CRSclip_layerClip a layer with a mask layeroverlay_layersSet-theoretic overlay (intersection/union/difference/…); dropped lower-dimension pieces are declared in the manifestdissolve_layerMerge features per key; the aggregation is recorded in the manifest and the group count verifiednearest_joinNearest neighbour with the distance in meters, UTM-measured on geographic CRS (decision recorded)explode_layerMulti-part to single-part, with the part count verified in closed formmeasure_areaArea in m², always: ground on the ellipsoid, or planar converted with the CRS's own declared linear unit (survey feet are not metres). Invalid rings repaired *before* measuring, and a plane that is not equal-area here comes back with the ratio against the ground areamerge_layersAppend layers (schema union); null-filled columns are named in the manifest, the count verified against the sumsimplify_layerDouglas-Peucker with the drift measured: area/length before and after recorded in the manifestcentroid_layerGeometric centroids computed in a metric CRS, never on degrees (decision recorded)convert_formatConvert between GeoParquet/GeoPackage/GeoJSON by output extension, re-read and verified (count and CRS). Two conversions are refused with the reason rather than performed: shapefile output, which truncates field names to 10 characters silently, and GeoJSON for a non-WGS84 layer- +16 more on the listing page
MCP Server tools 8
sthan_verify_addressVerify a US address is real and deliverable. Returns standardized format, ZIP+4, DPV, residential/commercial.sthan_parse_addressParse freeform US address text into structured components (street number, name, type, direction, unit, city, state, zip).sthan_autocomplete_addressSuggest complete US addresses from partial input. Sub-100ms.sthan_autocomplete_citySuggest US cities from partial input, with state code.sthan_autocomplete_zipcodeSuggest US ZIP codes from partial input.sthan_geocodeUS address → latitude/longitude with accuracy + confidence, county, ZIP+4 and time zone.sthan_reverse_geocodeLatitude/longitude → nearest US street address with distance in meters, county, ZIP+4 and time zone; `limit` (up to 10) also lists nearby addresses.sthan_ip_geolocationIPv4 or IPv6 → location (country to postal code, local time, flag, currency), the network behind it (ASN, ISP, proxy/hosting flags) and a confidence score.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mapsmith
{
"mcpServers": {
"mapsmith": {
"command": "uvx",
"args": [
"mapsmith"
]
}
}
}
MCP Server
{
"mcpServers": {
"sthan-io-mcp-server": {
"command": "npx",
"args": [
"-y",
"@sthan/mcp-server"
],
"env": {
"STHAN_API_KEY": "YOUR_STHAN_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Mapsmith is categorized under Location Services and uses a local stdio subprocess. MCP Server belongs to Location Services and uses a local stdio subprocess. Pick Mapsmith for location services work and MCP Server for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mapsmith has no declared pricing — check the project's own site. MCP Server is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mapsmith and sthan-io-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mapsmith has a quality signal of 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars. MCP Server has 61/100 (Good) with 5 views, 0 installs and 0 GitHub stars.