Ext Ops Panel
Open dashboard
Comparison

notify-sounds vs Heard

notify-sounds is a plugin bundle for AI coding tools published by AxGord. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Heard is an MCP server published by heard.dev. 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

Where each is published
Marketplacenotify-soundsHeard
Claude Code: claude-plugins-community Listed
Version: 0.1.4
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.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

notify-sounds vs Heard
Factnotify-soundsHeard
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.heard.dev/v1/mcp/agent)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/axgord/claude-notify-soundsgithub.com/heardlabs/heard-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 34 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

notify-sounds

In its own words, on Claude Code: claude-plugins-community:

Plays system sounds in Claude Code when a task finishes or when permission is needed, so you don't have to keep watching the terminal. Cross-platform: macOS (afplay), Linux (PulseAudio/PipeWire), Windows (PowerShell SoundPlayer), with terminal-bell fallback. Sub-agent stops are skipped to avoid noise during multi-agent workflows.

Heard

In its own words, on Official MCP Registry:

Let cloud agents talk to you: progress updates spoken on your Mac, and replies you send back.

How to run each

notify-sounds As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install notify-sounds@claude-community

Heard As a remote MCP server

Claude Code
claude mcp add --transport http heard https://api.heard.dev/v1/mcp/agent

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Heard 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: notify-sounds · What it can do: Heard · 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.

Where the data comes from: how the catalog is built