GrowBlocks Dev Kit

xyz.growblocksPublished by growblocks.xyzv1.2.0Updated Oct 25, 2026

Build, play-test with screenshots, and ship three.js browser games on GrowBlocks.

The publisher's own server: Blocks

Overview

AI-generated overview

A local MCP server that lets an AI assistant scaffold, play-test with screenshots, and upload three.js browser games to the GrowBlocks platform.

What you can do
Read the Dev Kit API documentation and starter resources for building games with three.js and Rapier physics, and create a new game folder from the starter kit. Run static checks, or play the game headless and return a screenshot after each change. Find, inspect and add published blocks from other developers. Sign in, create or link a game on GrowBlocks, and set its name, logo and details. Upload an unlisted test build with a shareable link, check build status and review notes, and submit for review or publish a block when asked.
When to use it
Useful when you want an assistant to build and iterate on a GrowBlocks browser game, verify changes visually through headless play-testing, and push private test builds for sharing before submitting for review.
Requirements
Runs locally over stdio via the npm package growblocks (npx), so Node.js is needed. Desktop clients only; a Claude Code plugin and a Claude Desktop extension are also offered. Signing in uses a code confirmed in the browser; no API keys or environment variables are declared.
Before you install
Signs in to a GrowBlocks account and creates or updates games on the platform. Uploads test builds and, when explicitly asked, submits games for review or publishes blocks, which makes content public after GrowBlocks review. Adding published blocks means their authors earn when the game ships. Payments and earnings stay in the browser, not through the assistant.

Installation

In SourceWeft

  1. Open GrowBlocks Dev Kit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

GrowBlocks Dev Kit for Claude, Cursor and other AI assistants

Make a browser game with an AI assistant and ship it on GrowBlocks: three.js, Rapier physics, characters, multiplayer rooms and hosting, with no setup.

The assistant reads the API, writes game.js, plays the game headless and looks at a screenshot after every change, reuses parts other developers published (blocks), and pushes an unlisted test build you can share. Nothing goes public until you submit it and GrowBlocks reviews it.

Install

Claude Code (plugin: tools + skill)

/plugin marketplace add Gioluan/growblocks-devkit/plugin install growblocks@growblocks

Claude Code (just the MCP server)

claude mcp add growblocks -- npx -y growblocks mcp

Claude Desktop: download growblocks.mcpb from the latest release and open it.

Cursor / Windsurf / any MCP client

json
{ "mcpServers": { "growblocks": { "command": "npx", "args": ["-y", "growblocks", "mcp"] } } }

Terminal: npx growblocks new my-game, then npx growblocks help.

Then ask: "Make me a GrowBlocks game where frogs race across lily pads", or use the make_game prompt.

Tools

ToolWhat it does
growblocks_docsThe Dev Kit API (or one section of it)
growblocks_checkStatic checks; with play it plays the game headless and returns a screenshot
growblocks_new_gameA new game folder from the starter kit
growblocks_blocks, growblocks_block_info, growblocks_add_blockFind and add published blocks (their authors earn when your game ships them)
growblocks_login, growblocks_whoamiSign in with a code you confirm in your browser
growblocks_create_game, growblocks_link_game, growblocks_update_gameMake the game on GrowBlocks and set its name, logo and details
growblocks_pushUpload an unlisted test build and get its link
growblocks_status, growblocks_gamesBuilds, links and the review note
growblocks_submit, growblocks_publish_blockOnly when you ask: submit for review, publish a block

Every tool takes dir, the game folder. Prompts: make_game, ship_game. Resources: llms.txt, gb.d.ts.

Money (collections, the coin, earnings) never goes through the assistant: it stays in your browser at growblocks.xyz. Developers keep 70% of the fees their game generates.

Layout

  • .claude-plugin/marketplace.json: this repo as a Claude Code plugin marketplace
  • plugins/growblocks/: the plugin (.mcp.json runs npx [email protected] mcp, pinned so every install runs the reviewed version, plus the growblocks-game skill)
  • desktop/: the Claude Desktop extension; build it with npx @anthropic-ai/mcpb pack desktop growblocks.mcpb
  • server.json: the entry for the official MCP Registry
  • TERMS.md: the Dev Kit terms

The server is one dependency-free file, growblocks.mjs, published on npm as growblocks.

Source: README.md at commit e06e2c9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.0LatestOct 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Blocks integrations