Ask your own library a question
June 1, 2026
AI assistants are good at answering questions about things they can see. The catch is that most of what I have collected over the years is not on the public web. It is in my own library, on my own disk, and I would rather it stayed there.
Markie has a small MCP server built in. MCP is just a standard way for an assistant like Claude to use a tool, and here the tool is your collection. With it connected, you can ask the assistant things like find the dashboard screenshots with a dark background, or pull the brand references tagged orange, and it searches your actual library and hands back the matches.
I use it when I am deep in a conversation about a design and I want to bring in a few references without breaking off to go hunting for them. I ask, it finds them, they are there. I also use the Markie MCP when I generate presentations. In my AI skills I have it set up to automatically search and populate the decks with my own content that is already on brand and approved.
The part that matters to me is where your library lives. The files stay on your machine, and the MCP server reads from them locally. It does not ship your collection off somewhere. When you ask the assistant to pull something, that result becomes part of your conversation with it, the same as any file you would hand it, and that part is covered by the assistant's own privacy policy. You stay in control of what you share and when.
If you also turn on local tagging, the descriptions it searches were written by a model running on your own computer too. Saving, describing, and searching all happen locally. The only thing that ever leaves is what you choose to pull into a conversation, when you choose to.
It turns a folder of saved images into something you can actually talk to. Not a cloud you pour your life into. A private library that happens to be legible to the tools you already use.