getting-started
Atlas public MCP

Atlas public MCP

The canonical HTTP entrypoint for the four public sensor tools is:

POST {API_BASE}/api/v1/atlas/mcp

Use header x-api-key. JSON-RPC 2.0 (tools/list, tools/call).

Resource (in monorepo docs/)Purpose
ATLAS_MCP_QUICKSTART.mdMinimal steps + schema export command
ATLAS_MCP_KEY_AND_CURSOR.mdKey, Cursor, production URL
MCP_ATLAS_PUBLIC_ENDPOINT.mdFull HTTP reference, legacy URL, limits
ATLAS_PUBLIC_MCP_TOOLS.jsonGenerated tool inputSchema (run npm run export:atlas-mcp-tools -w @interstitial/api)

Tools

  1. describe_atlas — Database summary (counts, services, coverage).
  2. search_sensors — Bbox / point+radius / limit.
  3. get_readings — Series or latest; raw window cap 90 days without aggregate.
  4. describe_sensor — One sensor by id.

tools/list (local)

API_BASE=http://127.0.0.1:3001
KEY=dev-key-12345
curl -sS -X POST "$API_BASE/api/v1/atlas/mcp" \
  -H "Content-Type: application/json" \
  -H "x-api-key: $KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

describe_atlas

curl -sS -X POST "$API_BASE/api/v1/atlas/mcp" \
  -H "Content-Type: application/json" \
  -H "x-api-key: $KEY" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"describe_atlas","arguments":{"include_bounds":false}}}'

JSON schema export

docs/ATLAS_PUBLIC_MCP_TOOLS.json in the repository is generated from the API source of truth. After changing tool definitions, run from the monorepo:

npm run export:atlas-mcp-tools -w @interstitial/api

Related

Quickstart (services)OpenAPI Spec