Createrun MCP

The per-user MCP server lets an AI client work with Createrun. Its CLI has its own Doctor and two removal scopes: unregister a client, or purge the installed program and local state.

Windows x64Linux x64Per-user install

1. Install and connect an AI client

The Store scripts install the stable release for the current user. --client or -Client can register it with codex, claude-code, claude-desktop, cursor or vscode; auto tries detected clients. Use none if you want to register a client later.

Windows PowerShell

& ([scriptblock]::Create((irm https://store.createrun.ai/installer/mcp/install.ps1))) -Client codex
$mcp = Join-Path $env:LOCALAPPDATA 'Programs\Createrun\MCP\createrun-mcp.exe'
& $mcp login

Linux shell

curl -fsSL https://store.createrun.ai/installer/mcp/install.sh | sh -s -- --client codex
MCP="$HOME/.local/share/createrun/mcp/bin/createrun-mcp"
"$MCP" login

Sign-in opens an IDM device-code flow. Restart the AI client after registering the MCP server. If you chose none, run createrun-mcp install --client <name> using the installed executable path. Check the installed tool with --version before relying on a newer command.

2. Run MCP Doctor

Run doctor from the installed copy. It checks version and install marker, configuration, Git, platform and IDM reachability, sign-in, update status and the release trust root. It does not diagnose a self-hosted Instance or Developer Suite.

# Windows PowerShell: use $mcp from the install step
& $mcp doctor
& $mcp doctor --json

# Linux shell: use $MCP from the install step
"$MCP" doctor

Read every FAIL and WARN line. A missing sign-in can be a warning before login; a failed endpoint, Git or trust-root check needs attention. --json is useful for a support report, but review identity and endpoint details before sharing it. Run update --check separately to check for a newer release.

3. Choose the removal scope

Command	Effect
`uninstall --client codex`	Removes the selected AI client's Createrun registration. Program, local state and sign-in stay.
`uninstall`	Uses `auto` to remove detected client registrations. Program and local state stay.
`uninstall --purge`	After confirmation, also removes the installed program, update/settings/log/workspace state and stored sign-in. Close all MCP clients first.

On Windows, invoke the installed $mcp path; on Linux use $MCP. For example:

# Unregister Codex only
& $mcp uninstall --client codex

# Or, after reviewing the listed paths, remove everything
& $mcp uninstall --purge

On Linux, replace & $mcp with "$MCP". The CLI prints the program, state and sign-in paths before asking for purge confirmation. --yes skips that prompt and is intended only when you have already reviewed those paths. If the running executable was not installed from a Store package with .install.json, purge leaves that program file in place. Verify client registration and file removal separately after the command.

Result and platform limits

doctor exits 0 when there are no FAIL checks, even if warnings remain; 1 means a check failed and 2 means invalid CLI usage. update --check uses exit 3 when an update is available. Uninstall can report individual failed steps; read those lines before assuming removal completed.

The Store's one-line installers target Windows x64 and Linux x64. A macOS MCP installer is not supplied by these scripts. For Instance health use Instance Doctor, which is a different executable.