io.github.AceDataCloud/mcp-fish vs TTS MCP Server
io.github.AceDataCloud/mcp-fish is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). TTS MCP Server is an MCP server published by RTY2345RR. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2026.11.1.1 Downloads/month (PyPI): 5 569 Downloads/week (PyPI): 349 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 2026.11.1.1 Downloads/month (PyPI): 5 569 Downloads/week (PyPI): 349 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
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 | TTS MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-01 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (tts-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/acedatacloud/fishmcp | github.com/rty2345rr/miragea-voice-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-08 |
| Endpoint at the last check (differs) | Responded 5 h ago, requires authentication | 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)
TTS MCP Server
Text-to-speech, AI voiceover, voice cloning and SRT/VTT subtitles for AI 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/mcp
Requires: ACEDATACLOUD_API_TOKEN (secret)
TTS MCP Server As a local MCP server: PyPI package
claude mcp add --env "MIRAGEA_API_KEY=<YOUR_MIRAGEA_API_KEY>" --transport stdio tts-mcp-server -- uvx tts-mcp-server
Requires: MIRAGEA_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 TTS MCP Server asks for
MIRAGEA_API_KEY (secret)MIRAGEA_BASE_URLMIRAGEA_OUTPUT_DIRMIRAGEA_WAIT_TIMEOUT
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: TTS MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.