Readwise Reader for AI agents
Readwise Reader is a reading app for saving, organizing, and reviewing articles, PDFs, and other documents. Readers use it to build a queue of content and keep notes across sources. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Readwise Reader.
Save an article to the reading queue
Add a new document to the library so it is ready to read later.
Check saved documents read-only
List documents in the library to find one to reference in a summary.
Delete a document with approval
Remove a saved document only after the user confirms it is no longer needed.
6 Readwise Reader actions, graded by risk.
Every Readwise Reader action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- readwise_reader.list_tagsList Tags
- readwise_reader.list_documentsList Documents
write
3Create and change things. Allow, or ask the user first.
- readwise_reader.update_documentUpdate Document
- readwise_reader.save_documentSave Document
- readwise_reader.bulk_update_documentsBulk Update Documents
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- readwise_reader.delete_documentDelete Document
Readwise Reader in three steps.
- 01Your users connect Readwise ReaderThey add their Readwise Reader api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “update Document” can wait for the user, and “delete Document” can be denied outright.
- 03Any agent can actYour agent calls Readwise Reader through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('readwise_reader', { read: 'allow', write: 'ask', // update_document destructive: 'deny', // delete_document }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Readwise Reader connects.
Users add their Readwise Reader api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Readwise Reader connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Readwise Reader from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Readwise Reader and Arc0, answered.
Can I use Readwise Reader with Claude, ChatGPT or Cursor?
Yes. Connect Readwise Reader to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Readwise Reader actions you allow.
How do users connect Readwise Reader?
Users add their Readwise Reader api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Readwise Reader actions can my agent take?
6 in total: 2 read, 3 write and 1 destructive, such as “update Document”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Readwise Reader?
Yes. Actions like “delete Document” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Readwise Reader too?
Yes. The same Readwise Reader connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Readwise Reader into your agent.
Your users connect Readwise Reader once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan