Atlas / MCP servers / readwiseio / Readwise

ReadwiseSAFE

mcp/readwiseio/readwise-1

Readwise MCP

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
1 1r · 0w · 0d
Transport
stdio
License
MIT
Stars
151
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

This MCP server is deprecated. Please use the new Readwise MCP server instead: [readwise.io/mcp](https://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](https://readwise.io/mcp).

If you also want CLI access and agent skills, see [readwise.io/cli](https://readwise.io/cli).

Legacy Installation (not recommended)

Click to expand old installation instructions

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 r

Read from source at commit 141eaf540864OBSERVED · 2026-10-07
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add readwise-mcp --env ACCESS_TOKEN=${ACCESS_TOKEN} -- npx -y @readwise/[email protected]
claude-desktop
{
  "mcpServers": {
    "readwise-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@readwise/[email protected]"
      ],
      "env": {
        "ACCESS_TOKEN": "${ACCESS_TOKEN}"
      }
    }
  }
}
03

Exposed tools (1)

1 read · 0 write · 0 destructive.

ToolRiskDescription
search_readwise_highlightsread
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
declared (5 observation(s))
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (2)

LOWInventory / provenance · inv.hidden_file · CWE-1104
.pre-commit-config.yaml
.pre-commit-config.yaml
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, axios, axios-retry, zod, @eslint/js, @modelcontextprotocol/inspector, eslint, ts-node
Why it matters. 11 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-07 · audit v0.4.1 · source sha 141eaf540864full audit observations/trust-audit/mcp-server/readwiseio__readwise-1.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-07141eaf540864SAFEB89first audit
06

Questions

What is the Readwise MCP server?

Readwise MCP

What tools does Readwise expose?

1 in total: 1 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Readwise safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Readwise need?

It reads ACCESS_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does Readwise run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as @readwise/readwise-mcp at 0.0.8.

How current is this page?

The grade is for one exact copy of the source (141eaf540864), read on 2026-10-07. The repository is watched and re-audited when it changes.

Advertisement