Summer Engine vs Computer Use Turbo
Summer Engine is an MCP server published by SummerEngine. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). Computer Use Turbo is an MCP server published by afaaq-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |   Summer Engine |  Computer Use Turbo |
|---|---|---|
| Official MCP Registry | Listed Version: 4.5.0 Forks (GitHub): 8 Stars (GitHub): 88 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 377 Downloads/week (npm): 41 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 2.5.1 Forks (GitHub): 8 Stars (GitHub): 88 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 | Summer Engine | Computer Use Turbo |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 88 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 8 (better) | 0 (worse) |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (computer-use-turbo) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 83 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/summerengine/summer | github.com/afaaq-io/computeruseturbo |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | 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
Summer Engine
The game engine built for AI. Any agent makes a multiplayer game and publishes it.
Computer Use Turbo
Let any AI agent operate desktop apps on macOS, Windows and Linux, in the background and safely.
How to run each
Summer Engine As a remote MCP server
claude mcp add --transport http summer https://mcp.summerengine.com/mcpComputer Use Turbo As a local MCP server: npm package
claude mcp add --transport stdio computer-use-turbo -- npx -y computer-use-turboCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Summer Engine 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Summer Engine · What it can do: Computer Use Turbo · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.