API access to your Recall knowledge base
under review
P
Paul Richards
The API would allow you to access all your Recall data as well as add more content and edit existing content.
Log In
Sankari Nair
Merged in a post:
MCP service
E
Ed Boutros
MCP simplifies issues related to the API and facilitates integration with other systems, such as Claude desktop and Claude. The friction involved in connecting to this data source should be minimized, as no other application currently offers comparable capabilities to collect information from mobile devices and desktops.
C
Chris Holloway
even an mcp so we can interact with it to organise
c
clark.venable
As I explore building an Open Brain [https://github.com/NateBJones-Projects/OB1/tree/main], for example, I'm learning the value of just being able to give access to data I own via an MCP server. Recall tools are fantastic for capturing information and, yes, I can chat with the knowledge base, but and MCP server would allow me to do that in the environment of my choice.
K
Keenan Burke-Pitts
clark.venable Exactly!!
p
phonics-spud-puppy
API preferred will take an MCP or webhook even. i really want access for my coding tools etc.
d
dieter
Don't overcomplicate things. MCP would be enough for most users.
d
dieter
YES, please!! Since the start I wanted a Readwise sync and have requested it several times. The reason for that is, that I can use Readwise highlights in Claude via MCP (and other places). Currently Recall is a silo and we all know what happens to them over time - they die. So either sync Recall summaries to Readwise or even better, give us MCP access. Only then I can really do something with the knowledge here. Otherwise it will go down the silo road.
M
Matthew A. Pigatt
My subscription renews in May. If this isn't moved to planned by then. I will not be renewing.
K
Kent Boehm
I can't emphasise the importance of this enough. it's an existential threat to not have a well documented, highly flexible API for any product that has an even remote chance of containing information someone would want an agent to access.
Great read on this:
E
Ed Boutros
Kent Boehm interesting blog post highlights another revenue stream for Recall. Agents can easily cause high usage of a service, making charging for API access a viable part of the equation. Recall API would be worthwhile if there’s a proper balance between usage and cost; otherwise, it's a hard no.
M
Martijn Rutten
The moment there is an API I'll instantly build a cli for OpenClaw (and similar tools) and MCP server for anything else. Building both a personal knowledge system with OpenClaw and Recall, as well as more dedicated knowledge graphs for a VC I work with is an absolute game changer. I can also see many embedded / branded integration possibilities for Recall once there is an API available.
Sankari Nair
Merged in a post:
Recall & Openclaw
H
Heather M
I'm curious if there's a list of use cases / skills generated to use Recall & Openclaw ... I suspect there's great potential.
Load More
→