Readwise MCP HTTP Server
Related Servers
Alternatives to Readwise MCP HTTP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA Model Context Protocol Server that enables language models to access and manipulate Readwise documents and highlights programmatically.49-
- AlicenseNot gradedqualityFmaintenanceTurns your Readwise library into a blazing-fast semantic search engine with a streaming MCP server for LLM clients, supporting vector search, nightly syncs, and deployment on serverless platforms like Vercel.24MIT
- 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

Readwise MCPofficial
AlicenseDqualityDmaintenanceA 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.198 npm151MIT- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server enabling LLMs to search, retrieve, and manage documents through Rememberizer's knowledge management API.36Apache 2.0
- AlicenseAqualityDmaintenanceEnables querying, searching, and managing documents in an Outline instance via the Model Context Protocol.811 npm1MIT
TDQS
Scored across 17 tools
Every tool has a clearly distinct purpose targeting specific resources and actions. For example, create_highlight, get_highlight, update_highlight, and delete_highlight form a complete CRUD set for highlights, while list_highlights, search_highlights, and export_highlights serve different retrieval purposes with no overlap. Tools like save_url and update_progress address unique Reader-specific functions.
All tools follow a consistent verb_noun naming pattern throughout. The pattern is strictly maintained across all 17 tools, with clear action verbs (create, delete, export, get, list, save, search, tag, update) paired with specific nouns (highlight, tag, book, document, progress, url). There are no deviations in style or convention.
The 17 tools are well-scoped for the Readwise domain, covering both the core highlights library and Reader document management. Each tool earns its place by addressing distinct operations like CRUD for highlights/tags, listing/filtering books/documents, saving URLs, and updating reading progress. The count is appropriate for the comprehensive functionality offered.
The tool surface provides complete coverage for the Readwise domain. It includes full CRUD operations for highlights and tags, comprehensive listing and filtering for books, documents, and highlights, specialized search and export capabilities, and key Reader functions like saving URLs and updating progress. No obvious gaps exist—agents can perform all expected workflows without dead ends.