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 "Deploy 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-memories search 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.
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 Voyage voyage-code-4
Team members search with natural language — vector search + Voyage reranking returns the most relevant past builds
npm install
npm run buildcp .env.example .env
# Fill in MONGODB_URI, MDB_GROVE_API_KEY, GROVE_BASE_URL, VOYAGE_API_KEY, MEMORIES_AUTHORAdd 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"
}
}
}
}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: VibeTape MCP Server
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 |
# 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")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 deployed
Shared memory for coding agents. Stop re-explaining your codebase every session.
One searchable history across every AI coding tool, with secret scanning and a shared task board.
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Shared project memory that keeps teammates and AI agents aligned across sessions.
