Permissions & access
What you grant when you authorize, what it requires, and how to disconnect.
What you grant
The consent screen lists what you're granting:
| Scope | What it allows |
|---|---|
profile:read | See your username, name, and avatar |
saves:read | Read your saves and your home feed |
boards:read | Read your boards and the saves on them |
search:read | Search Savee's public library on your behalf |
Private saves and private boards are included — the server shows the assistant the same things you see when you're signed in. If you'd rather keep private board saves out, the Hide private board saves from profile feed setting in Savee applies here too.
search:read is the odd one out: it doesn't expose anything of yours. It reads
Savee's public library — the same thing you'd see searching the site while
signed out — so granting it tells the assistant it may look outward, not that it
may see more of your account.
Search limits
Search is much more expensive to serve than reading your own saves, and it's the only tool that reads the public library rather than your account. It's metered separately and far more tightly:
| Limit | Window |
|---|---|
| 20 searches | 5 minutes |
| 200 searches | 7 days |
The weekly ceiling is the one to know about. It's deliberate — it's what keeps the library from being enumerated a query at a time — and it's per Savee account, so it can't be reset by reconnecting.
It's also a single budget across everything you've connected: searching here and searching through the REST API draw on the same 200.
An assistant that hits it gets a clear error and can carry on using every other tool; only search pauses until the window rolls over.
Requirements
The MCP server needs an active Savee subscription with API access enabled — the same requirement as the REST API. This is checked on every request, not just when you connect, so if your subscription lapses the connection stops returning data until billing is current again.
MCP or the REST API?
Use the MCP server when you want an assistant to read your Savee data conversationally. Use the REST API when you're writing code — it's the same data, and MCP tools are built on the same endpoints.
Disconnecting
Connected apps are listed under Connected apps at Settings → Developers, with what each one can read and when it was last used. Disconnecting takes effect immediately — the app loses access on its very next request, with no grace period.
Most clients also revoke their own access when you remove them on their side. If a client disappears without doing that, disconnecting it here has the same effect.