Ubriot

dev.ubriotPublished by ubriot.devv2.5.0Updated Nov 7, 2026

Build, sign, submit and roll back React Native and Expo releases from an AI assistant.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Ubriot lets an AI assistant build, sign, submit and roll back React Native and Expo app releases from the chat.

What you can do
  • Build, sign, submit and roll back React Native and Expo releases
  • Diagnose failed builds or releases, optionally using an OpenAI key
  • Generate release notes, optionally using an OpenAI key
  • Send push notifications for one app using a push server key
  • Authenticate with a Ubriot API key or session token, or with account email and password
When to use it
Useful when you ship React Native or Expo apps and want an assistant to trigger or roll back releases, look into failed builds, draft release notes, or send app push notifications without leaving the conversation.
Requirements
Runs as a local stdio process from the npm package ubriot-mcp, on desktop only. Needs a Ubriot account: either UBRIOT_TOKEN (API key or session token) or UBRIOT_EMAIL plus UBRIOT_PASSWORD. Optional: OPENAI_API_KEY for failure diagnosis and release notes, and UBRIOT_PUSH_SERVER_KEY for sending push to one app.
Before you install
Requires Ubriot account credentials (UBRIOT_TOKEN, or UBRIOT_EMAIL with UBRIOT_PASSWORD) and can build, submit and roll back releases, which changes what users receive. UBRIOT_PUSH_SERVER_KEY allows sending push notifications to an app's users. OPENAI_API_KEY is optional and, when set, is used by the diagnose and release-notes tools, so relevant data may go to OpenAI.

Installation

In SourceWeft

  1. Open Ubriot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.5.0LatestNov 7, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.