RepoRelay vs p-e relay (remote)
RepoRelay is an MCP server published by Lukie-81. Marketplaces we read that list it: 1 (Official MCP Registry). 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-24. 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 |  RepoRelay |  p-e relay (remote) |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.5 Downloads/month (npm): 196 Downloads/week (npm): 26 Forks (GitHub): 11 Stars (GitHub): 29 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 | RepoRelay | p-e relay (remote) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 29 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 11 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (reporelay-mcp) | Remote server (relay.zae.life/api/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/lukie-81/reporelay | github.com/it-start/relay-ui |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 h ago |
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
RepoRelay
Bounded local MCP access to one approved repository for AI read/search and structured handoffs.
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
RepoRelay
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: <repository-root>
p-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.
Only p-e relay (remote) has a remote endpoint we check. How we check endpoints
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: RepoRelay · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.