CogMemory MCP Server
Provides a unified context system for AI coding agents with memory, knowledge graph, specs, and code graph subsystems, all stored in SQLite. Enables persistent recall of decisions, conventions, errors, project knowledge, and code structure.
README
CogMemory MCP Server
A unified Model Context Protocol server providing four context subsystems for AI coding agents:
- Memory — decisions, conventions, errors, active context, changelog, plan, tasks, sessions
- Knowledge Graph — entities, relations, observations
- Specs — long-form documents (PRD/SRS), optionally linked to a KG entity
- Code Graph — static structural graph (symbols/edges) + named execution traces + AI-generated annotations
Storage: SQLite via better-sqlite3. One .db file per scope.
Quick Start
Install
git clone <repo> && cd cogmemory-mcp
pnpm install
pnpm run build
Configure in VS Code
Add to .vscode/mcp.json (workspace-scoped):
{
"servers": {
"cogmemory": {
"command": "node",
"args": ["/absolute/path/to/cogmemory-mcp/dist/index.js"]
}
}
}
Or add to your user mcp.json for global availability.
Run with MCP Inspector (dev)
pnpm run inspect
Scope Configuration
CogMemory resolves scope in priority order:
-
.cogmemory/config.jsonin workspace root:{ "scope": "global" } -
Environment variable:
COGMEMORY_SCOPE=global -
Default:
workspace
Paths
| Scope | Database Path |
|---|---|
| workspace | <workspace_root>/.cogmemory/memory.db |
| global | ~/.cogmemory/global.db |
Workspace Resolution & Multi-Root Support
CogMemory resolves the workspace root (where .cogmemory/memory.db lives) in this priority order:
--workspace <path>CLI argument (highest priority)COGMEMORY_WORKSPACEenvironment variable- Walk up from CWD looking for the nearest parent containing a
.cogmemory/directory - Fallback to CWD
Multi-Root VS Code Workspaces
In a VS Code multi-root workspace, each folder is a separate workspace root. CogMemory handles this:
- Single-root — Works automatically. VS Code sets CWD to the workspace folder, and
--workspaceis passed viamcp.json. - Multi-root — Each workspace folder can have its own
.cogmemory/. Point each to CogMemory with different--workspacepaths, or place a shared.cogmemory/in a parent directory.
Recommended multi-root mcp.json (per-folder):
{
"servers": {
"cogmemory-frontend": {
"command": "node",
"args": [
"/path/to/cogmemory-mcp/dist/index.js",
"--workspace",
"/path/to/frontend"
]
},
"cogmemory-backend": {
"command": "node",
"args": [
"/path/to/cogmemory-mcp/dist/index.js",
"--workspace",
"/path/to/backend"
]
}
}
}
Or use a shared database (all roots in one place):
{
"servers": {
"cogmemory": {
"command": "node",
"args": [
"/path/to/cogmemory-mcp/dist/index.js",
"--workspace",
"/shared/root"
]
}
}
}
Or use global scope to share across all workspaces:
{
"servers": {
"cogmemory": {
"command": "node",
"args": ["/path/to/cogmemory-mcp/dist/index.js"]
}
}
}
export COGMEMORY_SCOPE=global
Tool Reference
Memory Tools
| Tool | Description |
|---|---|
start_session |
Begin a work session (returns session ID) |
end_session |
Close session, store summary |
get_session_summary |
Recall session details including decisions, errors, changelog |
remember_decision |
Log a decision with rationale and tags |
remember_convention |
Log/update a convention (design token, pattern, style, naming) |
log_error |
Record an error with signature and resolution |
set_active_context |
Upsert current focus/task by key |
get_active_context |
Read current focus by key |
log_change |
Append changelog entry |
add_plan_item |
Add a roadmap item |
update_plan_status |
Change plan item status |
create_task |
Create a task, optionally linked to a plan |
update_task_status |
Change task status |
recall |
Unified search across decisions/conventions/errors/changelog |
Knowledge Graph Tools
| Tool | Description |
|---|---|
create_entity |
Add entity (deduped on name+type) |
create_relation |
Link two entities with a typed relation |
add_observation |
Attach a fact to an entity |
search_knowledge |
Query entities, relations, observations |
Specs Tools
| Tool | Description |
|---|---|
create_spec |
Store a long-form document |
get_spec |
Retrieve by ID or exact title |
update_spec |
Update content/title, auto-bumps version |
Code Graph Tools
| Tool | Description |
|---|---|
index_codebase |
Walk workspace, extract symbols + edges via ts-morph (JS/TS) |
query_code_graph |
Look up a symbol's callers/callees/imports (1-hop) |
generate_codemap |
BFS from entry symbol, bounded subgraph with optional traces + annotations |
annotate_symbol |
Attach narrative text to a symbol or trace |
Architecture
cogmemory-mcp/
├── src/
│ ├── index.ts # entry point, server bootstrap
│ ├── config.ts # scope resolution, path resolution
│ ├── types.ts # shared TS types mirroring schema
│ ├── db/
│ │ ├── connection.ts # DB open/close, pragma setup
│ │ ├── schema.sql # full schema (reference)
│ │ └── migrate.ts # idempotent schema application
│ ├── tools/
│ │ ├── memory.ts # decisions/conventions/errors/context/changelog/recall
│ │ ├── plan-tasks.ts # plan + tasks tools
│ │ ├── sessions.ts # start/end session, summary
│ │ ├── knowledge-graph.ts # entities/relations/observations
│ │ ├── specs.ts # spec CRUD
│ │ ├── code-graph.ts # index_codebase, query_code_graph
│ │ └── codemap.ts # generate_codemap, annotate_symbol
│ └── indexing/
│ ├── ts-analyzer.ts # ts-morph symbol/edge extraction
│ └── walker.ts # file discovery, gitignore respect
├── schema.sql # reference copy
├── package.json
├── tsconfig.json
└── README.md
Schema (15 tables)
- Memory (8):
sessions,decisions,conventions,errors,context,changelog,plan,tasks - Knowledge Graph (3):
entities,relations,observations - Specs (1):
specs - Code Graph (4):
symbols,edges,execution_traces,codemap_annotations
Pragmas
Set on every connection open:
PRAGMA journal_mode = WAL;
PRAGMA foreign_keys = ON;
Development
pnpm run dev # Run with tsx (no build step)
pnpm run build # Compile TypeScript
pnpm run start # Run compiled output
pnpm run inspect # Launch MCP Inspector
pnpm run smoke-test # Run smoke test script
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.