atlaslisted

# The atlas Tools: `atlas` and `settings` on the atlas MCP server. Both work from any session: in a knowledge base, in a project, or in a folder the atlas does not know. ## See what exists 1. Call `atlas`. It returns every knowledge base with its path, scope, mode, state, and the projects that use it; every project with its path, description, knowledge base, open thread counts, and whether a page describes it; the folders the atlas cannot read, with a reason; and the settings. 2. Show a compact picture: each knowledge base, then the projects under it, then the projects that use no knowledge base. Name each problem entry and its reason. Keep it short; the user asked for orientation, not a dump. 3. Say what needs attention: a project whose knowledge base is not on this machine, a project no page describes, a registered folder that is gone, a blocked or stale thread. ## Route | The user wants | Skill | |---|---| | Make this folder a project; link, unlink, rename, or forget one | `atlas-project` | | Create a knowledge base; change its scope or mode | `atlas-knowledge` | | Work inside a knowledge base or a project | `wiki` | | See or change threads across projects | `thread` | ## Settings and refresh - `settings` with `new_days` sets it and returns all; with no arguments it reads. Say what the value means before changing it: how long a knowledge base or project counts as new in the view. - `atlas` with `refresh: true` reads everything again and r