
Agora Mcp
io.github.vorlunoPublished by GitHub account vorlunov0.1.0Updated Nov 3, 2026
Shared per-repo space for Claude Code sessions: see activity, get collision warnings, notes.
Overview
Retired local MCP server that gives Claude Code sessions on the same repo a shared SQLite board for activity, collision warnings and notes.
- What you can do
- Summarize the repo's shared space: active sessions, recent activity, collisions and unread notes
- List active sessions and the files each one is touching
- Read the repo event log, filtered by time or session
- Check whether another live session is writing the same files or branch
- Leave notes to a specific session or broadcast, and read notes addressed to a session
- When to use it
- Only if you still run several Claude Code sessions on one repository and want them to see each other's file claims and leave notes. The README marks it retired because Claude Code now coordinates sessions itself, so new setups are unlikely to need it.
- Requirements
- Runs locally over stdio via Bun 1.3+ and git 2.x, with any MCP client such as Claude Code. No daemon or server process; state lives in a SQLite file under the repo root. No authentication, environment variables or headers declared.
Installation
In SourceWeft
- Open Agora Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
agora
A shared, persistent space for your Claude Code sessions — per repository.
See what other sessions are doing, get warned before you overwrite their work, and leave notes. No daemon, no server to run.
[License: Apache 2.0] [Bun] [Model Context Protocol] [Built with Claude Code]
Retired
Claude Code now does this itself. Sessions coordinate, see each other's work and share state without a separate MCP server in between, which is what this existed to provide.
The repository is archived and read-only. It still works — nothing was removed from npm, and the last published version keeps installing — but it will not be maintained, and it does not need to be. If you want the idea rather than the package, the whole design is in
docs/and the licence lets you take it.
Why
When several Claude Code sessions work on the same repository — in parallel, or just over the course of a day — they're blind to each other. None of them knows what the others touched, they overwrite the same files silently, and the context is lost when you close them.
agora gives every session a shared place to leave a trail and look at each other's work.
How it works
The whole system is one SQLite file per repo: <repo-root>/.agora/space.db (in WAL mode, so multiple processes read and write it at once without corruption).
- No one runs a server. There's no daemon, no web app. The "space" is the file.
- Every session of the repo writes what it does and reads what the others did.
- Because it's a file, it persists by itself — close everything, come back tomorrow, the state is still there.
- It's a shared board, not a live chat: sessions find out when they start, when they're about to edit (collision), or when they ask (the tools).
Multi-worktree friendly: the
.dblives at the main repo root, so every session of the repo — including those in different worktrees — shares one agora.
Features
- 🟢 See who's here and what files each session is touching, live.
- ⚠️ Collision warnings — before you edit a file (or work a branch) another active session already holds.
- 📋 Project resume — open a session and get a summary of what the others did.
- 📓 Activity log — a per-repo timeline of everything that happened.
- ✉️ Notes between sessions (directed or broadcast).
- 🛡️ Best-effort hooks — they exit
0no matter what; they never block your session.
Requirements
- Bun 1.3+
git2.x- Claude Code (or any MCP client)
Installation
From npm — nothing to clone:
From source — if you want to change it:
Configuration
Any MCP client works. The mcpServers entry:
For Claude Code, claude mcp add (above) writes this for you. For Warp or Cursor, paste the snippet into their MCP settings.
Tools
How collisions are detected
- File collision: 2+ distinct sessions with an active
writingclaim on the same file. - Branch collision: 2+ active sessions on the same branch but in different worktrees.
Only live sessions are counted, so a session that died without a clean exit won't produce false positives.
Automatic capture (hooks)
init installs 5 best-effort hooks (they always exit 0):
Development
Built test-first across 14 TDD tasks with per-task and whole-branch review.
Contributing and security
Read CONTRIBUTING.md first — its first line tells you whether your pull request will be considered. Vulnerabilities go to [email protected], never to an issue: see SECURITY.md, where the 72-hour acknowledgement is the one response time we commit to.
License
Apache-2.0 © 2026 Vorluno. See NOTICE.
Up to and including 0.1.0 this was MIT. Those releases stay MIT — a licence already granted cannot be withdrawn. From 0.2.0 on it is Apache-2.0, which grants patent rights explicitly.
Source: README.md at commit dba487c
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts