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
c
carl.webb
Really pleased to see read access land. Just wanted to add my voice to the write access request with a specific use case that I think sits beyond pure capture.
I use Recall alongside Claude (via MCP) as a thinking and synthesis layer. The read integration is already changing how I work — I can ask Claude to check Recall for prior context before starting new work, which surfaces connections I’d otherwise miss.
The gap right now is the loop back. A lot of my most valuable thinking happens inside Claude conversations — iterative reasoning, synthesising across sources, reaching a conclusion. Without write access, the output of that work either gets copy-pasted manually into Recall (friction that breaks the habit) or lives in chat history that becomes increasingly hard to retrieve over time.
Write access would close the loop: read context in, think it through, write the synthesis back as a new note with appropriate tags. Recall becomes a genuine second brain rather than a one-way archive.
K
Keenan Burke-Pitts
Thanks for releasing the API & MCP with rebrand! But its also very important to have write ability. I need to be able to programmatically pipe saved youtube videos and IG saved posts into my recall account, and write access is required for that.