Write API access to Recall

Sankari Nair
The ability to make changes in your Recall knowledge base via an API, such that you could add content and adjust content.
Log In
s
sbrown
I would love this! My Chief of Staff agent runs in Claude, so being able to write as well as read would be phenomenal!
b
barry_wallis
ABSOLUTELY!! I'm using Grok Bot to manage several repos in Recall. Not being able to curate and manage these with my Grok Bot is seriously annoying and is now leading me to look at other alternatives as the growing size and scope of these repos grow the current limitations in Recall not having write access through the MCP or API is becoming unsustainably restrictive for me and time consuming for me as I have to manually adjust and curate. Which my Bot could do in seconds!
All other major SAAS and platforms with MCP's allow write access, I don't understand why Recall would restrict the MOST important ability??
Nicole Howitt has said that it is on their engineering road map, not sure why it wasn't included from day 1, but how long and I would like to be part of the testing program if I haven't already jumped ship.
R
Rory Russell
+1. I use Recall through the MCP in Claude Code and it's great for reading, but adding a URL still means going through the web app. Even one write tool, "add this URL with a detailed summary", would make Recall the default capture step in my agent workflows. Editing tags would be a nice second.
A
Anderson Curry
Readability is critical for our process using Recall. Looking forward to the release and notification.
J
John Esser
+1. I use Recall mostly through my own tools and AI agents, and the API is what holds me back:
- Add items through the API. CSV import covers bulk adds, but I need to add a single item (or a few) directly. Today, saving from my own tools means driving the website.
- Full content. A card comes back as at most 50 chunks, never the full text or the full YouTube transcript, so I can't get my own library back out in full.
One request about how it ships: please put write access and full-content retrieval in the REST API (ideally with a small official CLI), not only in MCP. MCP servers load their whole tool schema into every request, which is bloated and inefficient on tokens, and they add another server to run and keep connected. A CLI costs nothing until it is called.
s
sbrown
+1 adding on to this: Write and full content belong in REST because REST is the base layer that MCP, a CLI, and scripts all sit on. A CLI makes Recall usable from cron and shell without an AI client. Keep MCP for chat clients.

Sankari Nair
Merged in a post:
More tools for MCP
C
Cristian Rojas
Hey team, I've been a user for a while, but right now it's hard to justify my subscription unless I can get more robust MCP tooling to do anything I need through agents.

Sankari Nair
Merged in a post:
two way integration with AI models
C
Chris Smith
right now Claude can only read access my recall library, it would be great to give it write access too

Sankari Nair
Merged in a post:
Mcp that alters and produces content
R
Raphael Pinho
It is possible that the mcp is not only for reading, but also for production and editing to actually be a second living brain.
s
schroell
If you would write your requests in English, you would probably have more success in upvoting from other users
r
recall
I am now in one month testing phase to decide whether to switch to Recall or not - the write API is a soft breaking point. I have some some Make workflows that are storing info into my current PKM and the unability to do such things in Recall do play against it. All I need is actually to create a new card (e. g. when the workflow decides to store an e-mail for future reference).
Load More
→