Summer Engine vs Balatro Agent

A side-by-side look at the Summer Engine and Balatro Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Summer Engine logoSummer EngineGaming · Local subprocess (stdio)MCP server, CLI and skills that let AI agents build, test and publish games with the Summer Engine game engine.45FairAuth: not declaredBalatro Agent logoBalatro AgentGaming · Local subprocess (stdio)MCP server connecting AI agents to play Balatro67GreatAuth: no auth required

Verdict: choose Summer Engine for gaming work as a local process; choose Balatro Agent for gaming as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Summer Engine logoChoose Summer Engine when

  • You need dedicated capabilities in the Gaming domain.
  • You prefer a local stdio subprocess transport.
Explore Summer Engine

Balatro Agent logoChoose Balatro Agent when

  • You need dedicated capabilities in the Gaming domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like connect, disconnect, balatro_select_blind.
Explore Balatro Agent

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSummer Engine logoSummer EngineBalatro Agent logoBalatro Agent
CategoryGamingGaming
Quality signal45/100 · Fair67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars8821
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed27

Tools & capabilities

Summer Engine tools

No tool names declared yet. Check the project README from the listing page.

Balatro Agent tools 27

  • connectConnect to a live Balatro instance and keep its bridge socket open. Read balatro://instances for the current indices and pass instance_index, or omit it when exactly one instance is running. Connecting changes no default: actions and live resources address instances by instance_index and open their own sockets on demand.
  • disconnectRelease the bridge socket held for a live Balatro instance. Read balatro://instances for the current indices and pass instance_index, or omit it when exactly one instance is running. Nothing else changes: later actions and resource reads reconnect on demand.
  • balatro_select_blindSelect the current blind to begin the round.
  • balatro_skip_blindSkip the current blind, forfeiting its cash reward in exchange for a tag reward.
  • balatro_play_handPlay the selected cards as a poker hand, scoring them against the blind's chip target.
  • balatro_discard_handDiscard the selected cards and draw replacements, consuming one discard for the round.
  • balatro_reroll_shopReroll the shop offerings, spending the current reroll cost.
  • balatro_reroll_bossReroll the upcoming Boss Blind for $10 during blind selection. Requires Director's Cut (once per Ante) or Retcon (unlimited rerolls), sufficient spendable money, and no reroll already in progress.
  • balatro_leave_shopLeave the shop to end the round.
  • balatro_cash_outCash out round-end rewards.
  • balatro_skip_boosterClose an open booster pack, forfeiting remaining picks.
  • balatro_restartRestart the current run with the same deck, stake, and seed.
  • +15 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "summer-2": {
      "command": "npx",
      "args": [
        "-y",
        "summer-engine@latest"
      ]
    }
  }
}

Balatro Agent

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "balatro-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "balatro-mcp"
      ]
    }
  }
}

Frequently asked questions

Summer Engine is categorized under Gaming and uses a local stdio subprocess. Balatro Agent belongs to Gaming and uses a local stdio subprocess. Pick Summer Engine for gaming work and Balatro Agent 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. Balatro Agent is listed as free. Auth: no auth required. 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 balatro-mcp 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. Balatro Agent has 67/100 (Great) with 4 views, 0 installs and 21 GitHub stars.