Atlases
An Atlas is a named knowledge domain inside a Workspace. It defines the project scope for memories, Sessions, files, and task context.
Use the Dashboard
Open Dashboard → Knowledge bases to create, rename, organize, and remove an Atlas. The Dashboard is the standard experience for selecting a Workspace, checking membership, and reviewing the content affected by a change.
Use Cloud MCP
Authorized Agents use the Cloud MCP Atlas tools to list and manage project scope. Memory tools accept atlasId when a task requires an explicit domain. When the scope is clear from the active Workspace and project context, the Agent can use the service's normal routing rules.
https://api.tokst.com/mcp
Atlas Properties
| Property | Description |
|---|---|
| Name | Human-readable project or knowledge-domain label |
| Keywords | Terms used to guide automatic memory routing |
| Workspace | Permission and audit boundary that owns the Atlas |
| Content | Related memories, Sessions, files, and task references |
Choose names that express a stable domain, such as “Product platform”, “Customer research”, or “Infrastructure”.
Routing and Boundaries
Atlas keywords help route a memory when an authorized Agent does not provide an explicit atlasId. Explicit task and Session context takes precedence. Review the selected Atlas before storing cross-project information, especially in team Workspaces.
An Atlas does not grant access on its own. Workspace membership and role checks control every read, write, file, Session, and task action.
Archive and cleanup
Archive or move required content before retiring an Atlas. Archiving retains its memories and associated files. A user may permanently clear archived content only from the Dashboard archive view after manual confirmation. Confirm the Workspace and Atlas identity before any lifecycle action.
Runtime Boundary
Cloud MCP manages Atlas data. The optional CLI manages device connection, local endpoint management, task execution, diagnostics, and export.