Documentation
API reference, integration guides, and tutorials for building with Adaptive Recall.
MCP (Model Context Protocol)
MCP is an open protocol that lets AI tools connect to external services. Adaptive Recall runs as an MCP server that any compatible client can connect to directly.
After you sign up, your dashboard shows your connection URL and API key, with the setup command for each app ready to copy. The connection URL is https://s1.adaptiverecall.com/mcp, and the dashboard always shows the exact one for your account.
Configuration
Most MCP apps, including Cursor, read a JSON settings file. Add Adaptive Recall to it:
{
"mcpServers": {
"adaptive-recall": {
"url": "https://s1.adaptiverecall.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Replace YOUR_API_KEY with the API key from your dashboard. For Cursor the file is ~/.cursor/mcp.json.
Available Tools
Once connected, your AI assistant has access to eight tools:
Claude.ai and Claude Desktop
The Claude apps connect through a custom connector and sign you in with your Adaptive Recall account, so there is no API key to paste.
- Open Settings, then Connectors, and choose Add custom connector.
- Name it Adaptive Recall and paste
https://s1.adaptiverecall.com/mcpas the URL. - Click Connect and sign in with your Adaptive Recall account when the login page opens.
A connector added on claude.ai is also available in Claude Desktop and the Claude mobile apps on the same account.
HTTPS / REST API
Every tool available through MCP is also available as an HTTP endpoint. Use this when your platform does not support MCP or when you need direct API access from your own code.
Base URL
https://s1.adaptiverecall.com/v1/
All requests require a Bearer token in the Authorization header:
Authorization: Bearer YOUR_API_KEY
Endpoints
| Method | Endpoint | Description |
|---|---|---|
| POST | /v1/store | Store a new memory |
| POST | /v1/recall | Search memories or retrieve by ID |
| POST | /v1/update | Update an existing memory |
| POST | /v1/forget | Remove a memory by ID or query match |
| POST | /v1/status | System health and statistics |
| POST | /v1/graph | Explore entity connections |
| POST | /v1/snapshot | Summary of stored memories by type |
| POST | /v1/feedback | Send feedback to the developers |
Memory Types
When storing memories, you can assign a type that affects lifecycle behavior and retrieval scoring:
general_knowledge- facts, observations, reference informationuser_knowledge- information about people and their preferencescallable_scripts- tool and script referenceswork_project- project tracking, tasks, deadlinescross_reference- pointers to external information and resourceslearned_procedure- multi-step workflows and procedures
Rate Limits
Rate limits are per account and vary by plan. Check the pricing page for details. When you exceed your limit, the API returns HTTP 429.
Claude Code (Anthropic)
Claude Code supports MCP servers natively. Add Adaptive Recall once and Claude will have persistent memory across sessions.
Quick Setup
Run this in your terminal. The --scope user option makes Adaptive Recall available in every project:
claude mcp add --transport http --scope user adaptive-recall https://s1.adaptiverecall.com/mcp --header "Authorization: Bearer YOUR_API_KEY"
Your dashboard shows this command with your API key already filled in. Run claude mcp list afterward to confirm the connection.
Project Configuration
To share the setup with a team through the repository instead, add this to the project's .mcp.json file:
{
"mcpServers": {
"adaptive-recall": {
"type": "http",
"url": "https://s1.adaptiverecall.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Quick Start
Once configured, Claude can store and recall memories naturally in conversation:
- "Remember that our API rate limit is 500 req/min on the production server."
- "What do you know about our deployment process?"
- "Forget the old database credentials I stored last week."
- "Give me a status report on my memory system."
Claude will call the appropriate tool (store, recall, forget, status) automatically based on context.
Codex / GPTs (OpenAI)
Codex CLI
OpenAI Codex supports MCP servers natively. Add Adaptive Recall to ~/.codex/config.toml and it will have persistent memory across sessions, the same way it works with Claude Code:
[mcp_servers.adaptive-recall]
url = "https://s1.adaptiverecall.com/mcp"
bearer_token_env_var = "ADAPTIVE_RECALL_API_KEY"
Codex reads the key from the environment variable named there, so set ADAPTIVE_RECALL_API_KEY to your API key in your shell profile before starting Codex.
Custom GPTs
Custom GPTs connect to Adaptive Recall through Actions. In the GPT editor, go to Configure, then Actions, and create a new action. Import the schema from your server's OpenAPI endpoint:
https://s1.adaptiverecall.com/openapi.json
Set the authentication type to "API Key" with the Auth Type set to "Bearer" and paste your API key. The GPT will automatically discover all available tools from the schema.
Gemini CLI (Google)
Google's Gemini CLI supports MCP servers natively. Add Adaptive Recall to your Gemini settings and it will have persistent memory across sessions.
Configuration
Add to your ~/.gemini/settings.json file (or .gemini/settings.json in your project directory):
{
"mcpServers": {
"adaptive-recall": {
"httpUrl": "https://s1.adaptiverecall.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Gemini CLI uses httpUrl for streamable HTTP MCP servers. Replace YOUR_API_KEY with the API key from your dashboard.
Other Platforms
Any platform that can make HTTP requests can use Adaptive Recall. The REST API accepts and returns JSON, authenticated with a Bearer token. See the HTTPS / REST API section above for full endpoint documentation.
If your platform supports MCP, use the MCP configuration for the best integration experience.