Funplay Cocos MCP
Funplay Cocos MCP is an MCP server published by FunplayAI; its MCP spec-revision support has not been verified yet. Last verified 2026-08-07.
Does Funplay Cocos MCP support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Funplay Cocos MCP supports (as of 2026-08-07).
Is Funplay Cocos MCP a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Funplay Cocos MCP (as of 2026-08-07).
How do I connect to Funplay Cocos MCP?
Funplay Cocos MCP is available via the package npm:funplay-cocos-mcp, the official MCP Registry under io.github.FunplayAI/funplay-cocos-mcp, the source repository at https://github.com/funplayai/funplay-cocos-mcp. Authentication: unknown. Transports: stdio.
When were Funplay Cocos MCP's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
stdio bridge for the local Cocos Creator Editor MCP server from FunplayAI/funplay-cocos-mcp.
How widely adopted is Funplay Cocos MCP?
Ranked #154 in The MCP 500 with Adoption Index 52.65 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 627 | API · |
| GitHub stars | 249 | API · |
| GitHub forks | 32 | API · |
| Last push | 2026-09-12T13:33:49Z | API · |
| Repository archived | no | API · |
Repository and package signals for Funplay Cocos MCP
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 0
- Primary language
- JavaScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Package (npm) as of
- Latest version
0.5.1- Last published
- First published
- Releases
- 12
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 0
- Unpacked size
- 652 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).