mcp-memories
Provides tools for storing and searching team knowledge base sessions in MongoDB Atlas, including vector search for semantic retrieval of past build sessions.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-memoriessearch for past build sessions about JWT authentication in Node.js"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-memories
An MCP server that captures code build sessions and publishes them to a shared team knowledge base, making past work discoverable via semantic search.
What it does:
Auto-captures every agent session via IDE hooks (Cursor, Claude Code)
When you call
complete_session, it summarizes with Grove AI and embeds with Voyagevoyage-code-4Team members search with natural language — vector search + Voyage reranking returns the most relevant past builds
Setup
1. Install and build
npm install
npm run build2. Configure environment
cp .env.example .env
# Fill in MONGODB_URI, MDB_GROVE_API_KEY, GROVE_BASE_URL, VOYAGE_API_KEY, MEMORIES_AUTHOR3. Register the MCP server
Add to your IDE's MCP config (e.g. ~/.cursor/mcp.json or Claude Desktop config.json):
{
"mcpServers": {
"mcp-memories": {
"command": "node",
"args": ["/path/to/mcp-memories/dist/index.js"],
"env": {
"MONGODB_URI": "mongodb+srv://...",
"MEMORIES_DB": "mcp_memories",
"MDB_GROVE_API_KEY": "...",
"GROVE_BASE_URL": "...",
"GROVE_MODEL": "claude-3-7-sonnet",
"VOYAGE_API_KEY": "...",
"MEMORIES_AUTHOR": "your.name"
}
}
}
}4. Set up auto-capture hooks
Cursor — hooks.json is already in .cursor/hooks.json. It fires the capture script on every stop event automatically.
Claude Code — merge the snippet in hooks/claude/settings-snippet.json into your ~/.claude/settings.json, updating the path to point to this repo.
Related MCP server: Concept Tracker
Tools
Tool | When to use |
| Called automatically by hooks, or manually to record what you're working on |
| Call when done — triggers summarization + embedding and publishes to the team |
| Find past builds relevant to what you're about to start |
| See what the team has built, by language / tag / repo |
| Browse the most recently published sessions |
Typical workflow
# During a session — automatic (hook fires) or manual:
capture_activity(session_id="abc123", conversation_context="Built JWT auth middleware...")
# When done:
complete_session(session_id="abc123", final_notes="Ended up using RS256 instead of HS256 because...")
# Later, someone else starting similar work:
search_memories(query="JWT authentication middleware Node.js")MongoDB Atlas setup
The server creates its own indexes on startup, including the Atlas Vector Search index (memories_vector_index, 1024 dimensions, cosine similarity, voyage-code-4). You need an Atlas cluster with Vector Search enabled.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- -license-quality-maintenancePersistent development memory server that automatically captures and organizes development context, code changes, and user interactions across projects.3
- Flicense-qualityDmaintenanceAutomatically extracts technical concepts from AI coding conversations, organizes them into a searchable knowledge base with hierarchy and categories, and links them to specific locations in your codebase.
- AlicenseBqualityBmaintenancePersistent memory and session intelligence for AI coding assistants. Auto-tracks mistakes, decisions, and context via hooks. Mines your full session history for patterns, predictions, and cross-session search.2116MIT
- AlicenseCqualityCmaintenanceCaptures key development moments, enables multi-agent traceability, provides intelligent context curation, and facilitates seamless agent-to-agent handoffs.2917MIT
Related MCP Connectors
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Persistent memory and cross-session learning for AI coding assistants (hosted remote MCP).
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/benkipnis/mcp-memories'
If you have feedback or need assistance with the MCP directory API, please join our Discord server