ai-crew-sync 0.7.1

MCP server that lets a team's AI coding agents (Claude Code, Codex, Cursor or any MCP client) exchange messages, coordinate tasks, share presence and keep shared notes, backed by Postgres
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
---
description: Hold a shared resource (deploy, migration, environment) for a while
argument-hint: "<resource> [minutes, default 30] [purpose]"
---

Take a lock on a shared resource through the crew bus.

Input: $ARGUMENTS

Steps:
1. The first word is the resource name, e.g. `deploy:staging` or `schema:users`. A second numeric word is the TTL in minutes (default 30). The rest is the purpose; if empty, use one line from what I am doing.
2. Call `acquire_lock` with `name`, `ttl_seconds` = minutes × 60, and `purpose`.
3. If it is refused, report verbatim who holds it, why, and when it expires. Do not retry in a loop; offer to wait for it with `wait_for_updates` (`kinds: ["lock"]`, the `wait` recipe) to be told when it frees up.

Confirm with the name, the expiry, and the reminder: `release_lock` (the `unlock` recipe) when I am done; the lock expires on its own otherwise.