home / mcp / readwise mcp server

Readwise MCP Server

Readwise MCP

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "readwiseio-readwise-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@readwise/readwise-mcp"
      ],
      "env": {
        "ACCESS_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

The Readwise MCP Server provides a local bridge that exposes Readwise context to your MCP-enabled LLM clients. It lets you securely supply your Readwise data as context to your preferred model workflows without exposing raw tokens or direct API calls to the models themselves.

How to use

You connect your MCP client to the Readwise MCP Server by configuring the client’s MCP server entry with the provided command. The server uses your Readwise Access Token to authenticate requests and pass Readwise context to the LLM during conversations. Use this to enrich responses with your notes and highlights without leaving your local environment.

How to install

Prerequisites you need to have installed before you begin.

1) Node.js must be installed on your machine. If you are unsure, check by running node -v in your terminal.

2) You will run the MCP server via NPX to fetch the Readwise MCP package on demand. No global installation is required beyond having Node and npm available.

3) Prepare your Readwise Access Token. You’ll place this token into the MCP client configuration so the server can authenticate requests to Readwise.

4) Add the MCP server configuration to your MCP client settings. Use the exact configuration snippet below, replacing YOUR_TOKEN with your Readwise Access Token.

{
  "mcpServers": {
    "Readwise MCP": {
      "command": "npx",
      "args": [
        "-y",
        "@readwise/readwise-mcp"
      ],
      "env": {
        "ACCESS_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

Additional notes

If you encounter issues starting or attaching to the MCP server, verify your Node/NPX setup. A common problem is using an incompatible Node version; if you manage versions with a tool like nvm, run nvm use 18 in your terminal. If you don’t use a version manager, consider reinstalling Node to ensure compatibility.

If you experience occasional MCP errors during conversations, try switching between different MCP-enabled models in your client if that option is available. This can resolve transient compatibility issues with certain model runtimes.