Skip to main content
Glama
Readwise MCP

Readwise MCP

Official
by readwiseio

Readwise MCP (Deprecated)

This MCP server is deprecated. Please use the new Readwise MCP server instead: readwise.io/mcp

The new server is hosted — no local installation needed. It supports both Readwise and Reader data, and works with Claude Desktop, ChatGPT, Claude Code, Cursor, and any MCP-compatible app.


Migration

Replace your existing claude_desktop_config.json entry with the new server. Setup instructions for all clients are at readwise.io/mcp.

If you also want CLI access and agent skills, see readwise.io/cli.


Related MCP server: Reader MCP Server

Installation in Claude

  1. Please make sure you have Node installed.

  2. Open Claude desktop app.

  3. Navigate to Settings > Developer.

  4. Click Edit Config.

  5. Add the following entry to the claude_desktop_config.json file, replacing ACCESS_TOKEN value with your Readwise Access Token.

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

Troubleshooting

For general troubleshooting guidance, please refer to the official Model Context Protocol Claude Desktop Troubleshooting section.

"Could not attach to MCP server Readwise MCP"

A very likely reason for this to happen is that you have an incorrect npx/Node version set up. If you're using nvm, try running nvm use 18 in your terminal. If not, consider reinstalling Node.

Errors when calling Readwise tools

When using this MCP server, you may occasionally encounter MCP errors during your conversations with Claude. If you experience such errors, we recommend trying to switch between different Claude models (e.g., from Claude 3.5 Haiku to Claude 3.7 Sonnet) as this often resolves the issue.

Available Tools

1 tool
search_readwise_highlightsD

Inputs: vector_search_term (required), full_text_queries (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusing it with other tools. Its purpose is clearly identifiable from its name despite the missing description.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (search_readwise_highlights). With only one tool, naming consistency is inherently maintained.

    Tool Count2/5

    A single tool is far too limited for a Readwise MCP server, which would be expected to support listing, retrieving, tagging, or managing highlights in addition to searching.

    Completeness1/5

    The surface is severely incomplete: only a search operation is exposed, with no way to retrieve specific highlights, browse by tag, or perform any other meaningful Readwise actions. This creates a dead-end workflow for most use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers