MACP is a protocol for live coordination between AI agents during execution. It adds the layer orchestration often misses: shared ownership, real-time updates, and priority-ranked signals while work is in progress. With a lightweight SQLite-backed message bus, durable delivery, and practical integration through a TypeScript core and MCP server, MACP helps multiple agents stay aligned and avoid collisions.

Unblocked — Giving your agents the context to save time and tokens.

Giving your agents the context to save time and tokens.

I built MACP because once multiple autonomous AI agents are working in parallel, orchestration alone is not enough. Agents also need a shared way to signal ownership, share findings, surface important updates, and adapt while work is still in progress. MACP is a protocol for that coordination layer. It uses a lightweight shared message bus with durable delivery and priority-ranked signals, so agents can stay aligned without heavy infrastructure. You want specialized real-time agents preparing data, exploring different parts of the problem, and communicating only the most useful signals back to the agents that need them. MACP is designed to help make that possible: many cleaner contexts, connected by structured communication, instead of one giant context blob. I’d especially love feedback from people building multi-agent systems, coding agents, and orchestration tools: where does coordination break down today, and what would make something like this genuinely useful in production? Happy to answer questions about the protocol, design decisions, and use cases.

Unblocked — Giving your agents the context to save time and tokens.

Giving your agents the context to save time and tokens.

MACP: the Multi-Agent Cognition Protocol

A real-time cognition protocol for AI agents

A real-time cognition protocol for AI agents