remote -reader

This MCP server exposes remote access to your Readwise Reader library via a secure OAuth-enabled MCP endpoint. It supports typical document and tag management operations such as listing documents with filters, retrieving detailed document data, creating new documents in your Reader library, updating existing ones, deleting documents, and listing tags. The server authenticates users using their Readwise API tokens, securely encrypts tokens at rest, and uses OAuth for token management. Clients interact with the server through the MCP protocol, leveraging the provided methods to manage content and metadata across your Reader collection. The included tools enable full content access (HTML content included by default) and the ability to manage documents, tags, and associated metadata throughout the lifecycle of Readwise Reader entries.

Prerequisites:

• Node.js (LTS) installed on your machine or environment where the MCP server will run
• NPM (comes with Node.js)
• Access to the internet to fetch the MCP package

Installation steps:

1. Ensure Node.js and npm are available: node -v npm -v

2. Install or run the MCP server via npx (as shown in the project README): npm install -g npx npx -y mcp-remote https://remote-mcp-reader-server.julien-marinica.workers.dev/sse

3. If you prefer a local project setup, initialize a project and install the MCP client package: mkdir readwise-reader-mcp cd readwise-reader-mcp npm init -y npm install mcp-remote

4. Run the server using the command configured in your mcp_config (as per the example below). For the default setup: npx -y mcp-remote https://remote-mcp-reader-server.julien-marinica.workers.dev/sse

Note: The exact command may vary depending on how you deploy (Cloudflare Workers, local testing, or a different hosting environment). Refer to your deployment provider’s documentation for running MCP servers in your environment.

Tips and considerations:

• Ensure Readwise API tokens are provided securely by end users; tokens are encrypted before storage.
• The server uses an OAuth 2.0 flow for token management, so client applications should support the standard OAuth redirects and token exchange.
• When filtering documents in listDocuments, leverage location, category, and updatedAfter to minimize payloads and improve performance.
• The tagList endpoint supports pagination; adjust the limit parameter as needed for large tag collections.
• If deploying on Cloudflare Workers, ensure proper KV and Durable Objects configuration for secure token storage and session state.
• Keep the MCP client library (mcp-remote) up to date to leverage security and feature improvements.