Docs · Connect

Command line

Configure Origin MCP from a terminal, install Origin Runner, and publish games from scripts and CI with the deploy script.

One-line Origin MCP installer

In a macOS, Linux or WSL terminal, run:

curl -fsSL https://origingame.ai/install.sh | sh

The script:

Reads Origin's live install catalog, which currently holds only the unified origin MCP (https://mcp.origingame.ai/mcp).
Detects Claude Code (claude), Codex (codex) and Grok (grok) on your PATH and asks which to configure.
Writes origin into each chosen agent's user-level configuration. Agents with browser sign-in (Claude Code, Codex) get the address only and open the browser sign-in themselves on first use; the other agents share one revocable credential from a browser device sign-in, stored in ~/.origingame/connector-credential (mode 0600).
Removes older entries such as origin-assets and origin-generate that an earlier version wrote (only entries whose address is exactly one Origin published) and reports the entries it kept.

It installs no Origin binary, runtime or background process. Re-run the same command to update; revoke the device sign-in under "Signed-in devices" on the Access page. The script needs curl, unzip and sha256sum (or shasum).

Option	Effect
`--agents claude,codex,grok`	Configure only the listed agents (comma-separated), or `all` for every detected agent; without it the script detects them and asks you to confirm
`--keep-legacy`	Keep the old per-domain MCP entries
`--project`	Install the catalog's Skills into the current project; credentials and MCP configuration stay in your user profile
`--aigcc`	Install only what AIGCC needs; when the catalog holds only MCP, this installs the unified `origin` MCP with no local upload helper
`--help`	Show usage

To pass options through the pipe, add -s -- after sh:

curl -fsSL https://origingame.ai/install.sh | sh -s -- --agents claude,codex

Note: the script supports only the default configuration folders; it stops when a custom CLAUDE_CONFIG_DIR or CODEX_HOME is set.

There is no PowerShell installer for Windows: add the address directly as described in Origin MCP, or use Origin Kit.

Origin Runner

Origin Runner runs Origin's threads on your own computer, with the game repositories kept in your folders. It holds no model keys or account credentials.

Install on macOS / Linux:

curl -fsSL https://origingame.ai/downloads/runner/install.sh | sh

On Windows, run this in PowerShell; no administrator rights are needed and it installs to %LOCALAPPDATA%\Origin. The Windows build has not been verified on a real Windows host yet.

irm https://origingame.ai/downloads/runner/install.ps1 | iex

Then connect it to your account:

Open the Origin Runner page, enter a name and choose "Issue a token". The token is shown once; your account needs at least one game repository first.
Run the commands the page shows: origin-runner login reads the token from standard input and writes it to ~/.origin/runner/token; origin-runner service install, with the --runner-id from the page, serves --dir ~/Games as your games folder and installs the background service (a systemd user unit on Linux, a LaunchAgent on macOS, a Scheduled Task on Windows).

A game created on the web is cloned into ~/Games the first time a session runs on this computer, and every session works in its own Git worktree beside it. Serve an existing checkout with --dir PATH=REPOSITORY_ID. On Linux, service install turns on lingering so the runner starts at boot without anyone logged in.

On macOS, Origin Kit ships Origin Runner; turn it on from Kit's "Runner" page with nothing else to install. The Origin Runner page shows whether each runner is online and lets you revoke it at any time.

Skill repository and deploy script

Scripts and CI that don't use MCP can publish with the deploy script in the Skill repository. It reads your account API token from the environment:

Get an API token

git clone https://github.com/fran0220/origingame-skill
export OG_API_KEY=og-...
export OG_HOST=https://origingame.ai
origingame-skill/scripts/deploy.sh ./dist --title "Neon Dodge" --cover cover.png

./dist is the built game folder and --cover the landscape cover. Every option, including updating an existing game, engine, genre and visibility, is listed in the comment at the top of the script. Publishing requirements, releases and rollback are in Publish a game.

Note: an agent already set up with Origin MCP by the installer or Origin Kit should publish through MCP, not with a separate API token.

Environment variables

The Skill repository's scripts read these environment variables:

Variable	Meaning	When unset
`OG_API_KEY`	Your account API token (`og-...`), created under Access	Commands that need a credential stop with an error
`OG_HOST`	The Origin website's origin, used for publishing (`/api/deploy`); set it to `https://origingame.ai` for production	`http://localhost:8787`
`OG_AI_GATEWAY`	The Origin public API host, without `/v1`: model endpoints are at `$OG_AI_GATEWAY/v1/...`	`https://api.origingame.ai`

Never commit OG_API_KEY to a repository or put it in game code. In CI, inject it through your platform's secrets.

Next steps

Publish a game: publishing requirements, updates, releases and rollback.
Model API: call https://api.origingame.ai/v1 directly with OG_API_KEY.
Origin MCP: use the platform tools in your agent.