Debug Unity Builds From Rider With the TeamCity CLI and MCP

At GameDev Day 2026, TeamCity engineer Artem Rokhin demonstrated diagnosing a Unity staging issue from Rider when a game’s background was absent despite a successful CI build. Using the TeamCity CLI, he identified the relevant WebGL run, examined its logs, and found that an unexpected `gameBuildFlavor` value of `diagnostic` had been supplied instead of the intended `game` setting; he then corrected the YAML pipeline configuration and committed the change to trigger a new deployment. The workflow requires a Rider-based Unity project, repository-stored TeamCity pipeline settings, CLI access, and optionally an MCP-capable AI agent connected to TeamCity with a read-only token. Through MCP, an AI agent can inspect build details and logs, compare them with local pipeline and build-script files, explain the likely cause with supporting evidence, and monitor the replacement deployment for completion and its staging URL. The example emphasizes verifying the deployed application directly, since a green build alone does not prove the issue is resolved, and recommends improving pipelines by logging output-affecting settings, validating permitted configuration values, and adding targeted smoke or visual tests.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.