@felores/kie-ai-mcp-server vs io.github.runapi-builder/runapi-mcp
@felores/kie-ai-mcp-server is an MCP server published by felores. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.runapi-builder/runapi-mcp is an MCP server published by runapi-builder. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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 |  @felores/kie-ai-mcp-server |  io.github.runapi-builder/runapi-mcp |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 5.5.0 Downloads/month (npm): 6 200 Downloads/week (npm): 3 458 Forks (GitHub): 18 Stars (GitHub): 83 Not marked · First seen |
Listed Version: 0.17.0 Downloads/month (npm): 1 844 Downloads/week (npm): 672 Forks (GitHub): 0 Stars (GitHub): 56 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.17.0 Downloads/month (npm): 1 844 Downloads/week (npm): 672 Forks (GitHub): 0 Stars (GitHub): 56 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 | @felores/kie-ai-mcp-server | io.github.runapi-builder/runapi-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 83 (better) | 56 (worse) |
| Forks (GitHub) (differs) | 18 (better) | 0 (worse) |
| Last release (differs) | 2026-10-28 (worse) | 2026-10-29 (better) |
| Where it runs (differs) | On your machine (@felores/kie-ai-mcp-server) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/felores/kie-cli-mcp | github.com/runapi-ai/mcp |
| Changes in the last 7 days (differs) | 1 | 4 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-25 |
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
@felores/kie-ai-mcp-server
MCP server for Kie.ai APIs: image, video, music and speech generation across Nano Banana, Veo3, Suno, ElevenLabs, ByteDance, Qwen, Runway, Midjourney, Wan, MiniMax H3, Kling, GPT Image 2, Flux Kontext, Recraft, Ideogram, Topaz, HappyHorse and more.
io.github.runapi-builder/runapi-mcp
130+ AI models for image, video, music, and audio — 18 model families, one RunAPI account.
How to run each
@felores/kie-ai-mcp-server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.runapi-builder/runapi-mcp As a remote MCP server
claude mcp add --transport http runapi-mcp https://mcp.runapi.ai/mcpRequires: RUNAPI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.runapi-builder/runapi-mcp 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
The marketplaces of @felores/kie-ai-mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: @felores/kie-ai-mcp-server · What it can do: io.github.runapi-builder/runapi-mcp · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.