MCP
Let an AI assistant read and write your own notebases, notes, card templates and review history over a remote MCP connection.
Read Frog runs a remote MCP server. Connect an AI assistant to it — ChatGPT, Claude, Codex, Claude Code, or any other MCP client — and that assistant can work directly with the study side of your account: your notebases, their fields, the notes in them, the card templates that turn notes into cards, and your review history.
It is your own data, reached through your own account. A note the assistant creates appears in your notebase straight away, and a rating it records changes the same FSRS schedule the review screen uses.
What it can reach
Five areas, each of which you grant separately and at the level you choose:
| Area | What it covers |
|---|---|
| Account information | Your name, email address and profile picture. Never note content. |
| Notebases and fields | Your notebases and the fields that define their structure. |
| Note content | The field values that make up each note. |
| Card templates | The front and back layout used to generate cards. |
| Reviews and learning history | Review records, scheduling state and daily limits. |
Connect an assistant covers how permissions work in detail. Reference lists all 29 tools and what each one needs.
What it cannot reach
MCP is entirely about the study side. It has nothing to do with translation: it cannot translate a page, and it cannot see your extension settings, your providers, your glossaries, your prompts or your site rules. None of those live in your account the way notes do.
It also does not fetch anything from the web. There is no tool that opens a URL or parses a PDF — when a recipe starts from an article or a document, the assistant reads that source with its own capabilities and Read Frog only saves the result. If your assistant cannot reach a source, paste the text into the conversation instead.
What you need
- A Read Frog account on the Ultra plan. See pricing for what each plan includes.
- An AI client that supports remote MCP servers over Streamable HTTP with OAuth 2.1 authorization.
Every client connects to the same address:
https://api.readfrog.app/api/mcpYou never hand the assistant your password, and there is no access token to copy by hand. Authorization happens on Read Frog's own consent page, and you can revoke it there at any time.
How this relates to the extension
The browser extension is the reading side of Read Frog: it translates pages, reads text aloud, and saves words and explanations you meet while reading. Those saves land in a notebase, and from there they become cards you review.
MCP opens a second door into that same workspace — one an assistant can walk through. It does not replace the extension, and it changes nothing about how translation works. If what you want is to save a word from a page you are reading, the extension's custom actions already do that without any assistant involved.
Start by granting read-only permissions and asking the assistant questions about your notes. Once you trust what it does with them, raise the permissions it needs for the recipes you actually want.
Where to go next
- Connect an assistant — the connection flow, the five permission groups, and how to revoke a connection.
- Recipes — things worth asking for, with the prompt to type and the permission each one needs.
- Tool reference — every tool, grouped by permission, for deciding what to grant.