Give AI agents access to Earth
The E2 MCP server exposes search, cache management, routing, remote/local compute, dataset upload, catalogs, and cell operations over standard input and output.
Documentation navigation
Start with E2
SDK guides
CLI guides
MCP guides
Applications
Framework quickstarts
Run the server
terminal
npx -y @embed-earth/mcp-testMCP clients start this process and communicate over standard input and output. The server logs its status to stderr so tool responses remain valid JSON text content.
Client configuration
mcp.json
{
"mcpServers": {
"e2": {
"command": "npx",
"args": ["-y", "@embed-earth/mcp-test"]
}
}
}Add this server entry to an MCP client that supports stdio servers. See setup details for Claude Desktop, environment variables, and local files.
Available tools
| Tool family | Capabilities |
|---|---|
e2_search | Multi-feature, multi-area search returning GeoJSON. |
e2_cache | List, resize, delete, and clear local data. |
e2_route | Route, matrix, isochrone, map match, locate, and height. |
e2_route_to_feature | Route to the nearest indexed feature. |
e2_compute | Eight remote, cached, or local spatial compute primitives. |
e2_compare | Compare two features or two areas. |
e2_storage_upload | Import user data and create a local data file. |
e2_features_search / e2_regions_search / e2_datasets_list | Discover E2 metadata. |
e2_encode / e2_decode / e2_neighbors | Create and traverse E2 cells. |
Local-first behavior
Search uses the same local and remote behavior as the SDK. Compute and storage operate on paths visible to the MCP server process. All tool results are serialized as JSON text content.