AutoShelf is a macOS app that watches your folders and auto-organizes files. Set a rule once and never think about it again. Free to try, unlock unlimited for $19.99.
Replies
Best
The MCP + CLI support is what makes this more than another folder-watcher — it means an agent can drive the organizing, not just a background rule quietly firing. Two setup questions: through the MCP server, can an agent create and modify rules and query where a given file ended up, or is it limited to triggering rules that already exist? And are the rules stored as a portable file I can version and move to another Mac, or are they locked in app state?
@noctis06 An agent can create, edit, delete, and run rules, but can't query file locations. Rules are JSON files you can move to another Mac, but folder permissions need to be re-set.
Report
Makes sense, and the portable-JSON-rules part is the piece I care about most. Quick follow-up on the can't-query-file-locations gap: when the agent runs a rule, does the execution hand the resulting destination path back to it (a receipt), so it knows where a file landed without a separate lookup? Otherwise the agent is organizing a bit blind after the fact.
@noctis06 The AI can call get_rule to see the full rule definition: which folder it watches, what condition it checks, and what action it takes with the destination path. So if a rule says "move PDFs from Downloads to /Documents/PDFs", the AI knows that's where files went without needing a per-file receipt. It's not blind, it just can't track individual file paths after execution.
Replies
The MCP + CLI support is what makes this more than another folder-watcher — it means an agent can drive the organizing, not just a background rule quietly firing. Two setup questions: through the MCP server, can an agent create and modify rules and query where a given file ended up, or is it limited to triggering rules that already exist? And are the rules stored as a portable file I can version and move to another Mac, or are they locked in app state?
AutoShelf
@noctis06 An agent can create, edit, delete, and run rules, but can't query file locations. Rules are JSON files you can move to another Mac, but folder permissions need to be re-set.
Makes sense, and the portable-JSON-rules part is the piece I care about most. Quick follow-up on the can't-query-file-locations gap: when the agent runs a rule, does the execution hand the resulting destination path back to it (a receipt), so it knows where a file landed without a separate lookup? Otherwise the agent is organizing a bit blind after the fact.
AutoShelf
@noctis06 The AI can call get_rule to see the full rule definition: which folder it watches, what condition it checks, and what action it takes with the destination path. So if a rule says "move PDFs from Downloads to /Documents/PDFs", the AI knows that's where files went without needing a per-file receipt. It's not blind, it just can't track individual file paths after execution.