cc-hooks-plugin vs PyAI Voice AI
cc-hooks-plugin is a plugin bundle for AI coding tools published by Husni Adil Makmur. Marketplaces we read that list it: 1 (Community GitHub marketplaces). PyAI Voice AI is an MCP server published by atomsai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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 | ||
|---|---|---|
| Community marketplace husniadil/cc-hooks | Listed Version: 1.1.0 Forks (GitHub): 4 Stars (GitHub): 19 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.1 Downloads/month (npm): 76 Downloads/week (npm): 181 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.5.1 Downloads/month (npm): 76 Downloads/week (npm): 181 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 | cc-hooks-plugin | PyAI Voice AI |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 19 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-24 |
| 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 | Not published | Not published |
| Hooks it runs (differs) | 9 | Not published |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/husniadil/cc-hooks | github.com/atomsai/pyai-platform-backend |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days 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
cc-hooks-plugin
Audio feedback system with multilingual TTS announcements, AI-powered contextual messages, and sound effects for Claude Code. Features include: prerecorded sounds (offline), Google TTS (free), ElevenLabs (premium), contextual AI completion messages via OpenRouter, multi-language support, granular silent modes, and multi-instance support for concurrent sessions.
PyAI Voice AI
User-approved phone calls, speech, transcription and voice agents with PyAI OAuth.
How to run each
cc-hooks-plugin As a Claude Code plugin
/plugin marketplace add husniadil/cc-hooks
/plugin install cc-hooks-plugin@cc-hooks-pluginPyAI Voice AI As a remote MCP server
claude mcp add --transport http pyai https://api.pyai.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PyAI Voice AI 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: cc-hooks-plugin · What it can do: PyAI Voice AI · 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. 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.