claude-code-notify vs io.github.PhoenixFeuer32/claude-context-bridge
claude-code-notify is a plugin bundle for AI coding tools published by decko. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.PhoenixFeuer32/claude-context-bridge is an MCP server published by PhoenixFeuer32. 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 |  claude-code-notify | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: f5cfb77 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.0 No figure published 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 | claude-code-notify | io.github.PhoenixFeuer32/claude-context-bridge |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (claude-context-bridge.fly.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/decko/claude-code-notify | github.com/phoenixfeuer32/claude-context-bridge |
| 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 43 h ago, requires a key |
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
claude-code-notify
claude-code-notify sends a desktop notification whenever Claude Code finishes responding, so you never miss a prompt while working across multiple sessions. Each notification shows your session name (from /rename) and the first 80 characters of Claude's last response, giving you context at a glance. When running in tmux, the notification includes the window index so you know exactly where to switch. The plugin is focus-aware: if you're already looking at the Claude session (detected via tmux pane, window, and terminal focus state), the notification is suppressed. On macOS without tmux, it checks whether your terminal app is frontmost. A 5-second debounce prevents notification spam during rapid tool calls. Works on Linux (notify-send) and macOS (osascript). Requires jq and bash 4+. tmux is optional but recommended for the best experience. Configuration is zero-config by default, with two optional environment variables: CLAUDE_NOTIFY_CONTEXT (adds a Work/Personal prefix) and CLAUDE_NOTIFY_URGENCY (sets notifica
io.github.PhoenixFeuer32/claude-context-bridge
Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.
How to run each
claude-code-notify As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-code-notify@claude-communityio.github.PhoenixFeuer32/claude-context-bridge As a remote MCP server
claude mcp add --transport http claude-context-bridge https://claude-context-bridge.fly.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.PhoenixFeuer32/claude-context-bridge 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: claude-code-notify · What it can do: io.github.PhoenixFeuer32/claude-context-bridge · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.