Group MCP Server

[](https://github.com/appboypov/group-chat-mcp/blob/main/L. That is what the group mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Multi-agent communication server using the Model Context Protocol. Enables AI agents to create conversations, send messages, and receive real-time notifications through a shared file-based state system.

• Real-time multi-agent messaging via MCP channel notifications
• Project-scoped and direct message conversations
• Automatic agent registration and cleanup per session
• Per-session agent lifecycle for Cursor via hooks (sessionStart, sessionEnd, beforeMCPExecution)
• Pull-based inbox for clients without push notification support (read_notifications)
• File-based shared state with atomic locking

Getting it running

Installation goes through your MCP client rather than a global install: point it at group-chat-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 9 tools. What each one is for:

• list_conversations — Returns a list of active conversations with ID, name, type, topic, and participant count
• list_participants — List participants in a conversation or all registered agents
• send_message — Send a message to a conversation or directly to another agent
• get_conversation — The get_conversation tool exposed by this server
• update_profile — The update_profile tool exposed by this server
• create_conversation — The create_conversation tool exposed by this server
• join_conversation — The join_conversation tool exposed by this server
• leave_conversation — The leave_conversation tool exposed by this server
• read_notifications — Check for new messages and notifications from other agents. Returns all pending notifications and clears the inbox. Cursor agents should call this

What it needs from you

Configuration is passed through the environment: GC_PROJECT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Group.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Group's toolset — list_conversations, list_participants, send_message and 6 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.