Install

Pick your tool. Every route ends the same way: your browser opens savee.com, you approve the request, and the client is connected. There's no API key anywhere in this flow.

Check your Savee plan

The MCP server needs an active Savee subscription. If yours has lapsed, the consent screen will tell you so instead of connecting — check your plan.

Add the server

Run this in your terminal:

claude mcp add --transport http --scope user savee https://mcp.savee.com/mcp

--scope user makes Savee available in every project. Drop it if you only want it in the current one.

Authorize

Start Claude Code and run /mcp. Select savee, then Authenticate. Your browser opens savee.com, where you sign in if you aren't already.

Approve

The consent screen lists exactly what you're granting — your profile, saves, and boards, all read-only. Click Authorize and the tab closes itself.

Try it

Back in Claude Code, ask for something:

What have I been saving on Savee lately?

Check your Savee plan

The MCP server needs an active Savee subscription — check your plan.

Add a custom connector

In Claude, open Settings → Connectors → Add custom connector, and paste:

https://mcp.savee.com/mcp

Authorize

Claude opens savee.com in your browser. Sign in if you aren't already, then Authorize on the consent screen.

Try it

Start a new chat and ask:

Look at my Savee boards and tell me what visual themes they share.

Check your Savee plan

The MCP server needs an active Savee subscription — check your plan.

Add the server

Open Settings → MCP → Add new MCP server, choose the HTTP type, and use:

https://mcp.savee.com/mcp

Or add it to ~/.cursor/mcp.json directly:

{
  "mcpServers": {
    "savee": {
      "url": "https://mcp.savee.com/mcp"
    }
  }
}

Authorize

Cursor prompts you to sign in. Approve the request on savee.com and the server shows as connected.

Check your Savee plan

The MCP server needs an active Savee subscription — check your plan.

Add the server

Run this in your terminal:

code --add-mcp '{"name":"savee","type":"http","url":"https://mcp.savee.com/mcp"}'

Authorize

Open Chat, switch to Agent mode, and select Savee from the tools list. VS Code sends you to savee.com to approve.

Any client that speaks Streamable HTTP works. Add:

https://mcp.savee.com/mcp

The client discovers everything else on its own: it gets a 401 carrying a WWW-Authenticate challenge that points at our protected resource metadata, which names savee.com as the authorization server. From there it registers itself and runs the OAuth flow without any manual configuration.

If your client still uses the older HTTP+SSE transport, it can connect through mcp-remote instead.

See For client developers for the protocol details.

What you'll see when authorizing

Savee shows you the connecting app's name, the exact permissions it's asking for, and where you'll be sent back to. Nothing is granted until you click Authorize, and you can revoke it later from Settings → Developers.

On this page