# Opentopography [Health: Active]

**Category:** 🗺️ Location Services  
**Repository:** https://github.com/pipeworx-io/mcp-opentopography  
**GitHub Stars:** 1  
**npm Downloads (last month):** 453  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/opentopography

## Description
OpenTopography global DEM rasters + point queries (free key)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "opentopography": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-opentopography"],
    "env": {
      "PLATFORM_OPENTOPOGRAPHY_KEY": ""
    }
  }
}
```

**Requires environment variables:** `PLATFORM_OPENTOPOGRAPHY_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Opentopography does

The Opentopography MCP server exposes OpenTopography's global digital elevation model data to MCP-compatible applications. It supports both a single-coordinate elevation lookup and raster requests covering a geographic bounding box. The service also provides a dataset listing so an agent can inspect available DEM options before making a query.

The supported datasets are SRTMGL1, SRTMGL3, AW3D30, NASADEM, COP30, and COP90. SRTMGL1 is the default and provides 30 m data. COP30 represents the Copernicus 30 m dataset, while the other names identify additional DEM sources offered through OpenTopography.

## How it works

The Opentopography MCP server defines three pack-specific tools:

- `point_elevation(lat, lon, dataset?)` returns the elevation at one latitude and longitude. The implementation calls OpenTopography's point service as a convenience, even though the platform's main service is raster-oriented.
- `dem(dataset, south, north, west, east, format?)` requests a DEM raster for a bounding box and returns a download URL.
- `datasets()` lists the available DEM datasets.

The gateway endpoint is available at `https://gateway.pipeworx.io/opentopography/mcp`. A full Pipeworx gateway endpoint is also available. The pack endpoint includes the three OpenTopography tools plus shared Pipeworx meta-tools, while the local package exposes only the pack-specific tools. Gateway requests can also be made through the HTTP tools API, such as a JSON POST to the `point_elevation` endpoint.

## Setup and configuration

A free OpenTopography API key is required. Through the Pipeworx platform, authentication uses the `PLATFORM_OPENTOPOGRAPHY_KEY` environment variable. The underlying API also accepts a key through the `?_apiKey=...` query parameter.

For a remote MCP connection, configure the gateway URL in an MCP client. The README names Claude Desktop, Cursor, and Windsurf as examples. For a local connection, run `npx -y @pipeworx/mcp-opentopography` or configure the package as a stdio server with the `@pipeworx/mcp-opentopography` npm package. The local mode does not require a Pipeworx account or a gateway round trip.

## Tools and capabilities

The Opentopography MCP server fits workflows that need terrain data tied to coordinates or regions. Agents can select a dataset, retrieve a point elevation, or obtain a URL for a raster covering south, north, west, and east bounds.

The remote gateway additionally supports Pipeworx-wide discovery and routing tools, including `ask_pipeworx`, `discover_tools`, `search_within`, `remember`, and `recall`. These are gateway capabilities rather than OpenTopography-specific tools.

## Limitations and notes

Raster requests return a download URL rather than raster contents directly. Point elevation is a one-point convenience operation and is distinct from the raster service. A valid API key is needed for OpenTopography access. Gateway connections expose more tools than the standalone package, so clients may see roughly 30 shared tools alongside the pack tools; the connection's `initialize` response is authoritative for the exact list.

_Full upstream README: https://allmcps.com/mcp/opentopography/readme_