Persistent Memory for Cursor IDE
Cursor knows your codebase but forgets everything between conversations. ContextForge gives Cursor persistent memory via MCP — your decisions, patterns, and team knowledge survive across every session.
.cursorrules is not enough
Cursor indexes your codebase, but every conversation starts blank. The race condition you debugged last week, the API decision your team made — all gone.
Cursor with growing knowledge
Build a searchable knowledge base that grows over time. Cursor uses MCP to retrieve exactly what it needs when it needs it. No more re-explaining.
Setup in under 3 minutes
Get your API key
Sign up at contextforge.dev (free tier available) and copy your API key from the dashboard.
Add ContextForge to Cursor
Create or edit .cursor/mcp.json in your project root:
{
"mcpServers": {
"contextforge": {
"command": "npx",
"args": ["-y", "contextforge-mcp"],
"env": {
"CONTEXTFORGE_API_KEY": "your-api-key"
}
}
}
}Restart Cursor and use it
Open Cursor chat and ask it to save context. The memory persists across sessions and devices.
What you can do
Beyond .cursorrules
.cursorrules is static text. ContextForge is dynamic — searchable by meaning, organized by project, shared with your team.
Semantic search across projects
Cursor can pull knowledge from any of your projects. Working on a new feature? It can find related decisions from old ones.
Multi-device sync
Your knowledge follows you. Save context on your laptop, recall it on your desktop. Cursor sees the same memory from any machine.
Team collaboration
Pro and Premium plans let your whole team share knowledge. New hires onboard faster because Cursor already knows your codebase patterns.
Common questions
How is this different from .cursorrules?
.cursorrules is a static instruction file. ContextForge is a searchable knowledge base. Use both — .cursorrules for "always use TypeScript", ContextForge for "we tried X approach but switched to Y because of Z".
Does Cursor need to be restarted to load the MCP server?
Yes. After adding ContextForge to your .cursor/mcp.json, restart Cursor for the changes to take effect. After that, the connection is automatic.
Can I use ContextForge with Cursor and Claude Code simultaneously?
Absolutely. The same memory is accessible from any tool that supports MCP. Save in Cursor, recall in Claude Code, share with your team in Copilot — one knowledge base, every tool.
Ready to give Cursor memory?
Free tier available. Setup takes under 3 minutes.