Maps & transport · Local MCP server
Terranode Geospatial API
Point-in-polygon, nearest feature, spatial join, and distance tools for US geospatial datasets.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.terranode-co/mcp-server-terranode- Version
- 0.1.10
- Status
- Active
- Category
- maps & transport
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-13
- Updated
- 2026-04-13
- Publisher
- terranode-co (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/terranode-co) · how
- Website
- docs.terranode.co/integrations/mcp/
- Repository
- github.com/terranode-co/mcp-server-terranode
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @terranode-co/mcp-server | 0.1.10 | stdio |
How to connect Terranode Geospatial API
Terranode Geospatial API runs locally from a Node.js package published to the npm registry: @terranode-co/mcp-server version 0.1.10. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @terranode-co/mcp-server@0.1.10. It reads these environment variables: TERRANODE_API_KEY (required, secret) and TERRANODE_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-server-terranode": {
"command": "npx",
"args": [
"-y",
"@terranode-co/mcp-server@0.1.10"
],
"env": {
"TERRANODE_API_KEY": "<secret>",
"TERRANODE_API_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, docs.terranode.co, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More maps & transport servers
| Server | Runs |
|---|---|
| Taxis FabbrimoneTaxi in Waterloo, Belgium: business info, ride price quotes and ride booking requests. | Remote · HTTPLive check: ✓ handshake |
| Tdx MCPTaiwan TDX: TRA/THSR stations, live boards, timetables. | Local · stdio |
| Terminal49Terminal49 MCP - wraps the Terminal49 ocean/container shipment tracking API. | Remote · HTTPLive check: ✓ handshake |
| Terminal49Find and monitor ocean shipments and containers, and create new tracking requests. | Remote · HTTPLive check: sign-in required |
| The New Engineer - HVACEuropean HVAC sizing: EN 12828 expansion vessels, EN 378 zones, Swiss refrigerant rules. | Remote · HTTPLive check: ✓ handshake |
| Tlaloc MCPOfficial Mexican data for AI agents: CURP, RFC, CFDI, postal codes, phone, SPEI/CEP, DOF, geocoding. | Remote · HTTPLive check: sign-in required |
| Tokenguard MCPReal-world data for agents: air quality, geocoding, quakes, holidays, web search. | Remote · HTTPLive check: ✓ handshake |
| TollmintPer-call data for agents: graded behavioural science, dark-pattern detection, web fetch, geocode. | Remote · HTTPLive check: ✓ handshake |