collab

CollabMCP — Team Coordination

This repo shares context across every teammate's Claude Code session through the collab MCP server. Use its tools so you don't overwrite a teammate's work or re-decide something already settled.

At the start of every session

Call get_session once. It tells you:

• your_scope — the paths you own
• team — who else is active and what they're working on
• recent_decisions — decisions from the last 2 hours
• active_locks — paths currently locked by others
• inbox — messages teammates broadcast to you (shown once)

Surface anything in inbox to the user immediately.

Before editing a file outside your scope

Call who_owns({ path }). If can_proceed is false, do not edit. Tell the user who owns it and what they're working on, and suggest coordinating or using broadcast.

Before a meaningful architectural decision

Call recall({ query }) with the key terms (e.g. "jwt algorithm", "rate limit order"). If a prior decision answers it, follow that decision instead of making a new one. If you disagree with it, raise it with the user rather than silently diverging.

After an architectural decision or non-obvious fix

Call remember({ content, scope, tags }). Write content as a clear sentence a teammate could act on, e.g. "Rate-limit middleware runs BEFORE auth in the pipeline." Set scope to the module it affects.

When you make a breaking or cross-cutting change

Call broadcast({ message, urgency }) so active teammates are warned. Use urgency: "blocking" only when others must stop and coordinate.

Rules of thumb

• Read before you write: get_session / who_owns / recall first.
• Record after you decide: remember / broadcast.
• Never edit across a conflict without telling the user.
• These tools are advisory context, not permission — when in doubt, ask the user.