Readwise MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCESS_TOKEN | Yes | Your Readwise Access Token, which can be found at https://readwise.io/access_token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_readwise_highlightsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
The single tool name follows a clear verb_noun pattern (search_readwise_highlights). With only one tool, naming consistency is inherently maintained.
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.
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.