#MCP Server

Connect Cresc to your AI client (Claude Desktop, an IDE, your own agent) so it can read your release state directly and investigate alongside GitHub, Sentry or CI. Everything is read-only — it never changes your releases.

#What you would use it for

Find out why a device did not get an update

A device on native package 1.2.0 of my app (appKey xxx) never received the update — can you check?

The agent looks up which version that package currently serves, replays the update decision, checks whether the patch artifacts are ready, and tells you where it stops — outside the rollout, package paused, or the patch still building.

Confirm the state around a release

Which version does 1.2.0 serve right now, and what is the rollout percentage?

Correlate with your other tools

Errors went up yesterday — compare the Sentry exceptions with the Cresc release history

#Getting started

#1. Create a token

In the Cresc console open "MCP Server", give it a name and a client label, tick the apps it may read, then copy the token right away — it is shown only once.

#2. Configure your client

With Claude Desktop:

{
  "mcpServers": {
    "cresc": {
      "type": "http",
      "url": "https://api.cresc.dev/mcp",
      "headers": {
        "Authorization": "Bearer pushy_mcp_your_token"
      }
    }
  }
}

#3. Just ask

Once connected, ask in plain language as in the scenarios above — you never need to name a tool.

#What it can read

#Good to know

• Read-only: it never publishes a version, pauses an app or changes any setting;
• Scoped per app: grant only the apps you are debugging; a token can be revoked from the console at any time and stops working immediately;
• Where the data goes: results go to the AI client you authorized, which may forward them to the model provider you chose — Cresc controls neither;
• Responses never contain email addresses, IPs, device identifiers, secrets or payment data.

#About gray releases

Whether a device is in a gray release is decided on the device, so the server can only name the candidate version. Supply a device uuid when investigating and the answer becomes specific to that device; the uuid is used for that one calculation and is never stored.