agent-bridge vs LMCP
agent-bridge is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
agent-bridge is a plugin bundle for AI coding tools published by EthanSK. No marketplace we read lists it any more. LMCP is an MCP server published by local-mcp.com. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   LMCP | |
|---|---|---|
| Community marketplace ethansk/agent-bridge | Removed on 2026-10-26 Version: 4.10.0 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.0.427 Downloads/month (npm): 10 964 Downloads/week (npm): 1 023 Forks (GitHub): 12 Stars (GitHub): 73 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 3.0.426 Downloads/month (npm): 10 964 Downloads/week (npm): 1 023 Forks (GitHub): 12 Stars (GitHub): 73 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-bridgeno longer listed · | LMCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 4 |
| Stars (GitHub) (differs) | 10 | 73 |
| Forks (GitHub) (differs) | 1 | 12 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 0 | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | 16 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/ethansk/agent-bridge | github.com/colibird-ai/local-mcp-releases |
| Changes in the last 7 days (differs) | 2 | 9 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-28 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of agent-bridge
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Strale agent skills with remote MCP connector for Strale platform integration.
-
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP…
-
Build, remix, and run apps with agents on Robutler. Search, delegate, post, chat, manage channels.
-
X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router
Single-connection MCP gateway discovering and executing 490+ verified MCP & A2A tools.
-
Read-only Exeris context for AI agents: ADRs, SDK contract, build output, kernel diagnostics.
-
agent-comm io.github.keshrath/agent-comm
Agent intercommunication - messaging, channels, shared state, and real-time events
What each says it does
agent-bridge
Unified agent-bridge MCP server: 13 outbound tools (bridge_send_message / bridge_notify / bridge_learnings_add / bridge_learnings_search / bridge_receive_messages / bridge_run_command / bridge_status / bridge_list_machines / bridge_clear_inbox / bridge_inbox_stats / bridge_codex_bind / bridge_codex_unbind / bridge_codex_status) plus the inbound channel watcher that pushes incoming messages from paired machines into the running session as <channel source="agent-bridge"> events.
LMCP
Mac & Windows: let ChatGPT, Claude & Cursor use your email, calendar, iMessage, Teams, files.
How to run each
agent-bridge
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
LMCP As a remote MCP server
claude mcp add --transport http local-mcp https://local-mcp.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only LMCP 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
Only agent-bridge asks for
AGENT_BRIDGE_PERSONA
Only LMCP asks for
LMCP_REF
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: agent-bridge · What it can do: LMCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.