Summer Engine vs Craftwire
A side-by-side look at the Summer Engine and Craftwire MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Summer Engine for gaming work as a local process; choose Craftwire for gaming as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Summer Engine when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
Choose Craftwire when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_instances, get_request_status, wait_for.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 45/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 88 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 35 |
| Full listing | View Summer Engine | View Craftwire |
Tools & capabilities
Summer Engine tools
No tool names declared yet. Check the project README from the listing page.
Craftwire tools 35
list_instancesList connected Minecraft clients and servers (id, name, versions, tools added by plugins or mods). Call this first.get_request_statusStatus of a request sent with an operationId: unknown, running, done (with result) or failed (with error). Kept 5 minutes.wait_forWait until something happens (after the call). Events: chat_match, hud_match, screen_open, screen_closed, log_match, player_join {pattern}. Server, every tick: block, player_near, inventory, event, message, expr {js}. Returns what held and its value. Details: craftwire://docs/tools.player_stateLocal player: position, rotation, health, game mode, dimension, hotbar slot, inventory, crosshair target.hud_readRead the HUD as text: bossbars, actionbar, title, sidebar (lines as drawn), tab list (header, footer, players), belowName.gui_readDescribe the open screen: title, slots (item, count, name, lore), hovered tooltip, widgets. {open:false} when none is open.gui_actionAct on the open screen: hover/click/right_click/shift_click {slot}, drag {slot,toSlot}, click_widget {widget}, type {text}, close. Returns the new gui_read.inputGameplay input with no screen open: keys (forward, back, left, right, jump, sneak, sprint, attack, use, pick, drop, inventory, swap_hands, chat, command, ...) with mode press|hold|release; look adds yaw/pitch; hotbar 1-9.cameraMove the render camera, not the player: set, look_at {target}, frame_area {area}, frame_entity {entity}, freecam_on/off, reset; path {keyframes}/orbit {center,radius} play over time. Details: craftwire://docs/video.client_settingsRead or set guiScale, fov, renderDistance, hideHud, windowSize; no arguments only reads.screenshotCapture the game frame. hud/chat:false hide them; maxSize: long edge; savePath writes full size (.png/.jpg); camera: this shot only. layer gui|tooltip|gui+tooltip: transparent PNG of the open menu (craftwire://docs/gui-capture).recordRecord a video with sound through the user's ffmpeg. start {savePath, preset max|high|balanced|light, durationMs?, camera? (a camera tool path/orbit motion), wait?}; stop; status. layer gui|tooltip|gui+tooltip: transparent .mov/.webm. Details: craftwire://docs/video.- +23 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Summer Engine
{
"mcpServers": {
"summer-2": {
"command": "npx",
"args": [
"-y",
"summer-engine@latest"
]
}
}
}
Craftwire
{
"mcpServers": {
"craftwire": {
"command": "npx",
"args": [
"-y",
"craftwire"
]
}
}
}
Frequently asked questions
Summer Engine is categorized under Gaming and uses a local stdio subprocess. Craftwire belongs to Gaming and uses a local stdio subprocess. Pick Summer Engine for gaming work and Craftwire for gaming.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Summer Engine has no declared pricing — check the project's own site. Craftwire has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add summer-2 and craftwire as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Summer Engine has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 88 GitHub stars. Craftwire has 63/100 (Good) with 3 views, 0 installs and 2 GitHub stars.