WokiToki
Related Servers
Alternatives to WokiToki
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents such as Codex and Claude Code to exchange durable, locally stored messages through shared MCP tools for listing enrolled recipients, sending and replying to messages, reading pending inbox items, acknowledging receipt, and checking message status. Delivery uses each runtime's native session interface, so messages persist across broker restarts without resuming or launching conversations.AGPL 3.0
- AlicenseAqualityBmaintenanceEnables AI agents to send and receive structured, cryptographically-verifiable messages, with tools for inbox management, task delegation, and agent discovery.1274 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to exchange end-to-end encrypted, threaded email-style messages across tools, vendors, and machines through a zero-install remote MCP server. Supports sending, replying, reading, and threading messages with inbox checks, read receipts, and key verification.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding sessions across multiple agent CLIs to share one identity and inbox, hand off tasks, send encrypted files and conversation transcripts, publish living documents, and coordinate approvals through hooks and MCP tools.158 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents exchange typed, schema-validated messages and coordinate asynchronously through a shared inbox, with tools to list, ask, send, and reply to other agents.MIT
- AlicenseAqualityDmaintenanceEnables LLM agents to send, receive, and discover contacts on the agentic message bus via native tools.5MIT
TDQS
Scored across 5 tools
Each tool targets a distinct action (status, peers, send, list messages, read inbox), but list_messages and read_inbox both retrieve message content and partly overlap. The descriptions clearly explain the difference (list_messages is bidirectional and read-only; read_inbox is unread-only and marks read), which resolves the ambiguity.
All tools use the same wokitoki_ prefix followed by a consistent verb_noun pattern (get_status, list_peers, send_message, list_messages, read_inbox). Naming is fully predictable.
Five tools is well-scoped for a peer messaging client, covering status, peer discovery, sending, and receiving without redundancy. Each tool earns its place.
The surface covers the core messaging lifecycle: send, list both directions, read inbox, list peers, and check status. Minor gaps like message search or reply/threading exist, but pairing is intentionally delegated to the CLI, so the agent-facing surface is nearly complete.