@terranode-co/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERRANODE_API_KEY | Yes | Terranode API key for authentication |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_datasetsA | List all geospatial datasets available for querying. Returns pre-loaded public datasets (US states, counties, ZIP codes, etc.) and your custom uploaded datasets. Each dataset has an id (UUID) — always use the id when calling other tools. |
| check_locationA | Check which feature in a polygon dataset contains a given coordinate (point-in-polygon query). Returns the properties of all matching features, or indicates no match. Requires latitude, longitude, and a dataset id (UUID) from list_datasets. Call list_datasets first to get the id. This is NOT a geocoder — it requires numeric coordinates, not addresses or place names. |
| find_nearestA | Find the nearest counties, districts, ZIP codes, or other features to a coordinate. Use this for proximity queries, finding what's nearby, or ranking features by distance. Returns features sorted by distance (meters and miles), measured to feature boundary. Also works as a reverse lookup — returns the containing feature (distance=0) plus neighbors. Requires latitude, longitude, and a dataset id (UUID) from list_datasets. |
| calculate_distanceA | Calculate the exact geodesic distance between two points on Earth's surface. Uses the WGS84 ellipsoid model for high accuracy. No dataset needed. Returns distance in both meters and miles. |
| spatial_joinA | Enrich a set of coordinates with attributes from a polygon dataset. For each point, returns the properties of the polygon it falls within. Like running check_location on multiple points at once, but more efficient. Requires an array of coordinate objects and a dataset id (UUID) from list_datasets. Call list_datasets first to get the id. Points need numeric coordinates, not addresses. |
| enrich_locationA | Get location attributes (county, flood zone, school district, etc.) for a coordinate. Queries all available datasets in one call and returns what matched. No dataset id needed — this is the simplest way to find out what's at a location. Optional radius expands the search area (meters). This is NOT a geocoder — it requires numeric coordinates, not addresses or place names. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/terranode-co/mcp-server-terranode'
If you have feedback or need assistance with the MCP directory API, please join our Discord server