Side-by-Side Model Context Protocol Comparison
Gis MCP vs Gis MCP Server
In-depth architectural comparison of the Gis MCP and Gis MCP Server 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
Gis MCP
Location Services · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Gis MCP Server
Location Services · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Gis MCP if you need specialized Location Services tools running via a local process. Choose Gis MCP Server 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 Gis 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).
- Primary tools included: read_file_gpd, append_gpd, merge_gpd.
Choose Gis MCP Server 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:
NOMINATIM_URL, NOMINATIM_USER_AGENT, OSRM_URL, OSRM_PROFILE, PELIAS_URL, PELIAS_API_KEY, OPEN_ELEVATION_URL, GIS_DEFAULT_CRS. - Primary tools included: geocode, reverse_geocode, distance.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Gis MCP Tools (87)
read_file_gpd
Reads a geospatial file and returns stats and a data preview.
append_gpd
Reads two shapefiles directly, concatenates them vertically.
merge_gpd
Merges two shapefiles based on common attribute columns,
This function performs a database-style join, not a spatial join.
Args:
left_shapefile_path: Path to the left shapefile. The geometry from this file is preserved.
right_shapefile_path: Path to the right shapefile to merge.
output_path: Path to save the merged output shapefile.
how: Type of merge. One of 'left', 'right', 'outer', 'inner'. Defaults to 'inner'.
on: Column name to join on. Must be found in both shapefiles.
left_on: Column name to join on in the left shapefile.
right_on: Column name to join on in the right shapefile.
suffixes: Suffix to apply to overlapping column names.
overlay_gpd
Overlay two GeoDataFrames using geopandas.overlay.
Args:
gdf1_path: Path to the first geospatial file.
gdf2_path: Path to the second geospatial file.
how: Overlay method ('intersection', 'union', 'identity', 'symmetric_difference', 'difference').
output_path: Optional path to save the result.
Returns:
Dictionary with status, message, and output info.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Gis MCP Configuration
Gis MCP Server Configuration