convez.ai
MCP ServerIntegração & APIsIntermediário
jordanspilgrim

Dead Letter Box (DLB) MCP

jordanspilgrim/dlb-mcp

Mensageria assíncrona entre agentes IA sem daemon

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP minimalista para mensageria entre sessões de agentes IA independentes. Oferece semântica real de fila com entrega garantida mesmo para destinatários não-existentes, sem daemon ou orquestração pesada.

Instalação

$npx convez-ai jordanspilgrim/dlb-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 6 dias
Versão
v0.6.2
Issues abertas
0
Contribuidores
1

Casos de uso

  • Coordenação entre múltiplas sessões Claude Code/Cursor em terminais diferentes
  • Fila de mensagens persistente entre agentes independentes
  • Troca de estado e contexto entre workflows desacoplados

Veredito

Solução focada e enxuta para comunicação inter-agentes. DLB preenche um gap específico (múltiplas sessões coordenadas) com excelente economia de complexidade — apenas 6 ferramentas, sem overhead de daemon. Ideal para quem precisa de messaging simples e local entre agentes; não substitui frameworks de orquestração pesada.

README

A tradução para o português deste README ainda está na fila.

DLB — Dead Letter Box

PyPI CI Python License

A tiny MCP server that lets independent AI-agent sessions leave each other notes. Fire-and-forget. Queued for non-existent recipients. No daemon. Six tools.

Why

If you've ever had two Claude Code / Cursor / Codex sessions running in different terminals and wished they could coordinate, you've hit the gap DLB fills. Existing options (mcp_agent_mail, agent frameworks like CrewAI/AutoGen) either bundle too much (40+ tools, contact policies, file leases) or only work inside a single parent process.

DLB does one thing: messages between agent sessions. It does NOT do orchestration, contact handshakes, file reservations, push notifications, web hosting, or auto-name-generation. If you want those, you want a different tool.

Five differentiators (vs. mcp_agent_mail and friends)

  1. 6 tools — fits cleanly in Claude Code's tool list without crowding out the builtins.
  2. No daemon — each MCP call opens SQLite, runs one transaction, closes. No server.lock, no port management.
  3. Names accepted as-is — call yourself alpha, ThreadBeta, worker-1. DLB will not rename you.
  4. Real dead-letter semantics — send(to="ghost") succeeds and queues the message; if/when someone registers as ghost, the messages are waiting.
  5. Zero ceremony — send works on call one. Registration is optional and observational.

Install

Zero-install (recommended — uvx fetches and runs on demand):

uvx dlb-mcp

Or install once:

uv tool install dlb-mcp

Wire into Claude Code

Add to ~/.claude.json:

{
  "mcpServers": {
    "dlb": {
      "type": "stdio",
      "command": "uvx",
      "args": ["dlb-mcp"]
    }
  }
}

Multiple sessions can coexist — they all share ~/.dlb/store.sqlite3 via SQLite WAL mode.

The 6 tools

ToolWhat it does
register(name, working_on=None, force=False)Declare a name + status. Returns session_token. Conflict on existing active name → error with suggestion.
list_threads(active_within="24h")See who's around. No auth.
send(to, body, subject=None, from_=None)Drop a message. Always succeeds — even if to doesn't exist yet.
read(name, session_token, unread_only=True, limit=20)Read inbox. Requires session_token for registered names.
ack(message_id, session_token)Explicit "I saw this and acted on it". Optional.
unregister(name, session_token)Release the name. Messages preserved for re-registration.

That's the entire API.

Configuration

Env varDefaultWhat
DLB_STORE~/.dlb/store.sqlite3Path to the SQLite store
DLB_MESSAGE_TTL_DAYS7Days before unread messages expire

Security model

  • Local-only. File permissions (~/.dlb/ is chmod 700) are the boundary.
  • Send is open. Anyone can drop messages in any inbox. By design — DLB is a relay.
  • Read is gated. Once a name is registered, only the holder of that session's token can read it.
  • No TLS, no accounts, no cross-host. If you need those, you want a different tool.

What DLB is NOT

  • Not an orchestrator. Use a script + your LLM SDK if you need to spawn agents.
  • Not a web service. Local only.
  • Not Gmail. No threading, replies, CC/BCC, attachments, contacts, importance flags.
  • Not a file-coordination tool. No file leases or advisory locks.
  • Not push. Polling-only — call read when you want to check.

If you find yourself wishing for any of these, that's a signal to use a different tool, not to ask DLB to grow.

License

MIT.

Ver o original no GitHub

Bom para

Relacionados