Connect Saive to your AI

Saive speaks MCP, the open protocol AI assistants use to reach external tools. Connect it once and your assistant can search your library, read your saves and highlights, and save new links for you, all against your own account over OAuth. The connector sees exactly what you see, and nothing is shared with anyone else.

Server URL: https://app.saive.my/api/mcp

Claude (web, desktop, mobile)

Open Settings → Connectors (on claude.ai: your initials → Settings → Connectors).
Click Add custom connector.
Name it Saive, paste the server URL above, and click Add.
Claude opens a Saive sign-in and consent screen. Approve it. That is the OAuth grant; there are no API keys to copy.
In any chat, enable the Saive connector from the tools menu and try: "What have I been saving about batteries lately?"

Claude Code

One command:

claude mcp add --transport http saive https://app.saive.my/api/mcp

Then run /mcp inside Claude Code to complete the browser sign-in the first time. claude mcp list should show saive ✓ connected.

Other clients

Any MCP client that supports remote servers with OAuth (ChatGPT connectors, Cursor, and others) works the same way: give it the server URL and complete the sign-in it opens. No manual client registration is needed.

What your AI can do once connected

Tool	What it does
`library_overview`	Counts, top tags, folders, date range. Orientation.
`search_saves`	Full-text search and filtered browse of every save, archived included.
`get_save`	One save's full record: summary, tags, your note, highlights.
`get_save_content`	The saved article text, with your `==highlights==` marked.
`list_tags`	Your tag vocabulary, your tags and AI tags separately.
`list_folders`	Folders with counts and sharing level.
`list_highlights`	Everything you have underlined, filterable.
`save_url`	Save one URL into your library, with optional tags, folder, and note.

Notes for the beta:

Every connection can read and save. A finer read-versus-write grant is planned. Your assistant will still ask you before it calls save_url, and a stray save is visible in your library and reversible like any other.
Saves made by your AI follow the same rules as your own: the same rate limits and the same AI-processing quota. They land as unread, private by default, and Saive fetches the page server-side.
Reading is free during the beta, rate-limited at 120 calls per minute so an agent loop cannot run away.

Troubleshooting

The consent screen never appears. Your client may have cached a failed attempt. Remove the connector and add it again.
"Rate limit exceeded — retry in Ns." The read limiter. Wait and retry.
save_url says the folder doesn't exist. The tool does not create folders. Make the folder in Saive first, or ask your assistant to run list_folders.
Disconnecting. Remove the connector in your client. You can also revoke the grant from your Saive account's connected-apps list at any time.