waggle
MCP-native artifact references for agent handoffs with read receipts.
waggle is an open-source MCP server and CLI that turns file paths and pasted context into ~30-byte attributed tokens. Agents mint, resolve, search, and read through the token while orchestrators get coverage and funnel receipts showing what was actually opened.
Official resources
Selection advice
Quick comparison
waggle standardizes share-by-reference handoffs across coding harnesses. Composio and Arcade.dev focus on SaaS tool catalogs and authorized MCP runtimes rather than artifact handoff receipts.
| waggle | Composio | Arcade.dev | |
|---|---|---|---|
| Best for | Auditable multi-agent handoffs of files and plans over MCP | Connecting agents to many SaaS apps with managed auth | Production MCP tool authorization and permission boundaries |
| Primary surface | Local MCP server + CLI tokens backed by SQLite | Managed toolkits, OAuth, and agent SDK integrations | MCP runtime with auth, permissions, and audited execution |
| Tradeoff | Handoff/reference layer, not a SaaS connector catalog | Broad SaaS coverage vs less focus on handoff receipts | Strong auth runtime vs no mint/resolve artifact tokens |
Best for
- multi-agent handoffs
- read/coverage receipts
- MCP-native coding harnesses
- local-first reference tokens
Not ideal for
- teams that only need SaaS connector catalogs
- projects that never delegate context across agents
- environments that cannot run a local MCP binary or daemon
Core concepts
Minimal implementation shape
Install with `brew install modiqo/homebrew-tap/waggle-cli`, run `claude mcp add waggle -- waggle serve --stdio`, mint a snapshot with `waggle mint --target file://$PWD/plan.md --snapshot`, then hand the returned token to a subagent to `resolve` / `read` / `search`.