Cursor
Integrate Rekall with Cursor to bring persistent memory to your AI-assisted coding sessions. Project-aware memory means Cursor remembers your codebase patterns, decisions, and preferences across sessions.
Overview
Cursor supports MCP servers natively, which means Rekall integrates seamlessly into your coding workflow. Once configured, Cursor's AI assistant can store and recall memories about your projects, coding decisions, architecture patterns, and team conventions.
Project-Aware
Memories are scoped to your project so each codebase has its own context.
Persistent
Decisions, patterns, and preferences persist across Cursor sessions.
Team Shared
Share memories via hives so the whole team benefits from collective knowledge.
Installation
First, install the Rekall MCP server globally:
npm install -g @rekall/mcp-server
Optionally, install the Rekall Cursor plugin for enhanced features like inline memory hints and project-aware context:
# Install via Cursor Extensions# 1. Open Cursor# 2. Go to Extensions (Cmd+Shift+X / Ctrl+Shift+X)# 3. Search for "Rekall"# 4. Click Install
MCP Configuration
Configure the MCP server in Cursor's settings. Open Cursor Settings and navigate to the MCP section, or edit the configuration file directly:
1. Open Cursor Settings (Cmd+, / Ctrl+,)2. Navigate to "Features" > "MCP Servers"3. Click "Add Server"4. Enter the following:- Name: rekall- Command: rekall-mcp- Args: --stdio5. Add environment variable:- REKALL_API_KEY: your-api-key-here6. Click Save
Per-project configuration
Set REKALL_CONTEXT to your project name so memories are automatically scoped. You can also use a .rekallrc file in your project root for per-project settings.
Project-Aware Memory
Rekall automatically scopes memories to your current project when configured with a project context. This means memories from one project do not bleed into another, keeping each codebase's context clean and relevant.
// .rekallrc in your project root{"context": "my-saas-app","agentId": "cursor","autoCapture": {"decisions": true,"patterns": true,"errors": false},"hive": "frontend-team"}
When autoCapture is enabled, Cursor automatically stores significant coding decisions and detected patterns as memories. This happens in the background without interrupting your workflow.
Using Memory in Cursor
Rekall memory is accessible in all of Cursor's AI interaction modes:
Memory in Chat
In Cursor's Chat panel, the AI assistant automatically has access to Rekall tools. You can ask it to remember or recall information naturally:
You: "Remember that we use Zod for all API input validation in this project."Cursor: "I've stored that as a semantic memory: your project uses Zod forAPI input validation. I'll keep this in mind for future code suggestions."---You: "What validation library do we use?"Cursor: "Based on my memory, this project uses Zod for all API inputvalidation."
Memory in Composer
When using Cursor Composer for multi-file edits, the AI can recall project conventions and patterns to generate consistent code:
You: "Create a new API endpoint for user preferences."Cursor: [Recalls project patterns from memory]"Based on your project conventions, I'll create the endpoint using:- Express with TypeScript- Zod for input validation- The repository pattern you use for data access- Error handling consistent with your existing endpoints"[Generates code matching your established patterns]
Inline Memory
With the Rekall Cursor plugin installed, you get inline memory hints. When editing code in areas where relevant memories exist, a subtle indicator appears in the gutter showing available context:
Inline hints
Hover over the memory indicator to see relevant memories for the current code section. This includes past decisions, known issues, and team conventions related to the function or module you are editing.
Configuration Options
| Option | Default | Description |
|---|---|---|
context | auto | Memory context (auto-detects from git remote or folder name) |
agentId | cursor | Agent identity for memory ownership |
autoCapture.decisions | true | Automatically capture coding decisions as memories |
autoCapture.patterns | true | Detect and store code patterns and conventions |
hive | none | Default hive for sharing team memories |
inlineHints | true | Show inline memory hints in the editor gutter |
