agora
The agora server provides a shared, persistent space for Claude Code sessions within a repository to coordinate work, detect conflicts, log activities, and facilitate communication.
Resume project (
resume_project): Get a full summary of active sessions, recent activity, file/branch collisions, and unread notes — ideal for quickly catching up when starting or resuming a session.See who is active (
who_is_here): List all currently active sessions and the specific files each one is touching, giving a live view of parallel work in the repo.Activity log (
activity_log): View a filterable timeline of all repository events, with options to filter by time window (in minutes) or by a specific session ID.Check for collisions (
check_collision): Before editing files or switching branches, check whether another active session is already working on the same files or branch, helping you avoid overwriting others' work.Leave a note (
leave_note): Send a message to a specific session or broadcast it to all active sessions, enabling asynchronous communication between Claude Code instances.Read notes (
read_notes): Retrieve notes addressed to a specific session (or broadcast notes), with the option to filter for unread-only, and automatically mark them as read.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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.
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.
Related MCP server: agent-bridge
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.xClaude Code (or any MCP client)
Installation
From npm — nothing to clone:
# Register the MCP server — nothing to install for this part
claude mcp add agora -- bunx --bun @vorluno/agora-mcp
# The hooks need the CLI on your PATH. Install once, then run it from any repo.
# Idempotent; add --project to scope it to the current repo only.
bun add -g @vorluno/agora-mcp
agora-init initFrom source — if you want to change it:
git clone https://github.com/vorluno/agora-mcp.git
cd agora-mcp
bun install
bun run src/cli.ts init
claude mcp add agora -- bun run /absolute/path/to/agora-mcp/src/index.tsConfiguration
Any MCP client works. The mcpServers entry:
{
"mcpServers": {
"agora": {
"command": "bun",
"args": ["run", "/absolute/path/to/agora-mcp/src/index.ts"]
}
}
}For Claude Code, claude mcp add (above) writes this for you. For Warp or Cursor, paste the snippet into their MCP settings.
Tools
Tool | Description |
| Summary of the agora: active sessions, recent activity, collisions, unread notes. |
| Active sessions and which files each one is touching. |
| The repo's event log, filterable by time/session. |
| Is another active session touching these files or this branch? |
| Leave a note for another session (or broadcast to all). |
| Read notes addressed to a session (marks them read). |
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):
Hook | What it does |
| Registers the session and injects the agora summary into your context (also fires on |
| Records the file claim + event; warns if a new collision appears. |
| Warns you before editing if another session already holds the file. |
| Marks the session idle / stopped and releases its claims. |
Development
bun test # full suite (incl. a real WAL concurrency test)
bunx tsc --noEmit # type-checkBuilt 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 security@vorluno.dev, 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.
Built by Vorluno — a software studio from Panamá 🇵🇦
Part of the mcp-s family of MCP servers.
Available Tools
6 toolsactivity_logActivity logC
Bitácora de eventos del repo (filtrable por minutos/sesión).
Inputs: sinceMinutes, sessionId, limit. Returns: events
check_collisionCheck collisionC
¿Otra sesión activa está tocando estos archivos o esta rama?
Inputs: paths (required), sessionId, branch. Returns: fileConflicts, branchCollisions, ok
leave_noteLeave noteB
Deja una nota para otra sesión (to) o para todas (broadcast si se omite to).
Inputs: body (required), fromSession, to. Returns: id
read_notesRead notesB
Lee notas dirigidas a una sesión (o broadcast) y las marca leídas.
Inputs: forSession, unreadOnly. Returns: notes
resume_projectResume projectA
Resumen del ágora del repo: sesiones activas, actividad reciente, colisiones y notas sin leer.
Inputs: no named parameters. Returns: sessions, recentActivity, fileConflicts, branchCollisions, +1 more
who_is_hereWho is hereA
Sesiones activas y qué archivos toca cada una.
Inputs: no named parameters. Returns: sessions
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: activity_log for event tracking, check_collision for conflict detection, leave_note/read_notes for messaging, resume_project for summary, and who_is_here for session listing. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., activity_log, check_collision, leave_note, read_notes, resume_project, who_is_here). The naming is predictable and uniform.
With 6 tools, the number is well-scoped for a collaborative session management server. Each tool serves a necessary function without unnecessary duplication or bloat.
The tool set covers core aspects: logging, collision detection, note passing, and session overview. A minor gap is the lack of explicit session lifecycle tools (e.g., ending a session), but the set is still functionally complete for common use cases.
Related MCP Connectors
Shared work memory for Claude Code, Codex, Cursor and chat, scoped to each repository.
Shared memory for a team in Claude Code: what one person records, everyone has.
Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Related MCP Servers
- AlicenseAqualityBmaintenanceLocal-first shared memory and task coordination for AI coding agents. One Go binary, MCP server, markdown files you own. Hooks for Claude Code and Codex CLI (and their desktop apps).306MIT
- AlicenseNot gradedqualityAmaintenanceEnables coordinating Claude Code and Codex across separate Git worktrees with shared issue ownership, file reservations, messages, and explicit handoffs.213 PyPI3MIT
- AlicenseNot gradedqualityBmaintenanceEnables separate Claude Code sessions across a team to see teammates' live presence, warn before editing a file someone else is editing, route shared-contract changes to the developers whose code depends on them, and produce structured handoffs when a session ends.357 npm1MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.202MIT