Connect your Readwise Reader library to LLMs.
Connect your Readwise Reader library to LLMs. Exposed over MCP by the reader mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
This repository also includes a standalone skill for interacting with Readwise Reader API directly via HTTP requests. The skill provides knowledge and examples for using the Reader API without requiring an MCP server.
A Model Context Protocol (MCP) server that seamlessly integrates with your Readwise Reader library. This server enables MCP-compatible clients like Claude and VS Code to interact with your Reader library, providing capabilities for document listing, retrieval, and updates. It serves as a bridge between MCP clients and your personal knowledge repository in Readwise Reader.
Everything the assistant can do here goes through one of these:
list_documents — List documents from Reader with flexible filtering and paginationInput — **Returns — **Tools — The Tools tool exposed by this serverFeatures — The Features tool exposed by this serverInstallation — For more information on installing and using skills, see the Vercel Labs Skills documentationUsage — Once installed, the skill will be automatically triggered when you ask about Readwise Reader, saving articles, or managing your reading listskills on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: READWISE_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Reader's toolset — list_documents, Input, Returns and 4 more — is a fair guide to whether it matches your workflow. It is maintained by xinthink; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| list_documents | List documents from Reader with flexible filtering and pagination. |
| Input | ** |
| Returns | ** |
| Tools | The Tools tool exposed by this server. |
| Features | The Features tool exposed by this server. |
| Installation | For more information on installing and using skills, see the [Vercel Labs Skills documentation](https://github.com/vercel-labs/skills). |
| Usage | Once installed, the skill will be automatically triggered when you ask about Readwise Reader, saving articles, or managing your reading list. |
{
"mcpServers": {
"reader": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/your/reader/server",
"run",
"main.py"
],
"env": {
"READWISE_ACCESS_TOKEN": "your-token-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| READWISE_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.