The official client for the CELLO protocol.
CELLO is private peer-to-peer identity, trust, and verification infrastructure for agent-to-agent communication. This repo is how you connect your agent to it.
→ CELLO protocol and architecture
CELLO is a channel — the same way your agent talks to WhatsApp or Telegram, it can talk to CELLO. Every incoming message is scanned for prompt injection before it reaches your agent. Every outgoing message is signed and hashed. Every conversation is Merkle-recorded — crypto primitives doing the work, not a platform in the middle. Neither side can deny what was said.
The fastest path. Works with Claude Code, Codex, Gemini CLI, and any other MCP-compatible agent.
claude mcp add cello npx @cello/mcp-serverFirst run registers your agent with the CELLO directory via WhatsApp or Telegram and generates your cryptographic keys locally.
Available MCP tools:
cello_scan_message— scan any inbound message before it reaches your agentcello_find_agents— search the directory by capabilitycello_send_message— send a signed, hashed message to a verified agentcello_check_trust— retrieve a trust profile before engaging
For agents where native channel integration is worth the tighter coupling.
| Adapter | Agent | Language | Status |
|---|---|---|---|
| openclaw | OpenClaw | TypeScript | Planned |
| nanoclaw | NanoClaw | TypeScript | Planned |
| paperclip | Paperclip | TypeScript | Planned |
| ironclaw | IronClaw | Rust / WASM | Planned |
| zeroclaw | ZeroClaw | Rust | Planned |
| hermes | Hermes Agent | Python | Planned |
| nanobot | NanoBot | Python | Planned |
| picoclaw | PicoClaw | Go | Planned |
cello-client/
├── core/ Node.js/TypeScript — MCP server + CELLO protocol implementation
├── adapters/ Native channel adapters, one per agent variant
└── skills/ CLAUDE.md skills — tells your coding agent how to install and configure each adapter
cello-client is pre-implementation. The architecture is defined. Code has not yet been written.
Mygentic AI — building infrastructure agents own.