Skip to main content
Glama
enesjakozh
readwiseio

Readwise MCP

Official
by readwiseio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Readwise MCP

预先提交

概述

模型上下文协议 (MCP)标准化了应用程序向大型语言模型 (LLM) 提供上下文的方式，确保上下文管理和直接 LLM 交互之间的明确分离。

该项目是一个本地MCP 服务器，旨在充当 LLM 客户端（如Claude ）和Readwise之间的桥梁。

观看演示！

Related MCP server: Reader MCP Server

克劳德的装置

  1. 请确保您已安装Node 。

  2. 打开 Claude 桌面应用程序。

  3. 导航至“设置”>“开发者”。

  4. 单击Edit Config 。

  5. 将以下条目添加到claude_desktop_config.json文件，用您的Readwise Access Token替换ACCESS_TOKEN值。

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

故障排除

有关一般故障排除指导，请参阅官方模型上下文协议 Claude 桌面故障排除部分。

以下是我们遇到并解决的常见问题的具体解决方案。

“无法连接到 MCP 服务器 Readwise MCP”

发生这种情况很可能是因为您设置的 npx/Node 版本不正确。如果您使用的是nvm ，请尝试在终端中运行nvm use 18 。如果不行，请考虑重新安装 Node。

调用 Readwise 工具时出错

使用此 MCP 服务器时，您在与 Claude 对话时可能会偶尔遇到 MCP 错误。如果您遇到此类错误，我们建议您尝试切换不同的 Claude 模型（例如，从 Claude 3.5 Haiku 切换到 Claude 3.7 Sonnet），这通常可以解决问题。

Available Tools

1 tool
search_readwise_highlightsD
ParametersJSON Schema
NameRequiredDescriptionDefault
vector_search_termYes
full_text_queriesYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev0.0.2
    • Changedsearch_readwise_highlights1 field changed
      • addedInput schema / properties / full_text_queries / maxItems
        Added value: +8
  2. 1 tool updatev1.0.0
    • First observedsearch_readwise_highlights
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

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 issues

Resources

Related MCP Connectors

Related MCP Servers