Seedance by Ace Data Cloud vs io.importly/importly-mcp
Seedance by Ace Data Cloud is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.importly/importly-mcp is an MCP server published by importly.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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.7.0 Downloads/month (PyPI): 5 170 Downloads/week (PyPI): 429 Forks (GitHub): 1 Stars (GitHub): 21 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 105 Downloads/week (npm): 47 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 2026.11.1.1 Downloads/month (PyPI): 5 170 Downloads/week (PyPI): 429 Forks (GitHub): 1 Stars (GitHub): 21 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 | Seedance by Ace Data Cloud | io.importly/importly-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 21 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-11-07 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (importly-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/acedatacloud/seedancemcp | github.com/yyildiz/importly-mcp |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 401 | 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
Seedance by Ace Data Cloud
Generate Seedance videos with Ace Data Cloud; retrieve the original task for finished video.
io.importly/importly-mcp
Download, transcribe, and get metadata for any video/audio URL. Managed yt-dlp + speech-to-text.
How to run each
Seedance by Ace Data Cloud As a remote MCP server
claude mcp add --transport http mcp-seedance https://seedance.mcp.acedata.cloud/mcp
Requires: ACEDATACLOUD_API_TOKEN (secret)
io.importly/importly-mcp As a local MCP server: npm package
claude mcp add --env "IMPORTLY_API_KEY=<YOUR_IMPORTLY_API_KEY>" --transport stdio importly-mcp -- npx -y importly-mcp
Requires: IMPORTLY_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Seedance by Ace Data Cloud 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 Seedance by Ace Data Cloud asks for
ACEDATACLOUD_API_TOKEN (secret)
Only io.importly/importly-mcp asks for
IMPORTLY_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Seedance by Ace Data Cloud · What it can do: io.importly/importly-mcp · 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.