Plugged.in Proxy vs discord-bridge
discord-bridge is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). discord-bridge is a plugin bundle for AI coding tools published by chrismdemian. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-19. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 35 876 Stars (Docker Hub): 3 Stars (GitHub): 136 Not marked · First seen |
Not listed |
| Community marketplace chrismdemian/claude-code-discord-bridge | Not listed | Removed on 2026-10-16 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 2 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 | Plugged.in Proxy | discord-bridgeno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 136 | 2 |
| Pulls (Docker Hub) (differs) | 35 876 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 2, secrets among them: 0 |
| Hooks it runs (differs) | Not published | 17 |
| Parts of the bundle (differs) | Not a bundle | 21 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/chrismdemian/claude-code-discord-bridge |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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 discord-bridge
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Discord messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /discord:access.
-
Discord plugin for Claude Code with per-session thread routing. Fork of the official Discord plugin with added support for session-isolated threads and full permission context in…
-
Show your Claude Code status in Discord with Rich Presence.
-
Caller-owned Discord operations for AI agents with 222 typed tools and verifiable guild builds.
-
omnicord io.github.OrygnsCode/omnicord
Discord server management MCP for AI agents: chat, moderation, admin, and full server building.
-
cursor-chat-bridge io.github.udah1/cursor-chat-bridge
Drive the Cursor agent from Telegram, Discord, or GitHub — with images and voice notes.
What each says it does
Plugged.in Proxy
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 servers from a single connection point with RAG capabilities and real-time notifications.
discord-bridge
Control Claude Code from your phone via Discord. Full session mirroring, bidirectional messaging, permission approval. Auto-discovers all running instances.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxy
Requires: PLUGGEDIN_API_KEY (secret)
discord-bridge
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of discord-bridge publish no list of tools, so we do not compare tools.
Settings each asks for
Only Plugged.in Proxy asks for
PLUGGEDIN_API_BASE_URLPLUGGEDIN_API_KEY (secret)
Only discord-bridge asks for
BRIDGE_PORTPLUGIN_DATA
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Plugged.in Proxy · What it can do: discord-bridge · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.