io.github.AceDataCloud/mcp-fish vs three.ws Audio
io.github.AceDataCloud/mcp-fish is an MCP server published by AceDataCloud. Marketplaces we read that list it: 1 (Official MCP Registry). three.ws Audio is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  io.github.AceDataCloud/mcp-fish |  three.ws Audio |
|---|---|---|
| Official MCP Registry | Listed Version: 2026.10.18.5 Downloads/month (PyPI): 5 569 Downloads/week (PyPI): 1 087 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (npm): 210 Downloads/week (npm): 42 Forks (GitHub): 66 Stars (GitHub): 241 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 | io.github.AceDataCloud/mcp-fish | three.ws Audio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 241 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 66 (better) |
| Last release (differs) | 2026-10-18 | Not published |
| Where it runs (differs) | Remote server (fish.mcp.acedata.cloud/mcp) | On your machine (@three-ws/audio-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/acedatacloud/fishmcp | github.com/nirholas/three.ws |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
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
io.github.AceDataCloud/mcp-fish
MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
three.ws Audio
Text-to-speech, speech-to-text, audio-to-face lipsync, and motion-capture clips for 3D agents.
How to run each
io.github.AceDataCloud/mcp-fish As a remote MCP server
claude mcp add --transport http mcp-fish https://fish.mcp.acedata.cloud/mcpRequires: ACEDATACLOUD_API_TOKEN (secret)
three.ws Audio As a local MCP server: npm package
claude mcp add --env "THREE_WS_API_KEY=<YOUR_THREE_WS_API_KEY>" --transport stdio audio-mcp -- npx -y @three-ws/audio-mcpRequires: THREE_WS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.AceDataCloud/mcp-fish 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 io.github.AceDataCloud/mcp-fish asks for
ACEDATACLOUD_API_TOKEN (secret)
Only three.ws Audio asks for
THREE_WS_API_KEY (secret)THREE_WS_BASETHREE_WS_TIMEOUT_MS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.AceDataCloud/mcp-fish · What it can do: three.ws Audio · Compare two other plugins
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.