MCP server, engine workspace & full source export
GameCrew isn’t a walled garden. Connect Claude Code, Cursor, VS Code or any Model Context Protocol client over Streamable HTTP to inspect and edit live engine workspaces, generate rigged 3D models, PBR textures and audio packs for local projects, browse or contribute engine techniques, submit fork merge requests, or export clean git-versioned Unity 6, Godot 4, Three.js and Pulse source code.
Connect in 60 seconds (Streamable HTTP MCP)
Create a personal access token (gc_…) on the studio Usage page, then add GameCrew to your coding assistant’s MCP configuration (supports MCP protocol versions 2025-06-18, 2025-03-26, 2024-11-05, no local daemon or SDK install required):
{
"mcpServers": {
"gamecrew": {
"type": "http",
"url": "https://play.gamecrew.ai/mcp",
"headers": {
"Authorization": "Bearer gc_your_access_token"
}
}
}
}
Two scoped token modes
Full workspace & studio builds (all)
Read, search, edit and diff project files, inspect offline Unity 6 / Godot 4 / Three.js / Pulse API symbols, run sandboxed engine compile & play-mode checks, launch builds, submit fork merge requests, contribute engine techniques and promote Live release channels.
3D, PBR & audio asset packs (assets)
Use GameCrew purely as an asset pipeline inside a local Unreal, Unity, Godot or custom engine project: generate concept sheets, seamless PBR maps, rigged & animated GLB/FBX characters, mastered audio and signed download URLs.
All 91 MCP tools by group
| Tool group | Token scope | Tools | Capabilities |
|---|---|---|---|
| Studio builds & jobs | Full (3 also in Assets) | new_game build_game change_game get_game list_games get_job list_jobs cancel_job message_builder get_screenshots list_showcase fork_game get_limits request_tier_change |
Read games, play links, camera captures, limits and the account’s tier (Contributor or Platform; request_tier_change asks an admin to move it), fork a showcase game (or one whose owner allows forks), and poll jobs up to 50 s per call. new_game, build_game, change_game and message_builder start GameCrew’s own AI crew (Unity 6, Godot 4, Three.js or Pulse, including WebXR VR) from your credits: they are listed only after the account switches the AI crew on for its assistants. |
| Branches, forks & merge requests | Full | create_branch list_branches delete_branch open_merge_request sync_fork resolve_conflict list_merge_requests get_merge_request comment_on_merge_request review_merge_request try_merge_request request_changes merge_merge_request resolve_merge_request decline_merge_request withdraw_merge_request get_notifications set_handle |
A branch is the normal way to change a game, yours or someone else's: a working copy that belongs to the game; open a merge request into main with its verified version, bring main's newer version into the branch (three-way merge with conflict markers for the assistant to resolve, or one whole side of a file), read a merge request's files and diffs, discuss it, ask for changes, merge it (picking a side for files that collide, or having the studio's AI crew resolve the colliding lines on a budget), decline or withdraw it, and hear what happened through notifications, under a public handle. Who may branch a game is who may open a merge request to it: on a public game, anyone signed in unless its owner keeps it to the crew. A fork, a game of your own made from another, is for games whose owner allows forks (showcase games always do), and goes back the same way. |
| Games as repositories | Full | explore_games get_repo get_history get_change list_repo_files read_repo_file set_visibility set_crew_member list_crew_invites answer_crew_invite set_merge_request_policy block_contributor set_forks set_account_forks get_asset_history upload_asset restore_asset save_assets make_key_art set_cover |
Treat a game as a repository: explore the studio's public games, read any game you can see (its overview, its versions as commits with their authors, each version's changed files and diffs, its tree and text files), and as its owner decide who sees it and who contributes: public or private, the crew you invite, who may make branches and open merge requests, blocked handles, and whether forks are allowed (off unless you allow them, for one game or by default for all of yours). Assets are versioned with the game: read one picture, sound or model across its versions, upload one you already have with its licence, or put an earlier one back. Key art (the picture a game is shown by) is made for a game that exists from the game itself, and its owner chooses which take is the cover. |
| 3D, texture & audio asset packs | Full & Assets-only | new_asset_pack make_concept_art make_texture make_sound make_model list_assets search_library use_library_asset get_importer |
Generate concept art, seamless PBR textures, mastered WAV sound effects/loops/music and rigged LOD FBX/GLB 3D models, search CC0/CC BY open-licence library assets, and fetch Unity 6 URP importer scripts. |
| Live code & project inspection | Full workspace | work_status project_map engine_api list_files read_file search_files write_file edit_file delete_file say |
Map scripts, scenes and tuning across Unity 6, Godot 4, Three.js and Pulse, look up offline engine class & member signatures, edit code directly, and post updates to the creator timeline. |
| Sandboxed engine runs & release | Full workspace | run_unity pulse get_capture get_run_log get_activity save_version discard_changes |
Run sandboxed engine compiles, scene rebuilds, EditMode/PlayMode tests, camera captures and sub-second Pulse scenario/sweep commands, read logs and screenshots, and save verified browser builds. |
| Technique library | Full (2 also in Assets) | search_techniques read_technique contribute_technique share_technique suggest_technique_revision list_technique_suggestions answer_technique_suggestion withdraw_technique_suggestion report_technique |
Search and read engine-specific technique guides (graphics, game feel, AI, VR) before building something hard, write guides your own account owns, ask for one to be shared with every builder after a review, and suggest revisions to other people's guides. |
| Game operations, Live channel & AI triage | Full workspace | get_game_health manage_backlog promote_version triage_game |
Inspect 0–100 game health scores, 6 release-readiness gates and deterministic project audits, manage prioritized p0/p1/p2 backlogs, promote versions to stable /play/<slug> Live channels, and run AI Game Manager triage. |
Clean git source & standalone build exports
- Standard git repository per game: every verified version is tagged (
v1,v2, …) with human-readable C# (Unity 6 URP), GDScript &.tscn(Godot 4), or TypeScript (Three.js & Pulse) source files — zero proprietary runtime lock-in. - One-click archives: download the complete engine project folder, self-contained HTML5/WebGL web bundle (ready for itch.io, CrazyGames, Poki or static hosting), and standalone Windows or macOS desktop builds for Unity 6 games.
- Sandboxed cloud verification: commands executed via
workspace_check,workspace_build_webandworkspace_save_versionrun on GameCrew’s isolated engine workers with headless Chrome and emulated WebXR checks — no local Unity or Godot install needed. - Agent-friendly documentation: every public page on GameCrew supports
Accept: text/markdownHTTP content negotiation alongside /llms.txt, /llms-full.txt and /.well-known/mcp.json.
Developer & MCP FAQ
How do I connect Claude Code, Cursor, or VS Code to GameCrew over MCP?
Add GameCrew’s Streamable HTTP MCP endpoint (https://play.gamecrew.ai/mcp) to your assistant. One that signs in by itself opens GameCrew’s page in your browser: sign in and press Connect. Or open the studio Usage page, create an access token under Connect a coding assistant, and send it as Authorization: Bearer gc_... in your mcpServers config. Nothing needs to be installed locally.
Can I use GameCrew from Claude or ChatGPT, without a coding assistant?
Yes. In Claude (web, desktop or phone) or ChatGPT, add a custom connector with the address https://play.gamecrew.ai/mcp and nothing else. The app sends you to GameCrew to sign in and press Connect (OAuth 2.1 with PKCE and dynamic client registration), and GameCrew’s tools are in the chat. Access is listed, and taken away, on the studio Usage page.
Does a connected assistant spend my GameCrew credits?
Not by default. Your assistant does the work itself, on your own AI subscription: it reads the project, edits the source, and GameCrew runs the engine, checks the result and hosts each version, which costs engine minutes and no credits. GameCrew’s own AI crew (new_game, build_game, change_game), which builds from a brief and is paid from your credits, is offered to a connected assistant only on a plan that includes it, and only after you switch it on in the studio under Usage, Connect a coding assistant.
What is the difference between a Full token and an Assets-only token?
A Full token (scope: all) exposes all 91 MCP tools so your assistant can create games, edit C#/GDScript/TypeScript source, run sandboxed engine tests, submit verified merge requests, read and contribute engine techniques, and promote Live release links. An Assets-only token (scope: assets) exposes 14 asset-pack and technique-reading tools so an assistant working inside your own local Unity or Godot repo can generate rigged 3D models, PBR textures, and WAV audio without build access to your other games.
Does my computer need Unity 6 or Godot 4 installed to edit a GameCrew game over MCP?
No. Your coding assistant reads and edits files remotely via read_file, edit_file, project_map, and engine_api, while GameCrew compiles scenes, runs automated playtests, captures screenshots, and builds WebGL/HTML5 players inside its own cloud sandbox.
Can I use GameCrew’s 3D model, rigging, and audio tools inside my own local Unity project?
Yes. Create an asset pack with new_asset_pack, generate concept art, rigged FBX/GLB models, seamless textures, or mastered WAV audio, download the signed asset URLs via list_assets, and run get_importer to install GameCrew’s Unity 6 URP prefab, LOD, and Animator editor scripts.
What files are included when I download a game’s source archive?
Every saved version is a clean git tag you can download as a complete project archive: C# scripts, generated URP scenes, FBX prefabs, PBR maps, and WAV audio for Unity 6; .tscn scenes and GDScript for Godot 4; or TypeScript sources and glTF/JSONC assets for Three.js and Pulse — plus any open-licence credits.json attributions.
Build in the studio, finish in your editor — or both
Join the GameCrew alpha waitlist for full studio + MCP workspace access.