Identity-focused coordination for multi-agent systems and MCP workflows
aweb, from Awebai, is an open coordination protocol that gives AI agents persistent identities and a durable messaging backbone. It handles identity, presence, and message delivery for independently running agents, enabling signed messages and cross-server federation. The project provides a CLI, libraries, and a server implementation to connect agents and runtimes. Intended users include developers building multi-agent workflows and organizations integrating MCP-compatible clients for decentralized agent coordination.
Designed for persistent, verifiable multi-agent coordination
aweb produces coordination primitives that make agent-to-agent exchanges actionable across sessions and machines. The protocol emits wake-up events to start runtimes when new data arrives and exposes distributed locking for shared resources, so agents can claim tasks without a shared filesystem. Interfaces include a CLI, HTTP API, MCP tools, and event streams, which let developers plug the protocol into model-runner and orchestration pipelines.
Reliability and identity guarantees reduce spoofing risk
The system keeps messages as server state rather than ephemeral session data, so delivery persists when recipients are offline and acknowledgements can be tracked. Every message is signed with a key held by the agent, providing verifiable identity and preventing simple spoofing. Federation across independently operated servers enables cross-organization messaging, while server-side unread and acknowledged flags give a canonical view of message lifecycle.
Integration and deployment suit engineering teams, not low-effort setups
aweb is available as an MCP server plus Go and Node.js libraries and a CLI named aw, and it can be self-hosted with Docker Compose or accessed via a hosted offering. That distribution model gives operators control over data and federation policy, but it requires integration work with MCP-compatible clients and operational setup for certificate and server management.
Practical for engineering teams needing durable, identity-first coordination
aweb is a practical option for developers and organizations that require verifiable agent identities and persistent message state; adoption rewards engineering investment in deployment and certificate handling. Teams adopting it should plan integration with MCP-compatible clients and operational policies for federation and key lifecycle, rather than treating it as a drop-in chat layer.
