Skip to content

Marketing & research integration

Readwise MCP server for Claude, Codex and Cursor

Search your Readwise highlights and Reader documents. Connect the Readwise MCP server to Toolstile once, then choose which of its tools Claude Code, Codex, Cursor and Claude Desktop may use.

Free plan available. Server credentials stay in Toolstile, not in agent configs.

On this page

What your AI apps can do with Readwise

  • Search highlights
  • Read saved documents

Readwise MCP tools

35 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

ToolWhat it does
readwise_search_highlightsHybrid vector and full-text search over your highlights
readwise_list_highlightsList highlights newest first, filtered by book, tag or date range
readwise_create_highlightsCreate one or more highlights, optionally linked to a book or article
readwise_update_highlightUpdate a highlight's text, note, location or tags
readwise_delete_highlightDelete a highlight
readwise_get_daily_reviewGet today's spaced-repetition review set
reader_search_documentsHybrid search across the full text of your Reader library
reader_list_documentsList Reader documents newest first, filtered by location, category or tag
reader_create_documentSave a URL or HTML/text content to Reader
reader_get_document_detailsGet a document's metadata and full Markdown content
reader_move_documentsMove documents between inbox, later, shortlist, archive and feed
reader_bulk_edit_document_metadataEdit title, author, category and other fields on up to 50 documents
reader_export_documentsStart a ZIP export of all documents as Markdown
reader_get_export_documents_statusCheck export progress and get the download URL when done
reader_list_tagsList all tags in your Reader library
reader_add_tags_to_documentAdd tags to a document
reader_remove_tags_from_documentRemove tags from a document
reader_get_document_highlightsGet all highlights on a document
reader_create_highlightCreate a highlight from exact text in a document
reader_add_tags_to_highlightAdd tags to a highlight
reader_remove_tags_from_highlightRemove tags from a highlight
reader_set_highlight_notesSet the note on a highlight
books_list_booksList books, filtered by shelf, ISBN, ASIN or change time
books_create_booksAdd up to 10 books by ISBN, ASIN, catalog id or title and author
books_update_booksUpdate a book's shelf, reading dates, rating, review or page count
books_delete_booksDelete books
books_list_sessionsList reading sessions newest first, filtered by book or time
books_create_sessionsLog completed reading sessions, optionally posting to your feed
books_update_sessionsEdit a reading session's feed caption
books_delete_sessionsDelete reading sessions with their XP and feed posts
books_get_sessions_by_dayGet daily reading totals for a date range
books_get_stats_summaryGet reading totals and goal for a year or all time
books_list_public_tokensList tokens created for your public book feed
books_create_public_tokenCreate a token that lets an external site read your public feed
books_revoke_public_tokenRevoke a public feed token

Suggested access for each AI app

The documentation this list comes from doesn't mark Readwise's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Readwise connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

  1. Connect once. Add Readwise to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
  2. Choose access per app. Give Claude Code every Readwise tool, give Cursor only the read tools, or keep Readwise away from an app entirely.
  3. Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
  4. Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Readwise MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell
claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Readwise in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Readwise endpoint to each app separately. In Claude Code:

Shell
claude mcp add --transport http readwise 'https://mcp2.readwise.io/mcp'

In Cursor's mcp.json:

JSON
{
  "mcpServers": {
    "readwise": {
      "url": "https://mcp2.readwise.io/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Readwise MCP documentation for what your client needs.

Before you connect

A Readwise account. Sign-in uses your Readwise permissions.

Server details

DetailValue
PublisherReadwise
Endpointhttps://mcp2.readwise.io/mcp
AuthenticationBrowser sign-in
CategoriesMarketing & research, Productivity
Tool list35 tools, observed 29 October 2026 (docs)

Readwise MCP documentation