[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Recall API and MCP server: Let your AI agent fill and tidy your Recall. > Recall has had an official MCP server and REST API since April 2026, both on the Free plan. They search, list and read your cards, and nothing else: no saving, no notes, no tags, no deletes (checked 25 Oct 2026). Cotlet runs 13 Recall tools hosted, the reads plus the writes, over MCP for agents and REST for scripts. Read Recall cards, tags and review status with an AI agent or script. Use MCP or REST to build knowledge summaries, Markdown exports and review reports. [MCP setup](https://cotlet.dev/integrations/recall-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/recall-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Recall - Page: https://cotlet.dev/integrations/recall-api-mcp-server ## What can you automate in Recall? - Save a reading list as cards - Tag cards that have no tag - Write a research note from your cards - Send a Friday digest of new saves - Back up cards as Markdown - Clear out cards from an old site ## Does Recall have an MCP server or an API? - Recall's MCP has 4 tools under one scope, kb:read. They cover 4 of our 13 tools in full and the tag list in part. - Recall lists "MCP 2.0 with write access" under "Coming Next" in its release notes of 19 Aug and 12 Sep 2026, with no date. - No Zapier app and no n8n node. A Zapier request on Recall's board has 75 votes since Feb 2024. | What you need | Official MCP | Official API | Cotlet | |---|---|---|---| | Search and read cards | Yes | Yes, in your code | Yes | | Tag list and knowledge base stats | Yes | No endpoint | Yes | | Save links and write notes | No | No | Yes | | Add or remove tags, delete cards | No | No | Yes, deletes after your OK | | Markdown export, connections, review | No | No | Yes | | The route Recall provides | Yes, official | Yes, official | Uses the web app | Checked 25 Oct 2026. Sources: [Recall Docs: API](https://docs.getrecall.ai/developer/api), [Recall Docs: MCP Server](https://docs.getrecall.ai/developer/mcp), [Recall changelog](https://feedback.recall.it/changelog), [Recall feature request: write API](https://feedback.getrecall.ai/feature-requests/p/write-api-access-to-recall) ## How does Cotlet connect to Recall? 1. **Sign in to Recall.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Recall login, and no card is deleted until you approve it. ## Connect Recall to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Enable Recall for agents.** Create a Cotlet account, sign in to Recall in its Cloud Browser and press Enable for agents. 2. **Add the Cotlet address.** Put https://cotlet.dev/mcp/v1 into your agent as an MCP server or connector. 3. **Allow the connection.** Chat apps send you to a Cotlet sign-in. Editors, n8n and scripts take an API key from the console. The shared address, `https://cotlet.dev/mcp/v1`, carries Recall next to your other apps. Recall's own server can stay connected too; give it the reads and Cotlet the writes. Enabled Recall after connecting? Refresh the connector so the new tools appear. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-recall \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-recall": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-recall] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: recall_write ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: recall_read ``` ## How to use the Recall REST API ### Create your Cotlet API key Create a Cotlet API key with access to Recall and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Sign in to Recall in its Cotlet Cloud Browser and enable the app for agents. Use your own Recall account; plan restrictions still apply to paid features. ### Make your first Recall API request cURL: ``` curl "https://cotlet.dev/api/v1/recall/cards/search?q=pricing&mode=focused" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read matching cards and selected text chunks A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "recall", "tool": "search_cards", "result": { "documents": [ { "card_id": "card_8f2a61", "title": "How we price a B2B SaaS", "created_at": "Oct 14, 2026", "source_url": "https://blog.example.com/how-we-price", "chunks": [ { "chunk_id": "chunk_004", "content": "Start with three tiers and anchor on the middle one.", "source": "page 2" } ] } ], "total_cards": 1, "total_chunks": 1 } } ``` Read `result.documents`, where text chunks are grouped by card. Focused search selects fewer cards with more chunks; exhaustive mode selects more cards with preview chunks. Neither search mode exposes cursor pagination. Narrow card lists by date or tag; multiple tag IDs match with OR. `get_card` returns selected chunks, defaulting to 20 with a maximum of 50. Use `focus_query` for a topic and do not treat selected chunks as guaranteed complete card text. ### Recall workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Search cards and read selected card chunks into a research brief that retains source references. | | Make | HTTP > Make a request | Read selected cards and export their Markdown into your chosen knowledge archive. | | Python or Node.js | REST API | Combine knowledge-base stats and review status into a personal learning dashboard. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Recall; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/recall-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Recall API endpoints and MCP tools ### Cards and search Content comes back as text chunks with page numbers or timestamps. The whole-library zip export in Settings is not a tool; Markdown goes one card at a time. - **Search cards** (`search_cards`, read): Find cards by meaning or keyword, optionally within a tag, date range or source. - **List cards** (`list_cards`, read): Cards in your knowledge base, filtered by tag, date or source URL. - **Get card** (`get_card`, read): The content of one card as text chunks, with its source. - **Get knowledge base stats** (`get_knowledge_base_stats`, read): Total cards, date range, top tags and common sources of your knowledge base. - **Export card as Markdown** (`export_card_markdown`, read): The card as a Markdown file, the same as Export to Markdown in the card menu. ### Saving and deleting One link per save. On the Free plan each new card's summary counts toward Recall's 10 a month. A deleted card is gone for good. - **Save URL** (`save_url`, write): Save a web page, YouTube video, podcast or PDF link as a new card. - **Create note** (`create_note`, write): Create a new note card with a title and text. - **Delete card** (`delete_card`, write, asks first): Permanently delete one card. ### Tags and connections A slash nests a tag, as in Business/Pricing. Removing a tag from a card leaves the tag itself in place. - **List tags** (`list_tags`, read): Your tags with the number of cards under each; nested tags appear as Parent/Child. - **Add tags to card** (`add_tags_to_card`, write): Add one or more tags to a card; an unknown tag is created. - **Remove tags from card** (`remove_tags_from_card`, write): Take one or more tags off a card. - **List card connections** (`list_card_connections`, read): The keywords and linked cards in a card's Connections tab. ### Review Reads the Review dashboard only. It does not answer questions or start a quiz. - **Get review status** (`get_review_status`, read): Questions ready for review now, due this week and how many sit in each knowledge stage. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/recall-api-mcp-server#tools ## Who can see my Recall session, and how do I revoke it? - **What we store.** Your signed-in Recall profile, encrypted with AES-256-GCM, in Finland. No password or code. - **What your agent gets.** The 13 Recall tools. Never the cookie or your Recall API keys. - **What the session sees.** Your whole library: cards, notebooks, tags, review questions. - **What no tool touches.** Plan and billing, API keys, chats, personas, full export, tag deletion. - **If Recall asks to sign in.** Recall can mail a one-time code. You type it in, we never do. - **How to cut access.** Disable for agents, reset the browser, or log out of Recall there. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). We have no SOC 2 report or third-party pentest yet. ## Is it against Recall's terms? Account safety > Automated Usage: Using scripts, bots, or automation tools to artificially increase usage. > > [Recall Fair Use Policy, Prohibited Use Cases, read 25 Oct 2026](https://www.recall.it/legal/fair-use-policy) The Terms of Service repeat it as "automation to artificially generate excessive usage" and let Recall suspend accounts that break the policy. The first step the policy names is a talk and a paused subscription, not a ban. One more line matters: Recall may refuse a refund in the first 30 days for "automation". Recall ships its own API and MCP, so an agent in your library is expected; a loop that saves hundreds of links a day to burn summaries is not. We found no public case of a Recall account paused or closed for automation (checked 25 Oct 2026). How we keep your account looking like you: - Your own Recall account, signed in by you - One Cloud Browser with its own IP and cookies, like one more device - One link per save call, no bulk summary runs - Card deletes wait for your OK - If Recall objects, we pause the Recall tools for everyone within 24 h > Recall says it is built for one user and that heavy use across many devices can cause trouble. Keep big imports to its own CSV import (up to 1,000 links) and let the agent tag and file after. ## What happens when Recall changes? - **12 h** between tests of the Recall tools - **$0** for a call to a Recall tool paused for repair Recall ships release notes every two weeks or so (changelog, Jun to Oct 2026), and a moved menu or renamed field is ours to fix. When Recall's own MCP gets write access, the "MCP 2.0" it lists as coming next, we will say here which tools it covers. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Lists the cards.** Filtered by site and date, titles only. 2. **Offers a Markdown copy.** Exports the cards you may want later. 3. **Waits for your OK.** Each delete shows up in your Cotlet console first. 4. **Reports what went.** Deleted titles, kept ones, files saved. | Action | Undo | |---|---| | Save a link | Delete the card; a Free summary already used stays used | | Create a note | Delete the card | | Add tags | Remove them with remove_tags_from_card | | Remove tags | Add them back with add_tags_to_card | | Delete a card | No, Recall has no recycle bin | 1 of 13 tools asks first: delete_card. Saves, notes and tags reach nobody and undo with one call, so they run at once. You can switch the wait off for a scheduled cleanup. > A recycle bin is an open request on Recall's feedback board. Until it ships, export before you delete. MCP call: ``` { "name": "save_url", "arguments": { "url": "https://blog.example.com/pricing-psychology" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/recall/url/save \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"url":"https://blog.example.com/pricing-psychology"}' ``` Tool output: ``` { "card_id": "card_e91d07", "title": "Pricing psychology for SaaS", "source_url": "https://blog.example.com/pricing-psychology", "status": "saved", "tags": [ "Business/Pricing" ] } ``` A cron job or script reaches the same tools over REST at `/api/v1/recall`, with the same key and price. It can sit next to Recall's own read API in one script: Recall for search, Cotlet for saving. The tools table lists the REST path of each tool. ## How much does the Recall MCP server cost? **About $21 a month** for one reader saving about 30 links a month, 3,580 credits. Your Recall plan stays with Recall. | Job | Calls | Credits | |---|---|---| | Save a reading list and tag it, weekly | 17 × 4 | 680 | | Friday digest of new cards | 11 × 4 | 440 | | Research note from saved cards | 7 × 4 | 280 | | Markdown backup of the week, weekly | 11 × 4 | 440 | | Tag cards that have no tag | 18 × 1 | 180 | | Clear out cards from one old site | 6 × 1 | 60 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,580 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on Recall Free, Plus ($10) and Max ($38), yearly prices The month is our example: Recall publishes no typical library size. If your agent only reads, Recall's own MCP does it for free. On Recall Free, 8 saves a week would pass the 10 summaries a month, so Plus fits this reader. Dollars at the $29 pack rate. ## Recall MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [Recall MCP server](https://docs.recall.it/developer/mcp) | Official, free, OAuth in the browser. 4 tools: search, filter, read a card, stats and tags. | Read-only. Writes are announced as "MCP 2.0", no date. | | [Recall API](https://docs.recall.it/developer/api) | Three read endpoints with an sk_ key from Settings. | No tags endpoint, no writes, code you host. | | [mcp-dir/recall-mcp](https://github.com/mcp-dir/recall-mcp) | Hosted wrapper on the official API, MIT, 0 stars, last commit 21 Aug 2026. | The same reads as the official server. | | Zapier, n8n | No Recall app or node. | Nothing to connect. | | Recall extension and CSV import | Saves the page you are on, or up to 1,000 links from a file. | By hand; an agent cannot call them. | For search and reading, Recall's own server is free and is the route Recall backs; use it. To save, write, tag, export or delete from an agent, nothing but Cotlet does it today. Both fit in the same agent, and when Recall ships writes of its own, switch the overlap back to Recall. ## Who runs Cotlet Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), runs Cotlet. It has worked since 2019 and was founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Recall tools to contact@cotlet.dev. ## Recall API and MCP: questions ### Can I use the Recall API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. ### How do I get access? Sign up at https://cotlet.dev, open Recall under Integrations in the console and sign in to Recall in its Cloud Browser. The trial starts with your first app, with no card. ### Does saving a link use my Recall AI summaries? Yes, on the Free plan. Recall writes a concise summary into the Notebook by default, and the Free plan includes 10 AI summaries per month; Plus has unlimited summaries (Recall Pricing). You can switch to storing only the full content in your Recall settings, which Recall documents under Summarize content. ### Does Recall allow an agent to work in my account? Recall's Fair Use Policy and Terms of Service ban scripts, bots or automation that artificially increase usage, for example to run up summaries. Saving, tagging and reading your own cards at a normal pace is not that. Keep bulk loops modest, because Recall can suspend an account for excessive automated usage. ### Can I get back a card my agent deleted? No. Recall has no recycle bin, and a deleted card cannot be recovered (Recall Docs: Deleting Content). That is why delete_card asks for your OK on each call by default. Export the card as Markdown first if you may want it. ### Will Recall's own MCP server get write access? Recall says so. Its release notes of 19 Aug and 12 Sep 2026 list "MCP 2.0 with write access" under "Coming Next", without a date. On 25 Oct 2026 its docs still call the server read-only. ### Does Recall have webhooks? No. Nothing tells an agent that you saved a card. Run the agent on a schedule instead, for example a weekly list_cards from the last 7 days. ### Is the MCP server different from the REST API? Only the way in differs. Both carry the same 13 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Recall? No. Cotlet is independent and not affiliated with Recall or recall.it. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.