Model Context Protocol
Your library
from the terminal
Aspects ships an MCP server, so Claude Code and other assistants can work with your library directly.
Ask what you made last week. Ask for the export.
claude mcp add aspects -- /Applications/Aspects.app/Contents/Helpers/aspects-mcp
Added MCP server aspects.
Run once. Settings ▸ Assistants has the exact path for your install.
Reading works with Aspects closed. Acting is off until you turn it on.
- Reads without permission
- Your artboards, decks, notes, exports and final assets are read straight off disk. It works with Aspects closed, and nothing has to be switched on.
- Acting is off until you say so
- Opening, exporting, creating and editing are behind one switch in Settings, off by default, and work only while Aspects is open.
- Exports through the real pipeline
- An assistant presses the same button the panel presses, so a render it starts is the render you would have made, in the same place with the same name.
- Nothing deletes
- There is no tool that removes a document, an export or a file. The worst case is a document you did not want, which you can throw away yourself.
- Nothing leaves your Mac
- The server talks to the app over a loopback socket on your own machine, with a token that changes every launch. No library data is uploaded to run it.
- Already inside the app
- It ships in the bundle rather than as a separate download, so it updates when Aspects updates and cannot fall out of step with your library.
Getting started
Connect it once.
Then just ask.
One command adds Aspects to Claude Code. Reading your library works straight away, with Aspects closed.
Letting it act is a separate switch, and a later decision.
what did I make in Aspects last week?
Fjord pitch — deck, 14 slides, edited Thursday Campaign hero — Capture site, exported 2160×1352 PNG Brand call — note, 400 words 3 documents, 5 exports.
No syntax to learn. It reads the library the way you would.
In practice
Things worth asking for.
Two of these ship as ready-made prompts — a weekly review, and finding a deliverable by what it is rather than what it was called. The rest are just questions.
- “What did I work on this week?”
- Documents touched and files rendered, in one answer. Asking about the work alone misses the output, which is usually the half you wanted.
- “Find the file I sent the client”
- Searches what you promoted to a final asset, where things carry names you chose rather than the tool and the pixel size.
- “What was in my note from the brand call?”
- A note comes back as its full text, so an assistant can summarise it, pull the actions out of it, or draft from it.
- “Export the campaign capture again”
- Starts the real render with the settings the artboard already has, and the file lands where your exports always land.
- “Start a note with these three actions”
- Makes the document in your library rather than somewhere you will have to go and find later.
- “Add today’s decisions to the project note”
- Appends rather than replaces, so nothing you wrote can be overwritten — and it is one undo step if you disagree with the result.