Ext Ops Panel
Open dashboard
Comparison

Funplay Cocos MCP vs io.github.dockndevai/mcp-android

Funplay Cocos MCP is an MCP server published by FunplayAI. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.dockndevai/mcp-android is an MCP server published by dockndevai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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

Where each is published
MarketplaceFunplay Cocos MCPio.github.dockndevai/mcp-android
Official MCP Registry Listed
Version: 0.6.8
Downloads/month (npm): 1 478
Downloads/week (npm): 117
Forks (GitHub): 43
Stars (GitHub): 346
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.6.8
Downloads/month (npm): 1 478
Downloads/week (npm): 117
Forks (GitHub): 43
Stars (GitHub): 346
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

Funplay Cocos MCP vs io.github.dockndevai/mcp-android
FactFunplay Cocos MCPio.github.dockndevai/mcp-android
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)346 (better)0 (worse)
Forks (GitHub) (differs)43 (better)0 (worse)
Last release (differs)2026-10-20Not published
Where it runs (differs)On your machine (funplay-cocos-mcp)On your machine (@dockndevai/mcp-android)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 010, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/funplayai/funplay-cocos-mcpgithub.com/dockndevai/mcp-android
Changes in the last 7 days22
First seen (differs)2026-10-112026-10-14

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

Funplay Cocos MCP

In its own words, on Official MCP Registry:

stdio bridge for the local Cocos Creator Editor MCP server from FunplayAI/funplay-cocos-mcp.

io.github.dockndevai/mcp-android

In its own words, on Official MCP Registry:

Control Android devices over ADB from AI agents — safe-by-default, read-only by default, audited.

How to run each

Funplay Cocos MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio funplay-cocos-mcp -- npx -y funplay-cocos-mcp

io.github.dockndevai/mcp-android As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-android -- npx -y @dockndevai/mcp-android

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Funplay Cocos MCP asks for

  • FUNPLAY_COCOS_MCP_TIMEOUT_SECONDS
  • FUNPLAY_COCOS_MCP_URL

Only io.github.dockndevai/mcp-android asks for

  • ANDROID_ADB_PATH
  • ANDROID_ALLOW_INSTALL
  • ANDROID_ALLOW_SHELL
  • ANDROID_AUDIT_LOG
  • ANDROID_DRY_RUN
  • ANDROID_MODE
  • ANDROID_PACKAGE_ALLOWLIST
  • ANDROID_PROTECTED_PACKAGES
  • ANDROID_SERIAL
  • ANDROID_TIMEOUT_MS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Funplay Cocos MCP · What it can do: io.github.dockndevai/mcp-android · Compare two other plugins

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.

Where the data comes from: how the catalog is built