Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
TerraLab is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Map data ready for QGIS: open data extracts, GIS files, coordinates, elevation, French parcels.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http terralab-mcp https://mcp.terra-lab.ai/mcp
# 2 — ask your agent for something these tools do
# find_places, convert_coordinates, get_elevation and 3 more
TerraLab costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TLAll 1 server
terra-lab1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http terralab-mcp https://mcp.terra-lab.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use this when the user asks to put, pin or plot places or addresses on an interactive map with their coordinates, wants the coordinates of an address or place name, the address at given coordinates, or a whole list of addresses (up to 100, pasted or as CSV with an address column) placed on a map. Worldwide, OpenStreetMap data; French street addresses are refined with the national address base. Sho
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | One address or place name. The place the user asks about, not the user's own location. |
| latitude | number | no | Latitude for a reverse lookup. The place the user asks about, not the user's own location. |
| longitude | number | no | Longitude for a reverse lookup. The place the user asks about, not the user's own location. |
| limit | integer | no | For a single query: maximum number of matches. |
| addresses | array | no | A list of addresses to place, up to 100. The place the user asks about, not the user's own location. |
| text | string | no | A list as text: one address per line, or CSV with an address column. The place the user asks about, not the user's own location. |
| title | string | no | For a list: map title, also used for file names. |
Use this when the user gives coordinates in any common format (decimal degrees, degrees minutes seconds, UTM, MGRS, Lambert 93, "lat, lon" or "lon, lat") and wants them in another format or projection. The format of each line is detected automatically; for a national grid the numbers alone cannot reveal (Dutch RD, Swiss LV95, British National Grid, Polish 1992, Belgian Lambert 72) or a UTM zone gi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | One coordinate per line, up to 1,000 lines. A label may follow the numbers. |
| target_epsg | string | no | Optional extra output system as an EPSG code. |
| source_epsg | string | no | Optional system the input is in, as an EPSG code, when it cannot be detected: Dutch RD EPSG:28992, Swiss LV95 EPSG:2056, British National Grid EPSG:27700, Poland 1992 EPSG:2180, UTM zone 32N EPSG:3263 |
Use this when the user wants the altitude of places, an elevation profile (cross-section) between two or more points (min, max, total ascent and descent), or the terrain of an area: contour lines (topographic lines) and slope statistics (how steep or flat it is). mode "point": up to 100 points. mode "path": 2 or more points, sampled into at most 500 samples, with a profile chart. mode "area": a bb
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | no | point: elevation of each point; path: profile along the points; area: contour lines and slope statistics. |
| points | array | no | For point and path: points or place names. The place the user asks about, not the user's own location. |
| samples | integer | no | For path: number of samples along the path. |
| area | object | no | For area: The area: a bbox, or a place (name, address or coordinates) with an optional radius in metres. The place the user asks about, not the user's own location. |
| interval_m | number | no | For area: vertical interval between contour lines, in metres. |
Use this when the user wants open geographic data for an area anywhere in the world: buildings, places, roads, addresses, administrative divisions, land use, points of interest, waterways, water areas, power lines, boundaries, railways, routes, transit stops or protected areas. The area is a bbox, a place, or a place with a radius. Returns the count, sample attributes, a map and a file (GeoJSON, K
| Parameter | Type | Required | Notes |
|---|---|---|---|
| theme | string | yes | The data layer. |
| area | object | yes | The area: a bbox, or a place (name, address or coordinates) with an optional radius in metres. The place the user asks about, not the user's own location. |
| formats | array | no | Download formats. |
| kind | no | Keep only some kinds of feature, matched against their OpenStreetMap tag value in English: pharmacy, school, supermarket, restaurant, hospital, farmland, forest, vineyard. One kind, or several in one |
Use this when the user shares or links a geographic file (GeoJSON, KML, KMZ, GPX, zipped Shapefile, CSV with coordinates, WKT), pastes its content, or has a list of points or GeoJSON to put on a map, and wants to see it, understand it (format, coordinate system, extent, feature count, geometry types, fields, problems) or convert it to GeoJSON, KML, KMZ, GPX, Shapefile zip or CSV. Shapefile, GeoJSO
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | object | no | A file uploaded in the conversation. |
| url | string | no | A public http(s) link to the file. |
| text | string | no | The file content pasted as text (GeoJSON, KML, GPX, CSV or WKT). |
| points | array | no | Points to show and convert, with a name. The places the user asks about, not the user's own location. |
| geojson | object | no | A GeoJSON FeatureCollection, Feature or geometry in WGS 84, given as an object. |
| title | string | no | Name for the map and the output files when there is no file name. |
| file_name | string | no | Optional name of the file, used to name the outputs. |
| convert_to | array | no | Output formats wanted. |
Use this when the user asks about the cadastral parcel (parcelle cadastrale) at an address or point in France: parcel id, commune, section, number, cadastral area, and the local urban plan zone (PLU or PLUi zone: label, type, document). Shows the parcel on a map with GeoJSON and KML downloads. France only. Never returns owners or property sales. Never use the user's current location unless they ty
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | An address in France. The place the user asks about, not the user's own location. |
| latitude | number | no | Latitude in France. The place the user asks about, not the user's own location. |
| longitude | number | no | Longitude in France. The place the user asks about, not the user's own location. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install TerraLab or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish TerraLab can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.