Team Memory MCP

Shared team memory for AI coding agents. Bayesian confidence scoring with temporal decay. Works with Claude Code, Devin, Cursor, and any MCP-compatible client.

The Problem

AI coding agents learn valuable things during sessions:

• "Spring Boot: use @Transactional(readOnly = true) on read-only queries to avoid unnecessary write locks"

• "PostgreSQL: always add CONCURRENTLY to CREATE INDEX on tables over 100k rows to avoid locking production"

• "REST APIs: return 409 Conflict (not 400) when a resource already exists — the API gateway retries on 400"

• "Flyway: migration files must follow V{ticket}_{seq}__{description}.sql or CI rejects the PR"

But when the session ends, that knowledge disappears. The next session starts from zero.

Multiply that across a team of 10 engineers, each using AI agents independently, and you get the same mistakes rediscovered week after week. The same wrong @Transactional scope. The same locking CREATE INDEX. The same 400 vs 409 confusion.

Related MCP server: total-recall

The Solution

Team Memory gives AI agents a persistent, shared knowledge store where engineering patterns are stored, validated by the team, and ranked by confidence over time.

1. Engineers or AI agents store patterns they discover during development

2. Each pattern starts with a confidence of ~0.667

3. Confirmations from team members increase confidence; corrections decrease it

4. Patterns not confirmed for 90 days gradually lose confidence (temporal decay)

5. Search results are ranked by confidence — well-validated patterns surface first

What This Looks Like in Practice

"Spring Boot: use @Transactional(propagation = REQUIRES_NEW) for audit logging
 to ensure logs persist even if the parent transaction rolls back"
→ Confirmed 23 times | Confidence: 0.92

"PostgreSQL: always add CONCURRENTLY to CREATE INDEX on tables with 100k+ rows"
→ Confirmed 15 times | Confidence: 0.88

"REST APIs: return 409 Conflict (not 400) when resource already exists on POST"
→ Confirmed 8 times, corrected 1 time | Confidence: 0.82

"JPA: avoid fetch = FetchType.EAGER on @ManyToOne — causes N+1 queries in lists"
→ Confirmed 31 times | Confidence: 0.94

New team members get the accumulated knowledge from day one. AI agents stop making the same mistakes.

How It Compares

We surveyed 10+ existing MCP memory servers before building this. No existing solution combines all four properties that matter for shared engineering knowledge:

Why Not Use an Existing Solution?

@modelcontextprotocol/server-memory — Anthropic's official reference implementation. Knowledge graph stored in a flat JSONL file. No confidence scoring, no decay, no team support. Intentionally minimal.

mem0-mcp — Commercial platform (YC-backed, $24M raised) optimized for conversational memory. Has team scoping via user_id/agent_id, but confidence is LLM-based re-ranking — not a transparent probabilistic model. No way to query "how many times has this pattern been confirmed?" Cloud dependency and cost.

mcp-memory-service — Most feature-rich OSS memory server (1,500+ stars). Has quality fields, access_count, and consolidation decay. But quality scoring is LLM-evaluated (opaque), team memory is basic SSE event propagation without access controls, and there's no confirmation count per memory.

Memento MCP — Neo4j-backed with configurable half-life decay on relations. Closest to our confidence model mathematically, but confidence values are manually assigned by the LLM rather than computed from evidence. Single-user only. Requires Neo4j infrastructure.

Memorix — Best team collaboration primitives (file locks, task boards, messaging across IDEs). But no confidence scoring, no temporal decay, no observation count tracking.

Graphiti/Zep — Academically rigorous bi-temporal knowledge graph (23k+ stars, published paper). Confidence is binary — facts are either valid or invalidated. No graduated confidence, no confirmation tracking. Requires Neo4j/FalkorDB.

The Gap

No existing solution tracks: "This pattern has been confirmed correct 47 times across 12 sessions by 5 different engineers."

That's what Team Memory does. The confidence score is:

• Transparent — you can see exactly why a pattern has a given score

• Evidence-based — computed from confirmation and correction counts

• Self-correcting — unused patterns decay, wrong patterns get corrected

• No LLM dependency — pure math, no API calls for scoring

Setup

Quick Start (npx — no install needed)

npx team-memory-mcp

Register with Claude Code

claude mcp add team-memory -- npx team-memory-mcp

Register with Devin

devin mcp add team-memory -- npx team-memory-mcp

Register with Cursor

Add to your .cursor/mcp.json:

{
  "mcpServers": {
    "team-memory": {
      "command": "npx",
      "args": ["team-memory-mcp"]
    }
  }
}

Install from Source (alternative)

git clone https://github.com/gustavolira/team-memory-mcp.git
cd team-memory-mcp
npm install
npm run build
node build/index.js

Storage

Local Mode (default)

SQLite database at ~/.team-memory/memories.db. No external services required. Zero configuration.

Shared Mode (PostgreSQL)

Set the TEAM_MEMORY_DATABASE_URL environment variable to connect to a centralized PostgreSQL instance:

export TEAM_MEMORY_DATABASE_URL=postgresql://user:password@host:5432/team_memory

When set, all agents and engineers on the team share the same memory store. The server auto-creates the required table and indexes on first run.

MCP Tools

Confidence Scoring

Uses a Beta-Bernoulli Bayesian model with temporal decay:

confidence = (alpha / (alpha + beta)) × decay + floor × (1 - decay)

alpha = 1 + confirmations    (starts at 2)
beta  = 1 + corrections      (starts at 1)
decay = 0.5 ^ (days_since_last_confirmation / 90)
floor = 0.05

Scoping

Patterns can be scoped to:

• project (default) — tied to the current git repository (auto-detected from git remote get-url origin)

• global — available across all projects

Both project-scoped and global patterns are returned by default when searching.

Features

• Auto-detected contributor — reads from git config user.name

• Cached git detection — project ID and contributor resolved once per session

• Graceful error handling — database errors return MCP error responses, never crash

• Dual storage backends — SQLite for local, PostgreSQL for team sharing

• Zero configuration — works out of the box, no env vars needed

Usage Examples

"Remember: Spring Boot @Transactional(readOnly = true) should be used on all read-only
 service methods to avoid write locks and improve connection pool usage"
→ AI calls store_pattern with domain="spring-boot", tags=["transactional", "performance"]

"What patterns do we have for PostgreSQL?"
→ AI calls search_patterns with query="PostgreSQL"

"That pattern about CONCURRENTLY on CREATE INDEX is correct, saved us from a production lock"
→ AI calls confirm_pattern (confidence goes up)

"That pattern about 400 vs 409 is wrong for our new gateway — it no longer retries on 400"
→ AI calls correct_pattern with replacement text (confidence goes down, content updated)

Roadmap

• Semantic search via embeddings

• Auto-capture hooks for Claude Code

• Devin auto-recall at task start

• Web dashboard for pattern management

• Conflict resolution for contradicting patterns

• Published on npm: npx team-memory-mcp

Built With

• Model Context Protocol SDK — MCP server framework

• better-sqlite3 — Local SQLite storage

• pg — PostgreSQL client for shared mode

• Zod — Schema validation

License

MIT