Configure the E2 MCP server

Run E2 as a stdio server and give your MCP client access to the local files, cache, and routing service it needs.

Documentation navigation

Start with E2

SDK guides

CLI guides

MCP guides

Applications

Framework quickstarts

Install or run with npx

terminal

# No global install required
npx -y @embed-earth/mcp-test

# Or install the package in a project
npm install @embed-earth/mcp-test

The published package exposes an e2-mcp executable, but npx -y is the recommended client configuration because it always resolves the package for the server process.

Claude Desktop style configuration

claude_desktop_config.json

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

Filesystem access

Tool	Path access
`e2_compute`	Uses remote/cached data by default, or reads the optional local database path supplied in its request.
`e2_storage_upload`	Reads input data and writes the database and optional output path.
`e2_cache`	Uses the server user's default ~/.e2/cache directory.

Use absolute paths when the MCP host launches the server from an unexpected working directory. Make sure the server user has permission to read and write those paths.

How it connects

The server communicates over standard input and output. Start it from your MCP client and keep ordinary application logs separate from tool responses.

All developer interfaces