workbrain
Provides integration with Git repositories by automatically capturing commit activity through an optional post-commit hook, recording hashes, branches, messages, and changed files into a local database.
Uses SQLite as the local storage backend for agenda items, work log entries, and commit records, enabling persistent and queryable data management.
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., "@workbrainWhat's my current focus and recent work?"
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.
Workbrain
Your personal operating layer for AI-assisted work.
Workbrain is a local Model Context Protocol (MCP) server for Claude Code. It gives Claude persistent context about how you work, what you're focused on this week, and what you've shipped — without sending that data to the cloud or sharing it with your team.
Overview
Most AI coding setups tell the model how to behave (rules, prompts). Workbrain tells it what you're doing — and lets it keep that picture up to date as you work.
Layer | What it stores | Example |
Playbook | How you work | Bug-fix approach, communication style |
Agenda | What you're focused on | This week's priorities and deliverables |
Work log | What you shipped | Summaries linked to agenda items |
Commits | Raw git activity | Auto-captured via optional hook |
Everything lives on your machine in ~/.workbrain/. Nothing is committed to project repos unless you choose to.
Related MCP server: Melchizedek
Features
Unified context —
get_contextreturns playbook, agenda, work log, and commits in a single callLiving weekly board — Claude can add, update, and complete agenda items during a session
Automatic work logging — marking an agenda item done creates a linked work log entry
Local-first & private — SQLite + markdown on disk; no accounts, no cloud sync required
Cross-project — registered at user scope; follows you across every repo
Git integration — optional post-commit hook records commits automatically
CLI — check your week from the terminal without opening Claude
Requirements
Node.js 22+ (uses built-in
node:sqlite— no native dependencies)Claude Code CLI or extension (Cursor, VS Code, or terminal)
Quick start
git clone https://github.com/himanshu-sharma-55/work-brain.git
cd work-brain
npm install
node bin/install.jsRegister the MCP server (server name is workbrain; repo folder is work-brain):
claude mcp add --scope user workbrain -- node /absolute/path/to/work-brain/src/index.jsAdd to your shell profile (~/.zshrc or ~/.bashrc):
export WORKBRAIN_ROOT=/absolute/path/to/work-brainVerify in Claude Code: type /mcp and confirm workbrain is connected.
Edit your playbook: ~/.workbrain/playbook.md
How it works
┌─────────────────────────────────────────────────────────┐
│ Claude Code │
│ (Cursor / VS Code / CLI) │
└────────────────────────┬────────────────────────────────┘
│ MCP (stdio)
▼
┌─────────────────────────────────────────────────────────┐
│ Workbrain Server │
│ get_context · get_agenda · log_work · get_commits … │
└────────────────────────┬────────────────────────────────┘
│
┌──────────────┼──────────────┐
▼ ▼ ▼
playbook.md data.db git hook (optional)
(how you work) (agenda, (commit capture)
work log,
commits)
└──────────────┴──────────────┘
│
~/.workbrain/
(or WORKBRAIN_HOME)Claude calls Workbrain tools on demand — your rules aren't loaded into every message, keeping context lean until it's needed.
MCP tools
Tool | Description |
| Recommended entry point. Playbook, current agenda, recent work log, and commits |
| Read your personal playbook |
| Replace or append to your playbook |
| Weekly board: focus, coming up, expected |
| Add an item to the board |
| Update status, title, estimate, etc. Auto-logs work when marked done |
| Remove an agenda item |
| Move unfinished items from last week to the current week |
| Agenda stats, work log, and commits for a given week |
| Recent work summaries |
| Log what you shipped (optionally linked to an agenda item) |
| Recent commits captured by the git hook |
Recommended session flow
Add this to your personal Cursor or Claude rules:
At the start of a work session, call
get_context. When we finish a clear task, update the agenda and log work. Marking an agenda item done is enough — it auto-logs.
Example prompts
You say | Workbrain does |
"What's my focus this week?" | Calls |
"Mark CSV export as in progress" | Calls |
"What did I ship this week?" | Calls |
"Roll over unfinished items" | Calls |
"How do I usually fix bugs?" | Reads playbook |
CLI
Check status without Claude:
node bin/workbrain.js status # current week at a glance
node bin/workbrain.js summary # full week recap
npm run status # shortcut via package scriptConfiguration
Environment variables
Variable | Default | Description |
|
| Data directory (playbook, database) |
| — | Path to the work-brain repo; required for git hooks |
Data directory layout
~/.workbrain/
├── playbook.md # How you work (markdown)
├── data.db # Agenda, work log, commits (SQLite)
└── git-template/ # Git hook template (created by install)Custom data directory
export WORKBRAIN_HOME=/path/to/shared/workbrain-data
claude mcp add --scope user workbrain -- \
env WORKBRAIN_HOME=/path/to/shared/workbrain-data \
node ~/work-brain/src/index.jsGit integration
node bin/install.js configures a global git template so new repositories automatically include the post-commit hook.
For an existing repository:
export WORKBRAIN_ROOT=/path/to/work-brain # in ~/.zshrc
node /path/to/work-brain/bin/setup-git-hook.js /path/to/repoEach commit records hash, repo, branch, message, and files changed into ~/.workbrain/data.db.
Multi-machine setup
Clone and register on each machine:
git clone https://github.com/himanshu-sharma-55/work-brain.git ~/work-brain
cd ~/work-brain && npm install && node bin/install.js
claude mcp add --scope user workbrain -- node ~/work-brain/src/index.jsEach machine maintains its own ~/.workbrain/ by default. To sync data:
Method | Approach |
Cloud folder | Symlink |
Dotfiles repo | Track |
Shared path | Set |
Cursor setup
Workbrain uses Claude Code MCP, not Cursor's ~/.cursor/mcp.json.
Install the Claude Code extension in Cursor
Open the integrated terminal
Run
claude mcp add(see Quick start)In the Claude panel:
/mcp→ enable workbrain
Privacy & scope
Workbrain is designed for individual use:
MCP is registered with
--scope user— not tied to any project repoPersonal data never leaves your machine unless you sync it yourself
Do not commit
.mcp.jsonto shared team repositories
Troubleshooting
Issue | Resolution |
| Install Claude Code CLI or use the extension terminal |
Server missing from | Re-run |
Broken path after moving the repo |
|
Commits not recording | Verify |
Server won't start | Run |
Development
npm install
npm start # run MCP server (stdio)
npm run install:local # install + init data dir + git template
npm run status # CLI status checkFor local development with a global CLI alias:
cd work-brain && npm link
claude mcp add --scope user workbrain -- workbrainNaming
Name | Used for |
| GitHub repository and local clone directory |
| MCP server name, npm package, data dir ( |
| Environment variable prefix |
License
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
- AlicenseBqualityAmaintenanceProvides a persistent "second brain" for Claude featuring zero-latency hot caching, semantic cold storage, and automatic pattern mining from activity logs. It enables users to store, search, and automatically extract project facts and code patterns for enhanced contextual recall.567MIT
- AlicenseAqualityBmaintenancePersistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.16557MIT
- AlicenseAqualityDmaintenanceCross-surface persistent memory for Claude. Bridges context between Claude Chat, Code, and Cowork via local SQLite with full-text search.6146MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent memory for Claude Code, automatically extracting and surfacing relevant context from past sessions to avoid re-explaining issues and decisions.MIT
Related MCP Connectors
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
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/himanshu-sharma-55/work-brain'
If you have feedback or need assistance with the MCP directory API, please join our Discord server