E2 MCP tool reference

Every registered E2 MCP tool returns JSON text content and validates its inputs with a Zod schema.

Documentation navigation

Start with E2

SDK guides

CLI guides

MCP guides

Applications

Framework quickstarts

Search and cache

Tool	Inputs	Behavior
`e2_search`	feature, area or regionId, mode, limit, bbox, where, properties	Returns a GeoJSON FeatureCollection.
`e2_cache`	action=list\|set\|delete\|clear; size or key as needed	Manages the default local data cache.

e2_search.json

{
  "feature": ["restaurant", "hospital"],
  "area": ["Manhattan", "Brooklyn"],
  "mode": "auto",
  "limit": 100
}

Cells

Tool	Inputs	Behavior
`e2_encode`	lat, lng, time, spatialResolution, temporalResolution, optional feature	Encodes a spacetime cell ID.
`e2_decode`	id	Decodes a cell into version, spatial, temporal, and feature data.
`e2_neighbors`	id, optional k from 1 to 10	Returns spatial neighbors.

Routing

Tool	Inputs	Behavior
`e2_route`	operation and body	Operation is route, matrix, isochrone, mapMatch, locate, or height.
`e2_route_to_feature`	feature, from, optional area and mode	Finds the nearest feature and routes to it.

e2_route.json

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

The MCP tool currently exposes six route operations. The SDK and CLI also expose additional request support.

Compute and storage

Tool	Required inputs	Optional inputs
`e2_compute`	primitive, feature	database, mode, region or area, near, within, distanceMeters, limit
`e2_compare`	features or feature plus areas	database, primitive, mode, region
`e2_storage_upload`	path, database	feature, connectTo, featureId, output, region

e2_compute.json

{
  "primitive": "COUNT",
  "feature": ["restaurant"],
  "area": "Manhattan",
  "near": "park",
  "distanceMeters": 500,
  "mode": "auto"
}

Catalog discovery

Tool	Input	Behavior
`e2_features_search`	query	Searches the feature registry.
`e2_regions_search`	query	Searches the region catalog.
`e2_datasets_list`	none	Lists datasets available to E2.

Validation defaults

The server validates latitude and longitude ranges, spatial resolution 0 through 15, known temporal resolutions, positive limits, relation distances, and operation enums before calling the SDK. Search and compute limits default to 1,000 and cap at 100,000.

All developer interfaces