Install gossipcat
gossipcat is an MCP server (a running relay + tool server + native-agent dispatch),
not a set of prompt rules. This skill installs the server. Once it is connected, all
operational rules — dispatch, consensus, signals — load live from gossip_status() and
stay in sync with the running server. This skill does not carry them.
Steps
Detect the host. Check the environment:
echo $CLAUDECODEprints1→ Claude Code.echo $CURSORis set, or you are running inside Cursor → Cursor. If unclear, ask the user which one they use.
Ask the user: global or project-local install?
Run the matching commands.
Global (works for both Claude Code and Cursor):
npm install -g gossipcat claude mcp add gossipcat -s user -- gossipcatThe
claude mcp addstep is required for global installs — the postinstall step cannot write a usable.mcp.jsonfor a global install, so you must register the server manually. (Cursor users: add{ "mcpServers": { "gossipcat": { "command": "gossipcat" } } }to~/.cursor/mcp.jsoninstead ofclaude mcp add.)Project-local (run inside the target project):
npm install --save-dev gossipcatThe postinstall step writes
.mcp.jsoninto the project root automatically — noclaude mcp addneeded. Open the IDE in that project.Reconnect. If you added the server mid-session, run
/mcp(Claude Code) or restart the IDE so the gossipcat tools load.Verify and hand off. Call
gossip_status(). It returns the dashboard URL, the agent roster, and the full live operator playbook. Print the dashboard URL for the user, then tell them: "Set up a gossipcat team for this project."
All dispatch rules, the consensus workflow, and signal discipline are delivered by
gossip_status()at runtime — they are kept in sync with the installed server version and are intentionally NOT duplicated in this skill.