Atlas Platform

Use Atlas from the web app, desktop app, host agents, applications, and API clients.

Hardware work happens across team spaces, local tools, agents, and applications. Atlas expands across these surfaces so users can apply Atlas context where work already happens, connect Atlas to more workflows, and use the same underlying capabilities through the interface that fits the task.

Atlas MCP

Open the MCP guide.

Atlas SDK

Open the SDK guide.

Agentic API

Open the API guide.

​

Product Surface Areas

Choose the surface based on where the user is working and how much control the integration needs.

Surface	Use when	Why
Atlas Web	Teams need a shared workspace for Atlas records and investigations.	Collaborate, share knowledge, and discover hardware issues across a team.
Atlas Desktop	Engineers need Atlas in local hardware workflows.	Update designs, run simulations, and analyze test results close to the files and tools on the workstation.
Atlas MCP	A host agent needs Atlas hardware context.	Expose Atlas context, returned resources, and approved actions to Codex, Claude Code, and other MCP-compatible agents.
Atlas SDK	An application needs a typed chat client.	Create a session, send a message, and stream events from Python or TypeScript.
Agentic API	A service or adapter needs HTTP-level control.	Build adapters, SDKs, and integrations that manage request envelopes, files, runs, returned objects, and actions directly.