MCP server for E2. It exposes search, cache, routing including feature-backed destinations, cloud/local compute, comparisons, user dataset storage, catalog discovery, and cell encode/decode over stdio. The e2_map_sources tool resolves the Planet basemap and published feature PMTiles sources for Map clients.

Product: embed.earth · Docs: MCP docs · Docs home

Related interfaces: SDK docs and CLI docs.

The MCP server is the agent-facing interface to the same capabilities exposed by the @embed-earth/sdk-test SDK and the @embed-earth/cli-test CLI.

Run

The e2_route tools use https://route.embed.earth by default. Set ROUTE_URL in the MCP host environment to use another compatible routing service.

npx -y @embed-earth/mcp-test

Add it to an MCP host using a standard stdio configuration:

{
  "mcpServers": {
    "e2": {
      "command": "npx",
      "args": ["-y", "@embed-earth/mcp-test"],
      "env": {
        "ROUTE_URL": "https://route.embed.earth"
      }
    }
  }
}

Do not place a real credential in a checked-in MCP configuration. ROUTE_URL is optional because the server already uses https://route.embed.earth.

Tool layout

Group	Tools	Purpose
Search	`e2_search`	Search features and return GeoJSON
Routing	`e2_route`, `e2_route_to_feature`	Run routing operations or route to an indexed feature
Compute	`e2_compute`, `e2_compare`	Run spatial primitives or compare features/areas
Catalogs	`e2_features_search`, `e2_regions_search`, `e2_datasets_list`	Discover available data
Local data	`e2_cache`, `e2_storage_upload`	Manage snapshots or index user data
Map	`e2_map_sources`	Resolve basemap and feature PMTiles
Cells	`e2_encode`, `e2_decode`, `e2_neighbors`	Encode, decode, and traverse cells

Input conventions

Input	Convention
`feature`	A feature key or numeric feature ID
`area`	A human-readable area name
`area_id`	An exact catalog ID; do not wrap it in a provider-specific prefix
`mode`	`cloud`, `offline`, or `auto` for search/compute
`database`	Optional local SQLite path for compute and upload workflows

e2_route accepts route, matrix, isochrone, mapMatch, locate, or height as its operation. e2_compute accepts NEAREST, DISTANCE, WITHIN, COUNT, DENSITY, COVERAGE, GAPS, or CLUSTER.

Use the regions catalog and features catalog to discover valid area, area_id, and feature inputs before calling a tool.

Practical tool calls

Search a named area, or use the raw exact area ID 4915 for New York:

{
  "feature": "restaurant",
  "area": "New York",
  "limit": 25,
  "mode": "auto"
}

{
  "feature": "restaurant",
  "area_id": "4915",
  "limit": 25
}

Run a spatial relation with e2_compute:

{
  "primitive": "NEAREST",
  "feature": ["restaurant"],
  "area_id": "4915",
  "near": "park",
  "distanceMeters": 500,
  "limit": 3,
  "mode": "cloud"
}

Route with e2_route by passing the operation and its body:

{
  "operation": "route",
  "body": {
    "locations": [
      { "lat": 40.74, "lon": -73.99 },
      { "lat": 40.71, "lon": -74.01 }
    ],
    "mode": "walking"
  }
}

Use e2_route_to_feature when the destination is a feature instead of a coordinate. e2_cache manages downloaded snapshots, e2_storage_upload imports GeoJSON/CSV/Parquet into SQLite, and e2_map_sources returns the Planet basemap plus published feature PMTiles sources.

Open-source foundation

The server uses the standard MCP runtime and delegates geographic work to the SDK:

Tool	Role in the MCP package
Model Context Protocol SDK	Tool registration and stdio transport
Zod	Runtime validation for tool inputs
EmbedEarth SDK	Search, routing, compute, catalogs, storage, and map sources
H3	Spatial cell operations through the SDK
PMTiles	Published map source descriptors through the SDK