F
licenseA
qualityD
maintenanceA Model Context Protocol Server that enables language models to access and manipulate Readwise documents and highlights programmatically.
4
9
-
Readwise MCP
Officialby readwiseio
リードワイズMCP
概要
モデル コンテキスト プロトコル (MCP) は、アプリケーションが大規模言語モデル (LLM) にコンテキストを提供する方法を標準化し、コンテキスト管理と直接的な LLM の相互作用を明確に分離します。
このプロジェクトは、LLM クライアント ( Claudeなど) とReadwise間のブリッジとして機能するように設計されたローカルMCP サーバーです。
Related MCP server: Reader MCP Server
クロードでのインスタレーション
Nodeがインストールされていることを確認してください。
Claude デスクトップ アプリを開きます。
[設定] > [開発者] に移動します。
Edit Configクリックします。次のエントリを
claude_desktop_config.jsonファイルに追加し、ACCESS_TOKEN値をReadwise Access Tokenに置き換えます。
{
"mcpServers": {
"Readwise MCP": {
"command": "npx",
"args": [
"-y",
"@readwise/readwise-mcp"
],
"env": {
"ACCESS_TOKEN": "XXXXXXXXX"
}
}
}
}トラブルシューティング
一般的なトラブルシューティングのガイダンスについては、公式の Model Context Protocol Claude Desktop のトラブルシューティング セクションを参照してください。
以下は、私たちが遭遇し解決した一般的な問題に対する具体的な解決策です。
「MCP サーバー Readwise MCP に接続できませんでした」
この問題が発生する原因として最も可能性が高いのは、npx/Nodeのバージョンが正しく設定されていないことです。nvm nvm使用している場合は、ターミナルでnvm use 18を実行してみてください。それでも解決しない場合は、Nodeの再インストールを検討してください。
Readwiseツールを呼び出す際のエラー
このMCPサーバーをご利用の場合、Claudeとの会話中にMCPエラーが発生する場合があります。このようなエラーが発生した場合は、Claudeの異なるモデル（例：Claude 3.5 HaikuからClaude 3.7 Sonnet）に切り替えてみることをお勧めします。多くの場合、この方法で問題が解決します。
Available Tools
1 toolsearch_readwise_highlightsD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vector_search_term | Yes | ||
| full_text_queries | Yes |
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 tool update
v0.0.2- Changed
search_readwise_highlights1 field changed- added
Input schema / properties / full_text_queries / maxItemsAdded value: +8
1 tool update
v1.0.0- First observed
search_readwise_highlights
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
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Zotero MCP server for Claude and ChatGPT: search, citations, safe writes, PDF passages and pages.
A Model Context Protocol server for Wix AI tools
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Related MCP Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol server that connects MCP-compatible clients like Claude and VS Code to your Readwise Reader library, allowing them to list, retrieve, and update documents in your personal knowledge repository.711MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with access to your Obsidian vault through the Obsidian Local REST API plugin.6,303 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server enabling Claude to read, write, search, and analyse your Obsidian vault with advanced research capabilities.1MIT