claude-inbox
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., "@claude-inboxcheck my inbox for new tasks"
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.
claude-inbox
EN · SK
A local inbox that lets Claude chat and Claude Code sessions (desktop app and terminal) exchange tasks, tickets and project context. One person, one machine, no network.
Threads and tickets. The chat sends a task to a project, Claude Code asks questions, the chat answers, Claude Code closes the thread with a summary.
Project map. Every project has a markdown card (what it is, current focus, decisions, next step) that you can edit in any editor. Chat and Code read it before they work.
Sessions. See which Claude Code sessions are active in which project and branch.
Status line + band. Every Code session shows
📬 api · 1 new · 2 on you · 1 waiting · 2 sessionsfor its own project.
Install
Requirements: Node 22+, Claude desktop and/or Claude Code.
git clone https://github.com/eodesign7/claude-inbox.git
cd claude-inbox
npm install
npm run setup -- --chat-agent=chat --wait--wait makes setup wait until you quit the Claude desktop app (it keeps its own copy of its config and would overwrite
ours). Quit it (Cmd+Q on macOS) when asked, then start it again. Setup makes a backup (*.bak-<time>) before every write and
keeps your existing settings:
builds the project,
adds the
claude-inboxMCP server to the Claude desktop config (macOS, Linux, Windows) withCLAUDE_INBOX_AGENT=<chat-agent>(defaultchat),registers the server in Claude Code (scope user, no fixed identity) and installs the
inbox-barmod,sets
statusLineand theSessionStart/UserPromptSubmit/SessionEndhooks in~/.claude/settings.json(an existingstatusLineis replaced and printed),links the
claude-inboxcommand globally and verifies the desktop config (desktop config OK).
The band above the prompt (inbox-bar) is installed by setup. To install only the mod from GitHub, in the Claude Code CLI:
claude plugin install inbox-bar --marketplace eodesign7/claude-inbox.
Then, in every repository:
claude-inbox link <agent> # creates the project card and ties this repo to itInstruction blocks to paste into your chat project and your Claude Code projects are in INSTRUCTIONS.md.
Related MCP server: claude-code-bridge-mcp
How identity works
An MCP server shared by chat and Code must know who is talking:
Claude Code session (detected by
CLAUDECODE=1, which Claude Code sets for its child processes): cardpaths(longest prefix wins) → git repository name → folder name →default.CLAUDE_INBOX_AGENTis ignored.Chat:
CLAUDE_INBOX_AGENT, then the same chain.
claude-inbox whoami prints the identity and where it came from. The server also prints
cwd / agent / source / environment to stderr on start.
MCP tools
tool | what it does |
| all projects: focus, open threads, active sessions, last summary |
| card, notes, open threads, active sessions, last 3 summaries |
| write the card ( |
| read-only access to |
| new thread |
| reply in a thread |
| my messages |
| whole thread, marks it read |
| closes, sends the summary, appends the daily log, rewrites card sections |
| threads by status |
Files
~/.claude-inbox/
inbox.db machine state: threads, messages, sessions
projects/<agent>/card.md project card (YAML frontmatter: name, paths, ticket_prefix)
projects/<agent>/notes/*.md free notes
log/YYYY-MM-DD.md daily log of summariesContext lives in the markdown files (source of truth); SQLite holds only machine state.
CLI
claude-inbox map # overview of projects
claude-inbox show <thread_id> # a whole thread
claude-inbox card <agent> # open the card in $EDITOR
claude-inbox log [YYYY-MM-DD] # daily log
claude-inbox link <agent> # card from template + this repo's path
claude-inbox whoami # who am I here and why
claude-inbox send <to> "text" --as <agent>Troubleshooting
The server is missing in the desktop app. The app overwrites its config while running. Run
npm run setup -- --wait, quit the app when asked.npm run checkverifies the config and the handshake.claudenot found during setup. Setup also looks inside the desktop app's bundle; otherwise it prints the commands to run by hand.A Code session writes as the wrong agent. Run
claude-inbox whoamiin the repo and check the stderr line in~/Library/Logs/Claude/mcp-server-claude-inbox.log(macOS). The desktop app also hands its own MCP servers to Code sessions; the chat instance tells the model not to use it from Code.
Status line labels are Slovak for now (nové = new, na tebe = waiting for you, čaká = waiting). Localization is welcome.
Development
npm test # vitest, temporary database and configs; never touches your real ones
npm run test:mod # tests of the inbox-bar mod (needs the `claude` CLI)
npm run buildMIT license.
Slovensky
Lokálna schránka správ medzi Claude chatom a Claude Code (desktop appka aj terminál): úlohy, tickety a kontext projektov. Jeden používateľ, jeden počítač, bez siete.
Inštalácia (Node 22+):
git clone https://github.com/eodesign7/claude-inbox.git
cd claude-inbox
npm install
npm run setup -- --chat-agent=chat --wait--wait počká, kým ukončíš Claude desktop (Cmd+Q). Appka si drží vlastnú kópiu configu a pri ukladaní by náš zápis prepísala.
Setup pred každým zápisom urobí zálohu a zachová ostatné nastavenia. Potom appku spusti a v každom repe:
claude-inbox link <agent>Identita: v Code session sa
CLAUDE_INBOX_AGENTignoruje; platí karta podľapaths, názov git repa, názov priečinka,default. V chate platíCLAUDE_INBOX_AGENT. Zistíš ju cezclaude-inbox whoami.Kontext je v markdowne
~/.claude-inbox/projects/<agent>/card.md(sekcie Čo to je, Aktuálny fokus, Rozhodnutia, Ďalší krok), upravíš ho v editore:claude-inbox card <agent>.Nástroje, súbory a CLI sú rovnaké ako v anglickej časti vyššie. Bloky inštrukcií pre chat a Claude Code sú v INSTRUKCIE.md.
Riešenie problémov: server v appke chýba →
npm run setup -- --waita ukonči appku;npm run checkoverí config.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.
Send notes from Claude, ChatGPT or Claude Code to your ThinkSpace inbox and arrange them into cards.
- SeturosOAuthcom.seturos
Shared work memory for Claude Code, Codex, Cursor and chat, scoped to each repository.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceShare context, detect file conflicts, and send messages across parallel Claude Code sessions71 npmMIT
- AlicenseNot gradedqualityCmaintenanceBridges Claude Code terminal sessions with Claude Chat by exposing session logs as tools, enabling seamless context transfer and two-way communication via a cooperative inbox and optional Google Drive sync.38 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI sessions like Claude, Cowork, and Claude Code to pass tasks and replies between each other through per-session mailboxes, and to keep a shared knowledge base of notes that every session can read, search, and update. Runs as a self-hosted Cloudflare Worker with D1 storage, so all data stays in the user's own account.41 npmMIT
- AlicenseAqualityCmaintenanceEnables a planning Claude chat and Claude Code to exchange work through local Markdown files, letting the chat create tasks that code agents pick up, complete, and report back on. Project-scoped task and report tools track each item's status from open through reported, eliminating manual copy-paste between the two clients.5MIT