Local and Remote MCP
Both modes expose the same Atlas tools and structured result fields.
Start Local MCP
atlas login uses device authorization and stores the user token locally. The MCP server reads that profile and sends Atlas calls under the signed-in user’s permissions.
Local MCP runs over stdio by default. The host sends JSON-RPC messages to the server on stdin. The server writes JSON-RPC messages to stdout and writes logs to stderr.
When the host supports MCP roots, the local server requests roots/list and rejects file:// inputs outside those roots.
Connect to Remote MCP
POST to /mcp. Long requests can return Server-Sent Events, including MCP progress notifications before the final JSON-RPC response. The user bearer token is required on every HTTP request.
Discover Tools
The host discovers Atlas tools through MCPtools/list. Atlas publishes a small registry of product-level tools.
Atlas tools start work, continue work, or apply an action decision. Returned objects, files, and artifacts are MCP resources fetched by URI.
Start a Request
intent controls the request shape. Supported values are answer, search, artifact, and propose_write.
Pass Files
MCP file inputs are request context. Atlas accepts these forms:
Use
file:// only with local MCP. For remote MCP, upload the file to Atlas first or pass small content inline. Atlas MCP converts inline text and blob inputs to Atlas file handles before it calls the Agentic API.
Continue a Session
Useatlas.reply with the session_id returned by a prior Atlas response.
Track Progress
Hosts request progress by adding an MCPprogressToken to the tool call metadata.
notifications/progress while the request runs. Hosts cancel active requests with notifications/cancelled.
Read Results
Atlas MCP returns an answer incontent, compact records in structuredContent, and resource links for full objects, files, and artifacts.
Fetch Returned Resources
Returned files, artifacts, and full object records are URI-addressed. The host reads a linked object, file, or artifact through MCPresources/read.
text. Binary resources return blob. Resource reads use the connected user’s Atlas permissions.