Developers

xprem developer resources

The canonical starting points for installing xprem, configuring an Expo app, publishing updates, authenticating API access, and connecting an agent over MCP.

Start and deploy

Start with the xprem quickstart to choose stateless or control-plane mode, configure storage, and point expo-updates at the server you operate. The server is distributed as a Docker image, a Helm chart, and a static Go binary. The eoas CLI initializes an app and publishes, rolls back, or republishes updates against your deployment.

API and agent access

The xprem API belongs to each self-hosted deployment; xprem.dev is not a shared release control plane. Human and CLI access use credentials configured on that instance. API tokens can be scoped by action, branch, and network where the licensed controls are enabled. xprem does not currently publish a versioned OpenAPI description, so integrations should use the documented CLI, MCP interface, or server source as the contract rather than guessing endpoints.

Every xprem server exposes its MCP endpoint at /mcp. Agents authenticate with OAuth 2.1 as dashboard users, and each tool is bounded by that user's application permissions. Use MCP when an agent needs to inspect apps, branches, channels, updates, or rollouts, or when an authorized operator asks it to perform a release action. The MCP documentation lists setup, authentication, and available tools.

Source and machine-readable indexes

Use the source repository for implementation details and release history. Use the two llms.txt indexes for curated, Markdown-first discovery: xprem.dev describes the product and trust pages, while the GitBook index enumerates the full versioned documentation set. These resources name xprem explicitly so search engines and agents can distinguish the project from similarly named products and from its former expo-open-ota name.