Rally Studio

place.rallyPublished by rally.placeOfficial publisherv1.0.0Updated Nov 11, 2026

Make multiplayer 2D/3D browser games on Rally by chat: build, script, playtest with bots, publish.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Rally Studio lets an assistant build, script, playtest with bots and publish multiplayer 2D/3D browser games on Rally through chat.

What you can do
  • Build multiplayer 2D and 3D browser games through chat on the Rally platform
  • Script game logic and behavior
  • Playtest games with bots
  • Publish finished games
  • No tool list is published, so the exact commands available are not documented here.
When to use it
Useful if you want to create or iterate on multiplayer browser games conversationally on Rally, from first build through scripting, bot playtesting and publishing, rather than working in a separate game editor.
Requirements
A remote endpoint at rally.place; OAuth sign-in is required. No packages, environment variables or headers are declared.
Before you install
Publishing makes games publicly available, and playtesting or publishing may consume Rally account resources; review what the assistant can change in your account before granting OAuth access.

Installation

In SourceWeft

  1. Open Rally Studio in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/place.rally%2Fstudio/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rally-studio": {
      "type": "http",
      "url": "https://rally.place/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 11, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Rally integrations