Finally, plug your creative findings into your AI tools.
Every save on the platform — websites, sections, images, snippets — is one MCP connection away from every AI tool you use.
Connect your creative
knowledge base to the work.
Ask for it the way you'd say it.
Describe what you're looking for and it finds it: "that minimal dark dashboard", "the type poster I uploaded", "the nav I built for Arc".
It searches everything in your workspace: saved, uploaded, or built there.
It sees the reference, not the filename.
Websites, captured sections, uploaded images and PDFs come back as the actual image, delivered inline for the model to analyze. Saved videos come back as their preview frame.
So when you ask for "sections with playful typography", it's matching what a model actually saw in each screenshot, not words you had to write about them.
Your folders are the context.
Ask for something by where it lives. Folders, workspaces and item types all come through, so "the save.design logo in my Platform Assets folder" is an instruction it can follow.
You stop hunting through folders yourself, and you stop pasting assets into chat to explain which one you meant.
Snippets and docs, straight into the build.
Components you built in the editor come back as real source files. Pages come back as markdown. Your own notes come back attached to whatever you wrote them on, and a saved website brings its tech-stack breakdown along too.
Your agent picks up where you left off, working to the conventions you already set instead of inventing new ones.
Six tools. Read-only.
That is the whole API your AI gets. It can look at what you saved and read it back — it cannot save, edit, move, or delete anything in your workspace.
list_workspacesEvery workspace you can reach, and which ones MCP is allowed to read.
list_foldersThe folders inside those workspaces, for scoping a request to one project.
list_itemsEverything you saved, newest first — websites, links, files, pages, components, sections.
get_itemA light summary of one item: title, source, folder, your note, type-specific metadata.
read_item_contentThe full thing on demand — markdown, source code, file contents, or the image itself.
search_itemsNatural-language search ranked across your own saves. No global library mixed in.
One URL. Any MCP client.
MCP is an open protocol, so this is not an integration we had to build tool by tool. If your app speaks MCP, it can read your library.
Copy the server URL
One endpoint for your whole account. It works for every workspace you can read.
Add it in your AI tool
Paste it as a custom connector or MCP server. Cursor and VS Code take a one-click link; Claude Code takes a single command.
Sign in with save.design
OAuth, in the tool you're already in. No API keys to generate, rotate, or leak — and you can revoke any connection from settings.
https://save.design/api/mcpExact instructions for each tool live in your account settings once you’re signed in.
Answers
Answers
What is MCP, exactly?+
The Model Context Protocol — an open standard for connecting an AI tool to a data source. You add one server URL to Claude, Cursor, ChatGPT, or any other MCP client, authorize it once, and the tool can call that server's tools mid-conversation. save.design runs one for your library.
What can my AI actually see?+
Everything in a workspace it's allowed to read: websites and their tech-stack analyses, captured sections, uploaded files, images and videos, code snippets and components you built, written pages, and the notes and folders you filed them under. Visual items come back as the real image, so the model can look at them rather than read a filename. A shared workspace is shared here too — if a teammate saved it there, your agent can read it.
What if I never named or tagged the file?+
It still turns up. Images are analyzed the moment you upload them — a model writes the title, the description, and search attributes covering technique, mood, colour and typography — and a PDF's contents are read straight into its index. So Untitled-3.png doesn't stay Untitled-3.png: it gets a real title and is found by what's in the picture. Its folder counts too — anything in "Client — Arc" answers to "Arc".
What about saved videos and screen recordings?+
Recordings come back as their preview frame, so your AI sees what a clip is. Animated sections from the library were analyzed as video when they were added, so they're searchable by their motion. Clips you upload yourself aren't re-watched yet — those answer to their title, your note, and their folder.
Can it change or delete my saves?+
No. The server exposes six read-only tools — list, get, read, search. There is nothing in the API that writes, moves, or deletes.
Does it search the whole save.design curated websites and elements library?+
No — only yours. Search runs over the items in your own workspaces. The curated public library is a separate thing and never gets mixed into results.
Which plan includes it?+
The personal MCP endpoint comes with Individual and Team membership. Access is granted per workspace.
How does signing in work?+
Standard OAuth. Your tool sends you to save.design, you approve the connection, and it gets a token — no API keys to generate, copy around, or rotate.
Can I disconnect a tool later?+
Yes. Account settings → Integrations lists every connected app with a revoke button. Revoking kills that tool's access immediately; the others keep working.
Your library, inside
every tool you build in.
Connect it once. Stop describing what you already saved.