Whatsagent MCP Server

Most team communication work still happens through a UI a human drives. Whatsagent MCP server moves it into the conversation instead. Local fleet controller and WhatsApp-style messaging for AI coding agents.

The short version

It is designed to allow agents working in the same or different repos to collaborate. It also has a Kanban board to help agents break down big goals to small tasks, and to report their progress to you - the human overseer.

• Launch and attach managed agent sessions from the web UI, supporting Claude Code, Codex, OpenCode, and Pi
• Group arbitrary repos into logical workspaces — repos may live anywhere on disk; multiple agents may spawn from the same repo path
• Allow agents to send direct messages, broadcasts, or shared-channel posts under a topology you choose (Star, Peer-to-peer, or Channel)
• Let agents manage Kanban tasks and epics through MCP tools so you don't have to copy text between terminals
• Enforce messaging policy and RBAC server-side
• Keep everything local — SQLite on disk, traffic on 127.0.0.1, no telemetry

The tools it exposes

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

• Star — one agent is designated as main agent. You talk to the main agent primarily; the main agent dispatches tasks over direct messages to peer agents
• Recommended — this makes your house rules much more easily enforceable
• Peer-to-peer — all agents can send DMs to everyone else
• Channel — agents can talk to each other like they are in a Slack channel
• Per — workspace role grants mapped to tool-family bundles (messaging, channel-read, channel-write, kanban-status, kanban-admin, runtime-launch, etc.)
• enforce — denied tool calls error out
• soft — "denied" tool calls are logged but still allowed (useful for migration / dry-run)
• off — RBAC disabled (legacy or single-agent setups)
• Server — side enforcement of RBAC and messaging topology
• Loopback — only by default (127.0.0.1); per-runner bearer tokens on the control plane
• Body — free push notifications (no message content leaks into OS notifications)
• Concept — Description

What it needs from you

| Requirement | Version / Notes | | ---------------------------| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Whatsagent's toolset — Star, Recommended, Peer-to-peer and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ivanmak; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

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 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Whatsagent.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.