Readwise MCPofficial
A
licenseD
qualityD
maintenanceA local Model Context Protocol server that connects LLM clients (like Claude) to Readwise, enabling AI assistants to access and interact with your saved reading content.
1
98 npm
151
MIT
Kiseki-Labs-Readwise-MCP
Related Servers
Alternatives to Kiseki-Labs-Readwise-MCP
No user-submitted related servers found.
Related 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
- AlicenseAqualityBmaintenanceEnables searching and accessing Readwise highlights and documents through HTTP endpoints using the Model Context Protocol. Provides vector and full-text search capabilities with streaming responses for retrieving reading highlights and notes.171MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to read, write, search, and organize Dynalist documents programmatically.MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to extract and use content from unstructured documents across a wide variety of file formats.111-
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server enabling LLMs to search, retrieve, and manage documents through Rememberizer's knowledge management API.36Apache 2.0
TDQS
A3.7/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: finding documents by names, getting highlights by document IDs, getting highlights by filters, and listing documents by filters. There is no overlap in functionality, and the descriptions make it easy to differentiate between document-focused and highlight-focused operations.
Naming Consistency4/5
The naming follows a consistent verb_noun_by_filters pattern for three tools (find_readwise_documents_by_names, get_readwise_highlights_by_document_ids, get_readwise_highlights_by_filters, list_readwise_documents_by_filters), with 'find' and 'list' being slightly different verbs but still semantically clear. The structure is predictable and readable throughout.
Tool Count4/5
With 4 tools, the count is reasonable for a Readwise integration, covering core operations like retrieving documents and highlights. It might be slightly thin for a full-featured server, but it effectively handles key use cases without being overwhelming.
Completeness3/5
The toolset covers reading operations (finding and listing documents, retrieving highlights) but lacks create, update, or delete capabilities, which are common in CRUD workflows for a service like Readwise. This creates notable gaps that could limit agent functionality for managing documents or highlights.
Maintenance
ActivityInactive
ResponsivenessNo issues