Terranode Geospatial API

io.github.terranode-coPublished by GitHub account terranode-cov0.1.10Updated Oct 24, 2026

Point-in-polygon, nearest feature, spatial join, and distance tools for US geospatial datasets

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Local MCP server that gives an assistant tools to run US geospatial queries — point-in-polygon, nearest feature, distance and spatial joins — through the Terran

What you can do
List available geospatial datasets, both system and custom ones, so the assistant knows what it can query against. Look up which feature contains a coordinate (point-in-polygon), such as the county, state or ZIP code for a latitude and longitude. Find the nearest features to a coordinate with distances, and compute geodesic distance between two points in meters and miles. Enrich several coordinates at once with polygon attributes through a spatial join.
When to use it
Useful when you want an assistant to answer location questions about US data — which county, state or ZIP code a point falls in, what is nearby, how far apart two places are, or tagging a batch of coordinates with region attributes — without writing API calls yourself.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. A Terranode API key is required, supplied in the TERRANODE_API_KEY environment variable; the key is obtained by signing up at the provider's app site. Network access to the Terranode API is needed, and the base URL can be overridden with TERRANODE_API_URL.
Before you install
The server requires a Terranode API key stored in the TERRANODE_API_KEY environment variable; keep it out of shared config files and repositories. Coordinates you submit are sent to the third-party Terranode API for processing. Usage may be subject to the provider's account limits or billing.

Installation

In SourceWeft

  1. Open Terranode Geospatial API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@terranode-co/mcp-server

MCP server for spatial queries via the Terranode Geospatial API. Gives AI agents (Claude Desktop, Cursor, etc.) tools to query geospatial datasets — point-in-polygon lookups, nearest feature search, distance calculations, and spatial joins.

Prerequisites

Setup

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "terranode": {      "command": "npx",      "args": ["@terranode-co/mcp-server"],      "env": {        "TERRANODE_API_KEY": "your-api-key-here"      }    }  }}

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

json
{  "mcpServers": {    "terranode": {      "command": "npx",      "args": ["@terranode-co/mcp-server"],      "env": {        "TERRANODE_API_KEY": "your-api-key-here"      }    }  }}

Claude Code

Add to your Claude Code MCP settings:

json
{  "mcpServers": {    "terranode": {      "command": "npx",      "args": ["@terranode-co/mcp-server"],      "env": {        "TERRANODE_API_KEY": "your-api-key-here"      }    }  }}

Available tools

ToolDescription
list_datasetsList all available geospatial datasets (system + custom)
check_locationPoint-in-polygon: which feature contains a coordinate?
find_nearestFind the N nearest features to a coordinate, with distances
calculate_distanceGeodesic distance between two points (meters + miles)
spatial_joinEnrich multiple coordinates with polygon attributes at once

Example prompts

Try these in Claude Desktop or Cursor:

  • "What county is latitude 40.71, longitude -74.00 in?"
  • "What datasets are available?"
  • "Find the 3 nearest counties to Central Park"
  • "How close is my proposed site (40.7128, -74.006) to the nearest school (34.0522, -118.2437)?"
  • "Which states do these 5 warehouse locations fall in?" (paste coordinates)
  • "What ZIP code is 37.7749, -122.4194 in?"

API Reference

The full API spec is available at docs.terranode.co/openapi.yaml (OpenAPI 3.1).

Feedback

Report issues or feature requests: [email protected]

Source: README.md at commit 0bab79e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.10LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts