Agent Comms vs p-e relay (remote)
Agent Comms is an MCP server published by ExaDev. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). p-e relay (remote) is an MCP server published by it-start. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Agent Comms |  p-e relay (remote) |
|---|---|---|
| Official MCP Registry | Listed Version: 8.13.20 Downloads/month (npm): 46 698 Downloads/week (npm): 3 230 Forks (GitHub): 9 Stars (GitHub): 30 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Agent Comms | p-e relay (remote) |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 30 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 9 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (agent-comms) | Remote server (relay.zae.life/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 15 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/exadev/agent-comms | github.com/it-start/relay-ui |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Agent Comms
Cross-harness communication mesh for LLM agents — rooms, DMs, presence, and visibility over TCP
p-e relay (remote)
Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed.
How to run each
Agent Comms As a local MCP server: npm package
claude mcp add --transport stdio agent-comms -- npx -y agent-commsp-e relay (remote) As a remote MCP server
claude mcp add --transport http relay-ui https://relay.zae.life/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Agent Comms · What it can do: p-e relay (remote) · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.