Readwise
by Readwise
Search every highlight you have saved and triage your Reader inbox from your AI assistant. 22 tools, OAuth sign-in with separate read and write scopes, and a paid subscription after a 30-day trial.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Readwise via MCP
https://mcp2.readwise.io/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Readwise Tools & Capabilities (22)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- It is paid software, and the two products are gated differently. Readwise states there is no free plan after the 30-day trial. More precisely: Readwise's pricing page lists Readwise Lite at $5.59 a month billed annually and marks the Reader app as not included at that tier, while the full Readwise plan at $9.99 a month billed annually explicitly includes Reader. So one subscription covers both products, but only the full one — a Lite subscriber connecting this server gets the seven
readwise_*tools working against a library the fifteenreader_*tools have nothing to read. - Deletion of a highlight is soft, not permanent — which cuts both ways. It is the reason an agent cannot destroy your notes. It is also the reason you cannot use this connector to genuinely erase anything: Readwise directs you to the original source for that.
- There is no undo tool. Readwise's undo is a keyboard shortcut in the web app and shake-to-undo on iOS. An agent cannot reverse its own discard; you do it afterwards, by hand.
- Reader's Trash is device-specific. Readwise states a deleted document must be restored from the device that deleted it. No connector tool deletes a document today, so this is a boundary to know rather than a live risk.
- We could not read tool schemas or safety annotations. The server is gated and our anonymous handshake returned HTTP 401. Every behavioural claim above comes from Readwise's documentation or its skills repository, never from a schema we read. We make no claim about
readOnlyHintordestructiveHinton any tool. entry.permissionsis absent from Anthropic's snapshot for this server. The single cheapest read/write cross-check is unavailable, and we state that rather than substituting a quieter inference.- The deprecated endpoint is still live and still documented.
https://mcp.readwise.io/sseanswers anonymously, exposes two tools, reaches Readwise highlights only, and publishes a descriptor with no scopes. Readwise's own legacy guide still prints that URL. Check which endpoint your client holds. - Batch operations have documented ceilings. Readwise documents
reader_bulk_edit_document_metadataas covering up to 50 documents per call, and states that it andreader_move_documentsshare a rate limit of 20 calls per minute, advising you to batch IDs into fewer calls. - The platform API is rate-limited at 240 requests per minute per access token, with a lower limit on highlight and book listing endpoints and a
429carrying a wait time. Readwise does not state how MCP tool calls map onto those counters, so treat the figure as platform-wide rather than connector-specific. - Search is an index, and an index can miss. Readwise's own FAQ concedes that search and recency filtering can omit documents you know you saved, and advises naming the topic or roughly when you saved it, or asking for a list by topic first.
- No prompts or resources on the current server. Anthropic's snapshot records no prompt names for this connector, and we could not probe the gated server's capabilities. On the deprecated endpoint both capabilities are declared and both list empty.
- It has no end-to-end encryption. Readwise states this plainly and describes both products as consumer software optimising for user experience over enterprise compliance. Weigh that against whatever you have saved.
Frequently asked questions
Does this access my Reader documents or just my Readwise highlights?
Both, through one connection. Readwise states the integration indexes your Readwise highlights and your Reader documents and makes all of them available to connected AI apps. That is why the tool names split into two prefixes: seven readwise ones covering saved highlights, and fifteen reader ones covering the read-later library.
Is this related to the older Readwise MCP server?
It replaces it. Readwise states the previous Readwise-only server is being deprecated in favour of this one, which covers both products. Readwise tells anyone who configured the old server to update their AI app to the new URL. We found the old host still answering on 2026-08-18, so the switch is on you to make.
Can I undo a tag or move that the MCP made?
Yes for tags and moves. Readwise states every action the MCP takes is reversible the same way you would undo it in Reader, by removing the tag, moving the document back or restoring it from archive, and that you can ask the assistant to undo what it just did. Deletion is a separate question.
How often does the index update?
Continuously, in the background. Readwise states the index updates automatically as you add or change content, and that after the initial full index later syncs only process new or changed material so they finish quickly. A document saved moments ago may still be mid-index when an assistant searches for it.
Can I connect multiple AI apps at the same time?
Yes, with no stated ceiling. Readwise states you can use the same MCP server URL with as many compatible apps as you like. Each app runs its own OAuth authorisation, so every connection is a separate grant that you approve and can revoke on its own without disturbing the others.
Does Readwise offer a free plan?
No. Readwise states there is no free plan after the free trial, which runs 30 days. The connector fronts a paid subscription, so budget for it before wiring an agent to it. Readwise does document discounts for students, teachers, non-profits, military, first responders and people in countries with depressed currencies.
Why can't I permanently delete highlights?
Because Readwise stores a soft discard rather than a hard delete. Readwise explains it keeps the record so a re-sync from Kindle or another source does not re-import the highlight as new, and says outright that a hard delete would frustrate users wanting to recover an accidental deletion. Readwise directs anyone needing true erasure to delete at the original source.
Can I restore documents that I've previously deleted?
Yes, from Trash, with one catch that matters here. Readwise states deleted documents stay in Trash until you recover them or empty it, and that restoring returns the document to your library along with its highlights and notes. Readwise also states the Trash is device-specific, so a document must be restored from the same device that deleted it.
Sources
- Anonymous MCP
initializeagainsthttps://mcp2.readwise.io/mcp— HTTP 401 withWWW-Authenticate: Bearer resource_metadata="https://mcp2.readwise.io/.well-known/oauth-protected-resource/mcp", our own observation, 2026-08-18. This challenge is what establishes the OAuth posture. A plainGETto the same URL also returns 401, so no unauthenticated tool catalogue is served. · retrieved 2026-08-18 - Readwise's RFC 9728 protected-resource descriptor — — HTTP 200, retrieved 2026-08-18. Source for
authorization_servers: ["https://readwise.io/o/"]andscopes_supported: ["openid", "read", "write"]. The path-less form on the same host returns 404, so only the RFC-insert form is served. · retrieved 2026-08-18 - Authorization-server metadata — and the RFC-insert form — both HTTP 200, retrieved 2026-08-18. Identical documents:
issuer: https://readwise.io/o/, aregistration_endpoint,authorization_code/implicit/refresh_tokengrants,code_challenge_methods_supported: ["S256"], and the same three scopes. The OpenID discovery document at also returns HTTP 200 and lists the same three scopes. · retrieved 2026-08-18 - Deprecated v1 endpoint, our own observation, 2026-08-18.
POST https://mcp.readwise.io/mcpreturns 404;GET https://mcp.readwise.io/ssereturns HTTP 200 withcontent-type: text/event-streamand issues a session endpoint. An anonymousinitializeover that session succeeds without authentication, reportingserverInfo.name: "Readwise MCP (v0.0.2)", version 1.9.4 and protocol2025-03-26. Itstools/listreturns exactly two tools,searchandfetch;prompts/listandresources/listare declared ininitializecapabilities and both return empty arrays. Its descriptor at returns HTTP 200 namingresource: "https://mcp.readwise.io"with noscopes_supportedkey. We ran only listing RPCs and never called a tool. · retrieved 2026-08-18 - Readwise MCP landing page (HTTP 200, retrieved 2026-08-18). Source for the per-tool table of all 22 tools with descriptions, the endpoint as Readwise publishes it, the per-client setup steps, the
mcp-remotebridge command, and six example prompts. · retrieved 2026-08-18 - Readwise MCP Server documentation (HTTP 200, retrieved 2026-08-18). Source for four of the FAQ questions verbatim, the Reader-and-Readwise tool split, the Perplexity Pro requirement, the Codex CLI commands, and the vendor's statement that the previous Readwise-only server is being deprecated. Located via
docs.readwise.io/sitemap.xml; no sub-URL was guessed. · retrieved 2026-08-18 - Usage Examples (HTTP 200, retrieved 2026-08-18). Source for the triage, digest, quiz, recommendation and organise prompts, including Readwise's own "Ask me before making changes" instruction. · retrieved 2026-08-18
- Reader FAQs (HTTP 200, retrieved 2026-08-18). Source for the Trash behaviour, the statement that restoring returns highlights and notes, the device-specific Trash caveat, the bulk Restore all path, and the
Z/ shake-to-undo feature. · retrieved 2026-08-18 - Reviewing highlights FAQ (HTTP 200, retrieved 2026-08-18). Source for "Why can't I permanently delete highlights?", the soft-Discard-versus-hard-Delete design, the sync rationale, the explicit accidental-recovery reason, and the instruction to delete at the original source for true erasure. Also the source for deletion in Readwise not propagating to Kindle, Apple Books or Instapaper. · retrieved 2026-08-18
- Subscription & Billing FAQ (HTTP 200, retrieved 2026-08-18). Source for "Does Readwise offer a free plan?" and its answer, and for the discount categories. · retrieved 2026-08-18
- Privacy & Security FAQ (HTTP 200, retrieved 2026-08-18). Source for the absence of end-to-end encryption, the consumer-software framing, and the OpenAI training opt-out. · retrieved 2026-08-18
- Readwise pricing — and (both HTTP 200, retrieved 2026-08-18). Source for the 30-day free trial, Readwise Lite at $5.59/month billed annually excluding the Reader app, and the full plan at $9.99/month billed annually ($12.99 monthly) explicitly including Reader. · retrieved 2026-08-18
- Readwise API documentation (HTTP 200, retrieved 2026-08-18). Source for the 240-requests-per-minute-per-token rate limit, the lower ceiling on highlight and book listing, and the
429wait-time response. · retrieved 2026-08-18 - Legacy MCP guide — served within
https://docs.readwise.io/llms.txt(HTTP 200, 473 KB, retrieved 2026-08-18). Source for the vendor still publishinghttps://mcp.readwise.io/sseas the ChatGPT MCP Server URL on the same page that announces the deprecation, and for the local@readwise/readwise-mcpstdio server taking anACCESS_TOKEN. · retrieved 2026-08-18 readwiseio/readwise-skills(default branchmaster, pushed 2026-06-19, retrieved 2026-08-18). Reached from a real link onhttps://readwise.io/mcp; the repository URL was not guessed. Source for the third independent tool list, the eleven published skills, the.mcp.jsonnaming the samemcp2endpoint, the 50- document batch ceiling, the 20-calls-per-minute shared rate limit, and the two-product description.reader_personaappears there as a generated file name, not a tool. · retrieved 2026-06-19robots.txtforreadwise.io(HTTP 200, retrieved 2026-08-18).Allow: /with two narrow disallows, neither on a path used here, and noContent-Signaldirective on any of the three axes, so fetching and synthesis are both unrestricted.readwise.io/llms.txtreturns 404;readwise.io/sitemap.xmlreturns 200 and is how the pricing pages were located. · retrieved 2026-08-18robots.txtfordocs.readwise.io(HTTP 200, retrieved 2026-08-18).Allow: /, noContent-Signal, and it names the sitemap. The host serves both anllms.txtand asitemap.xml; the four/tools/*pages that carry this page's best material appear in the sitemap and not inllms.txt. · retrieved 2026-08-18- Anthropic Connectors Directory entry, including the 22 tool names, endpoint and partner tier — , from the committed snapshot dated 2026-08-16. The entry carries no
permissionsfield. Anthropic's directory documentation states that verification "is not a security audit". · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Readwise
- Tools
- 22
- Domain
- mcp2.readwise.io
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.