Overview
What the Savee MCP server gives an AI assistant access to, and what it can't touch.
Savee runs a Model Context Protocol server, so AI assistants can read your saves, boards, and home feed directly — no API token to copy, no client code to write. You connect once through your browser and approve the request, the same way you'd connect any other app.
The server URL is:
What you can ask
Once connected, the assistant has twelve tools. You don't call them by name — just ask for what you want.
| Tool | What it reads |
|---|---|
get_current_user | Which Savee account the connection is for, and its plan |
list_saves | Your own saves, newest first — including private ones |
get_save | One specific save, looked up from a savee.com link or its id |
list_feed | Your home feed: saves from people you follow, plus curated content |
list_boards | Every board you can see, including team and collaborator boards |
list_board_saves | The saves on one specific board |
search | Savee's public library — everyone's work, not just yours |
view_saves | The actual images for specific saves, so it can see them |
Four more appear only if you grant write access when you connect:
| Tool | What it changes |
|---|---|
create_board | Makes a new board, or a sub board under an existing one |
update_board | Renames a board, or changes its description or privacy |
save_items | Saves items into your account, optionally onto a board |
remove_save_from_board | Takes one save off a board, leaving it in your account |
Each save comes back with its Savee URL, the original source URL, dimensions, and its dominant colors, so the assistant can reason about what's actually in your collection.
The listing tools return metadata — title, source, dimensions, dominant colours
— which is enough to reason about where something came from and what palette it
uses, but not about what it looks like. view_saves closes that gap: pass it the
ids of a few saves and the assistant sees the images, so it can talk about
composition, layout and typography rather than inferring from titles.
get_save is the one to reach for when you have a specific save in mind rather
than a theme. Paste a link — https://savee.com/i/997d6DW/ — and the assistant
resolves it directly instead of hunting for it through search. It also takes the
bare short id (997d6DW) or an id from an earlier answer, and it reaches your
own saves plus any public save on Savee.
search is the one tool that looks outward. Everything else reads your own
account; search reads the public library, so it's how an assistant finds
references you haven't saved yet. It's metered far more tightly than the other
tools — see permissions.
Things that work well:
- "What have I been saving lately? Group it by theme."
- "Look at my Posters board and describe the visual style it's converging on."
- "Find the saves in my account with a dominant blue, and give me their source links."
- "Summarize what's in my Savee feed today."
- "What is https://savee.com/i/997d6DW/ — where's it from, and what does it look like?"
- "Look at the last ten things I saved and tell me what they have in common visually."
- "Search Savee for brutalist poster design and compare it to what's on my Posters board."
With write access granted, the assistant can also act on what it finds:
- "Make me a board of ceiling lamp inspiration and fill it with the best things you find."
- "Save these to my Posters board."
- "Rename my Textures board to Surfaces and make it private."
- "Take that one off my Posters board — it doesn't fit."
Nothing here can delete
Write access is deliberately partial. An assistant can create boards and saves and take a save off a board, but there is no tool that deletes a save or a board — not gated, not built. The most it can do is add things you didn't want and leave a board untidy, both of which you can undo on savee.com.
Write access is also off unless you grant it. Connections made without the write scopes don't see those four tools at all, so an assistant can't offer to do something it has no permission for. See permissions.