## Readwise integration

Readwise is a read-it-later and highlight management tool that syncs highlights, notes, and saved articles from Readwise Reader and other sources.

Agen.co connects to Readwise through Readwise's own hosted MCP server as an **Official** connector. Each user authorizes with their own Readwise account, and agents can search, read, and manage that user's highlights and Reader documents.

Prerequisites
- A Readwise account. No app needs to be registered with Readwise — the MCP server registers Agen.co as a client automatically, so there is no Client ID or Client Secret to copy.


### Connect Readwise in Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. In the **Select connector** drawer, search for `Readwise` and select it. The **Add Readwise** panel opens.
3. Fill in the field:
| Field | Required | Description |
|  --- | --- | --- |
| **Instance Slug** | Yes | Prefixes each imported tool as `slug__tool`, so several instances of the connector can coexist. Prefilled with `readwise`. Use lowercase kebab-case. You can change it later from the connector's settings. |
4. Click **Connect**. Readwise opens in a new tab, and the panel shows **Waiting for authorization — complete it in the opened tab…**
5. Sign in to Readwise if prompted, then approve the requested access on Readwise's consent screen.
6. Back in Agen.co, the panel switches to **Select the tools to import from Readwise.** Every tool is toggled on; turn off any you don't want to import, then click **Add**.


The connector is created and its tools imported only when you click **Add**. If you close the panel before that, nothing is saved, even though the Readwise tab reported success.

### Authorize each user

Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Readwise tool, the call returns an authorization link instead of a result. The user opens the link, signs in to Readwise, and approves access. After that, the user's tool calls run with their own Readwise account, reaching that account's own highlights and Reader documents.

Once connected, Readwise appears under **My connectors** with tools spanning:

| Area | What it covers |
|  --- | --- |
| **Reader documents** | Listing, searching, and exporting documents, reading their details, metadata, and highlights, checking export status, and creating new documents |
| **Document organization** | Moving documents between locations such as later, shortlist, and archive, and bulk-editing document metadata |
| **Tags** | Listing tags, and adding or removing tags on documents and highlights |
| **Highlights** | Listing, searching, creating, updating, and deleting highlights, and adding notes to highlights |
| **Daily Review** | Reading the day's Daily Review content |


Search combines full-text matching with semantic search, so results can surface relevant content even when a query doesn't use the exact words from the original highlight or document.

Enabling the Readwise connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose.

### Additional resources

- [Readwise MCP server documentation](https://docs.readwise.io/tools/mcp)