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
C
Chris Holloway
even an mcp so we can interact with it to organise
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.
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.
Sankari Nair
Merging this one in the API request as we would need an API to set this up!
Sankari Nair
Merged in a post:
Official MCP Server for Bidirectional AI Agent Integration (Claude Code, Cursor, Windsurf)
l
lars.viding007
### Description
With the rapid adoption of AI coding agents (Claude Code, Cursor, Windsurf, Codex), there's a growing need for Recall to provide a
Model Context Protocol (MCP) server
that enables bidirectional integration between Recall's knowledge base and AI agent workflows.Why MCP specifically (not just a REST API):
MCP is becoming the standard protocol for connecting AI agents to external data sources. Claude Desktop, Claude Code, Cursor, Windsurf, and other tools all support MCP natively. An MCP server would give Recall instant compatibility with the entire ecosystem — no custom integrations needed per tool.
Proposed MCP tools:
| Tool | Description |
|------|-------------|
|
recall_search
| Semantic search across the user's knowledge base with filters (tags, source type, date range) ||
recall_get_card
| Retrieve full card content by ID ||
recall_create_card
| Create a new card from agent-generated content (research results, summaries, decisions) ||
recall_tag
| Add/remove tags on existing cards ||
recall_list_recent
| List recently added or modified cards |Use cases this enables:
- Knowledge-grounded agents— An agent researching a topic checks the user's Recall KB first, giving priority to curated sources over raw web results
- Automated knowledge capture— After a research session, the agent saves key findings back to Recall with appropriate tags
- Cross-session continuity— Different agent instances (terminal, IDE, desktop) all share the same knowledge base
- Bulk organization— Ask an agent to re-tag, merge, or reorganize cards based on semantic relationships
Implementation reference:
A simple remote MCP server config would look like:
```json
{
"mcpServers": {
"recall": {
"url": "https://api.getrecall.ai/mcp",
"headers": {
"Authorization": "Bearer <RECALL_API_KEY>"
}
}
}
}
```
This pattern is already established by tools like Todoist, Asana, and Linear who ship official MCP servers. Recall's knowledge ingestion and AI summarization is best-in-class — adding MCP access would make it the central knowledge hub for AI-powered workflows rather than just a standalone app.
Competitive context:
Users are already discussing migrating to Obsidian + CLI + MCP setups because they offer programmatic access. An official MCP server would eliminate this migration pressure and position Recall as the knowledge layer for agentic AI workflows.---
l
lars.viding007
+1 from an Azure architect using Claude Code agents daily.
My workflow: I use Recall to ingest YouTube videos, articles, and technical docs into a curated knowledge base. It's fantastic for that. But my actual
work
happens through Claude Code agents running in terminals, VS Code, and Claude Desktop — each with different contexts and tasks.Right now there's a gap: my agents can search the web, read local files, and query APIs — but they can't tap into the curated knowledge I've spent time building in Recall. That means I end up manually copy-pasting context from Recall into prompts, which defeats the purpose of having AI agents.
What I need specifically:
- Read access via MCP or REST API— so my Claude Code agents can query my Recall KB as a first-pass knowledge source before falling back to web search
- Write access— so agents can push research results, summaries, and architectural decisions back into Recall for future reference
- Semantic search endpoint— not just keyword matching, but the same smart retrieval Recall's built-in chat uses
The competitive pressure is real. Tools like Obsidian + CLI + MCP are becoming viable alternatives precisely because they offer programmatic access. Recall's content ingestion and summarization is best-in-class, but without API/MCP access, power users running agentic workflows will eventually migrate to tools that integrate into their pipelines.
Happy to beta test if you need early adopters for this.
---
E
Ed Boutros
lars.viding007 I’m already using Obsidian for much of my work and would prefer to use Recall specialization, but as long as the system remains isolated, it’s a problem. Information cannot be isolated anymore.
Load More
→