rulesync and MCP server

CLIs only accept slash commands they know. atril registers one in each CLI, the bridge /atril <name or task>, plus a router rule that tells the agent to ask atril before a task. Everything else stays on demand, unless you choose to expose it permanently:

atril expose command:review     # recorded in atril.json
atril sync                      # write the bridge, the rule and the exposed artifacts
atril sync --check              # for CI: exit 1 while .rulesync/ is out of date

atril sync writes into rulesync’s sources (.rulesync/), owning only what it wrote through rulesync’s ownership ledger: a hand edit, a file of yours or another writer’s entry stops it with nothing changed. With "rulesync": { "generate": true } in atril.json it then runs rulesync generate, which spreads the pieces to every CLI.

MCP server

atril mcp --root .atril

Serves search, resolve, install and remove as MCP tools over stdio. The store is fixed when the server starts; a tool call never chooses it.