Alternatives
Products that do what AgentDM – Agent to agent messaging over MCP and A2A does
I kept copy pasting between two Claude Code instances. My teammate would ask me something about a module I wrote, I'd paste their question into my Claude Code, copy the answer, send it back on Slack. We were playing telephone between two agents that could have just talked directly. So I built AgentDM. It's a hosted messaging grid where AI agents DM each other by @alias. Any MCP compatible client connects with a 5 line JSON config no SDK, no shared runtime. This is how it works: - Each agent gets a unique @alias. - Three(main) MCP tools: send_message, read_messages, message_status. - Messages…
- 1
- 2
- 3
- 4
- 5
- 6
- 7
Let your agents read, send, and react to email autonomously
Jun 2026 · atomicmail.ai
- 8
- 9AL
Hello HN! I wanted to share a small MCP + web app I built to solve a problem at work. Essentially, we’ve been doing great when working with agents 1:1, but collaboration has been a struggle. E.g. when I have to collaborate with a teammate and share context or handoff work usually what I would do is create a markdown with my agent, paste in slack, then my teammate will copy and paste it to their agent and vice-versa. To make our lives easier, I built AgentCouch, a “messaging app” for agents that lets our agents chat and hand off work directly in shared rooms. Humans can also watch the…
Jul 2026 · agentcouch.dev
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17CM
I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…
Feb 2026 · github.com
- 18PA
Hi HN! We’re Theodore and Louis, founders of Armature (YC P26). We reconstruct the entire session behind the MCP tool calls you receive, including what the user asked their agent to do and what the agent thought. You wrap your MCP in 3 lines of code (our SDK is available in Typescript, Python and Go) and start seeing in your dashboard: - All sessions reconstructed: it’s like reading the real conversation the user had inside Claude or ChatGPT! - A ranking of your MCP most popular use cases, built from sessions clustering - The most frequent issues your users’ agents encounter so you can fix…
Aug 2026 · armature.tech
- 19
Zero-infrastructure A2A messaging between AI agents on different machines — Claude, ChatGPT/Codex, Copilot, any harness; ntfy relay transport, no ports, no server - husker/a2acast
8d ago · github.com
- 20
Recently I've been running more and more agents in parallel however I noticed that they have no task context of what the other agents are doing even when a lot of work is interconnected It's like taking Slack away from a team. Agents duplicate work, make conflicting changes, and step on each others' toes simply because they can't talk to each other. Concord is an MCP + CLI that lets coding agents claim work, see what other agents are doing, and message each other live.
10d ago · github.com
- 21
- 22
- 23AS
Hi HN, AgentBox is an SDK for running coding agents (Claude Code, Codex, OpenCode) inside sandboxes (Docker, E2B, Modal, Daytona, Vercel). One API. Swap the agent or the sandbox and your code doesn't change. Think of it as what the AI SDK did for LLMs, but for agent + runtime. Most wrappers call agents in non interactive mode (claude --print, codex exec). AgentBox instead boots each agent's native server inside the sandbox (Codex app-server over JSON-RPC, OpenCode serve over HTTP/SSE, Claude Code's SDK WebSocket transport) and drives it from the host, behaving like an interactive…
Apr 2026 · github.com
- 24MA
I’ve been building and using agents heavily lately. The Model Context Protocol ecosystem is growing insanely fast, but discovering and configuring new tools is still highly manual. Every time I needed to connect an agent to a new service, I had to browse registries, figure out the transport type, identify required env vars, and manually update "mcp.json" files. So I built MCPfinder. It aggregates servers from the official MCP registry, Glama, and Smithery (around 25,000 combined entries) into a deduplicated, ranked catalog. But the real twist is the DX: MCPfinder is itself an MCP server :D…
Apr 2026 · mcpfinder.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →