Quick Start
Sign up
Create an account using GitHub OAuth. It takes 30 seconds.
Install Recall
After signup, you'll get a personalized install command. Run it in your terminal:
bashnpx recall-mcp-setup@latest YOUR_TOKEN
This automatically configures Claude Code with Recall and preserves your existing MCP servers.
Restart Claude Code
Restart Claude Code to load Recall. You'll see Recall tools available in your session.
Prefer manual setup? Add this to ~/.claude/mcp.json:
json{ "mcpServers": { "recall": { "type": "stdio", "command": "npx", "args": ["-y", "recall-mcp-v3"], "env": { "RECALL_API_TOKEN": "your-api-token-here", "RECALL_API_URL": "https://api-v3.recall.team" } } } }
User Guides
Everything you need to get the most out of Recall. Click each guide to expand.
In 5 minutes, your AI assistant will remember everything you build.
Steps:
- Sign up at recall.team with GitHub
- Copy your install command from Settings
- Run the command in your system terminal (not inside Claude Code)
- Restart Claude Code - this is required
- Verify by typing
/mcp- you should see "recall" - Save your first session by saying "Save this session to Recall"
The Magic Moment
Start a new session and ask: "What did I work on last?" Claude will tell you about your previous session. That's team memory working.
Quick Reference
| Load context | Happens automatically at session start |
| Ask about history | "What did we work on recently?" |
| Save your work | "Save this session to Recall" |
| Check connection | Type /mcp |
How It Works
Session Start
When you start a Claude Code session, Recall automatically loads your team's context: recent decisions, mistakes to avoid, and relevant history.
During Session
Work normally with Claude Code. Recall captures key decisions and context in the background without interrupting your flow.
Session End
When you save your session, Recall summarizes what was accomplished and makes it available to your team.
Available MCP Tools
recall_get_context
Load your team's context at session start. Includes recent sessions, decisions, mistakes to avoid, and project overview.
recall_get_origin
Get the project overview - tech stack, structure, key files. Used when Claude needs to understand what the project is.
recall_get_history
Get detailed session history. Claude uses this when you ask about past work or need more context.
recall_repo_activity
See what collaborators across your accessible repos have been working on. Ask "What has [name] been working on?"
recall_save_session
Save a summary of your session. Include what was accomplished, decisions made, and blockers.
recall_log_decision
Log an important decision during your session. Quick way to capture why something was done.
recall_add_repo
Add a new repository to Recall. Used when you open a repo that isn't tracked yet.
Security
Data Protection
Your source code never leaves your machine. We receive a preprocessed transcript, summarize it with AI, encrypt the summary, then delete the transcript. Only encrypted summaries are stored.
- Source code never uploaded - only conversation summaries
- AES-256-GCM encryption for all stored summaries
- Team-specific encryption keys
- Raw transcripts deleted immediately after summarization
Learn more about our security practices on the Security page.