TerraLab
Server Details
Geodata for any place, inside your agent: map data, terrain, routes, satellite images, GIS files.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 72.5% over 21 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 13 tools
Each tool has a distinct GIS purpose, and descriptions explicitly separate adjacent workflows such as routing, straight-line measurement, and isochrones. Minor overlap remains around buffering (measure radius/buffer vs. process_geometry buffer) and general vs. France-specific building/parcel data, but the boundaries are mostly clear.
Almost all names use snake_case and are descriptive, with a predictable verb_noun style such as convert_coordinates, extract_open_data, get_elevation, and process_geometry. The main deviations are bare measure and the domain-prefixed french_building_heights/french_parcel, but the set remains readable and consistent overall.
Thirteen tools is well within a reasonable range for a broad GIS platform and each tool covers a recognizable, non-trivial capability. The set is scoped without obvious padding or missing basic utility slots.
The surface covers a wide GIS workflow: geocoding, data extraction, coordinate conversion, elevation, imagery, routing, isochrones, cadastral/building data, file conversion, and geometry processing. Minor gaps remain for layer-level reprojection, attribute filtering/query, and spatial joins, but most common tasks have a usable tool path.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Added
get_forest_type
7 tool updates
- Changed
extract_open_data4 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "area": { - "bbox": [ - 2.34, - 48.857, - 2.343, - 48.859 - ] - }, - "formats": [ - "shapefile" - ], - "theme": "buildings" - }, - { - "area": { - "place": "Annecy", - "radius_m": 500 - }, - "kind": "pharmacy", - "theme": "pois" - } -]New value: +[ + { + "area": { + "bbox": [ + 2.34, + 48.857, + 2.343, + 48.859 + ] + }, + "formats": [ + "shapefile" + ], + "theme": "buildings" + }, + { + "area": { + "place": "Annecy", + "radius_m": 500 + }, + "kind": "pharmacy", + "theme": "pois" + }, + { + "area": { + "place": "Bretagne, France" + }, + "formats": [ + "shapefile" + ], + "level": "county", + "theme": "divisions" + } +] - changed
Input schema / properties / formats / descriptionPrevious value: -"Download formats."New value: +"Download formats. A GeoPackage is always included." - changed
Input schema / properties / formats / items / enumPrevious value: -[ - "geojson", - "kml", - "shapefile", - "csv" -]New value: +[ + "geojson", + "kml", + "shapefile", + "csv", + "geopackage" +] - added
Input schema / properties / levelAdded value: +{ + "description": "For the divisions theme: the administrative level to keep. region = French région, US state, German Land; county = French département, US county; municipality = commune, town or city. With a named place, a division of that name at this level is returned alone, and lower levels are kept only inside the named place (\"the departments of Brittany\": place Brittany, level county).", + "enum": [ + "country", + "region", + "county", + "municipality" + ], + "type": "string" +}
- Added
french_building_heights - Added
get_route - Added
get_satellite_image - Added
get_travel_area - Added
measure - Added
process_geometry
1 tool update
- Changed
get_elevation1 field changed- changed
Input schema / properties / mode / descriptionPrevious value: -"point: elevation of each point; path: profile along the points; area: contour lines and slope statistics."New value: +"point: elevation of each point; path: profile along the points; area: DEM, hillshade and slope GeoTIFFs, plus contour lines and slope statistics for small areas."
6 tool updates
- First observed
convert_coordinates - First observed
extract_open_data - First observed
find_places - First observed
french_parcel - First observed
get_elevation - First observed
open_gis_file
Related MCP Connectors
Maps for agents: truck/ADR routing, geocoding, places, matrices, isochrones, EV and fleet planning.
Mobility, geocoding and nearby urban services for AI agents.
Routing, geocoding, places, matrix and map tools for location-aware AI workflows.
Real-world data for agents: air quality, geocoding, quakes, holidays, web search
Related MCP Servers
AlicenseBqualityCmaintenanceEnables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.85 npm7Apache 2.0- AlicenseAqualityAmaintenanceEnables AI agents to query any Earth location as a token-budgeted topological map with indoor floors, weather, traffic, transit schedules, and live delays.92,413 npmApache 2.0
- AlicenseAqualityDmaintenanceGeospatial API tools for AI agents — geocoding, reverse geocoding, routing, isochrone, distance matrix, static maps, H3 hexagons, elevation, GPS map-matching, point-in-polygon, address normalisation, timezone lookup, and batch geocoding. Built on OpenStreetMap infrastructure. Cost-effective alternative to Google Maps API.1814 npmMIT

Mapbox MCP Serverofficial
AlicenseAqualityAmaintenanceProvides geospatial intelligence to AI agents through Mapbox APIs, enabling geocoding, routing, POI search, map images, and offline spatial calculations.285,064 npm363MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.