-
Notifications
You must be signed in to change notification settings - Fork 1
Dashboard and HTTP API
Atlas can run a local dashboard, HTTP API, repository watcher, and MCP endpoint from one process.
atlas serveUseful variants:
atlas serve --open # also auto-open the dashboard in your browser
atlas serve --watch=false # do not keep the graph fresh in the background
atlas serve --mcpDefault address:
http://127.0.0.1:3099
Dashboard:
http://127.0.0.1:3099/dashboard
curl http://127.0.0.1:3099/healthz
curl http://127.0.0.1:3099/readyz
curl http://127.0.0.1:3099/openapi.json-
healthzconfirms the process is running. -
readyzconfirms Atlas can answer a lightweight engine request. -
openapi.jsonis the version-specific API contract.
curl http://127.0.0.1:3099/api/v1/status
curl http://127.0.0.1:3099/api/v1/stats
curl "http://127.0.0.1:3099/api/v1/search?q=Checkout"Use the OpenAPI document rather than copying old request shapes from historical examples.
Loopback is the safe default. Before binding to another interface:
export ATLAS_API_TOKEN='replace-with-a-strong-token'
atlas serve --mcp --addr 0.0.0.0:3099Authenticated request:
curl \
-H "Authorization: Bearer $ATLAS_API_TOKEN" \
http://host:3099/api/v1/statusATLAS_API_TOKEN protects /api/v1/* and POST /mcp. Browser clients from
additional origins must also be explicitly allowed:
export ATLAS_MCP_ALLOWED_ORIGINS='https://trusted.example'Use TLS at a trusted reverse proxy when traffic leaves the machine.
When a token-protected dashboard requests credentials, supply the configured Atlas API token. The dashboard uses authenticated API calls and a short-lived stream credential for live updates.
Do not place the API token in shared links, logs, screenshots, or source control.
atlas status
atlas doctor
lsof -nP -iTCP:3099 -sTCP:LISTENIf healthz passes but readyz fails, indexing or database maintenance may be
blocking engine requests. Wait for the current operation or stop competing
Atlas processes before retrying.
Atlas | Releases | Benchmarks | License