Bitrise
Run and inspect Bitrise mobile CI/CD — apps, builds, artifacts, and workflows. Sign in with Bitrise to connect.
What Bitrise exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the bitrise__ namespace. Your agent never loads them all — it searches, and gets the few that match.
bitrise__abort_build6 arguments · 2 required
Abort a specific build.
Required
app_slugbuild_slugbitrise__abort_pipeline5 arguments · 2 required
Abort a pipeline.
Required
app_slugpipeline_idbitrise__add_member_to_group2 arguments · 2 required
Add a member to a group.
Required
group_sluguser_slugbitrise__add_testers_to_tester_group3 arguments · 3 required
Adds testers to a tester group of a connected app.
Required
connected_app_ididuser_slugsbitrise__codepush_create_deployment3 arguments · 2 required
Create a new CodePush deployment for a Bitrise app.
Required
nameapp_idbitrise__codepush_delete_deployment1 argument · 1 required
Delete a CodePush deployment. This action is irreversible.
Required
idbitrise__codepush_delete_update1 argument · 1 required
Delete a CodePush update. This action is irreversible.
Required
idbitrise__codepush_generate_update_upload_url9 arguments · 5 required
Generate a signed upload URL (valid 1 hour) for uploading a CodePush update bundle. The response contains the URL, HTTP method, and headers needed for a direct upload. After uploading, check status with codepush_get_update_status.
Required
iddeployment_idapp_versionfile_namefile_size_bytesbitrise__codepush_get_deployment1 argument · 1 required
Get a specific CodePush deployment by its ID.
Required
idbitrise__codepush_get_metrics1 argument · 1 required
Get workspace-level CodePush usage metrics including data transfer, storage, and monthly active users, along with their limits and billing cycle information.
Required
workspace_slugbitrise__codepush_get_update1 argument · 1 required
Get a specific CodePush update by its ID.
Required
idbitrise__codepush_get_update_status1 argument · 1 required
Get the processing status of a CodePush update (e.g. pending, ready, failed).
Required
idbitrise__codepush_list_deployments4 arguments · 1 required
List CodePush deployments for a Bitrise app.
Required
app_idbitrise__codepush_list_updates4 arguments · 1 required
List CodePush updates for a specific deployment.
Required
deployment_idbitrise__codepush_patch_update4 arguments · 1 required
Patch a CodePush update to change its disabled state, mandatory flag, or rollout percentage. Only include fields you want to change — omitted fields are left unchanged.
Required
idbitrise__codepush_promote_deployment8 arguments · 2 required
Promote a package from a source deployment to a target deployment. The most recent package in the source deployment is promoted unless package_id is specified.
Required
idtarget_deployment_idbitrise__codepush_rollback_deployment2 arguments · 1 required
Rollback a CodePush deployment to its previous version, or to a specific package if package_id is provided.
Required
idbitrise__codepush_update_deployment2 arguments · 2 required
Update the name of an existing CodePush deployment.
Required
idnamebitrise__create_connected_app8 arguments · 3 required
Add a new Release Management connected app to Bitrise.
Required
platformstore_app_idworkspace_slugbitrise__create_outgoing_webhook5 arguments · 3 required
Create an outgoing webhook for an app.
Required
app_slugeventsurlbitrise__create_tester_group3 arguments · 2 required
Creates a tester group for a Release Management connected app. Tester groups can be used to distribute installable artifacts to testers automatically. When a new installable artifact is available, the tester groups can either automatically or manually be notified via email. The notification email will contain a link to the installable artifact page for the artifact within Bitrise Release Management. A Release Management connected app can have multiple tester groups. Project team members of the connected app can be selected to be testers and added to the tester group. This endpoint has an elevated access level requirement. Only the owner of the related Bitrise Workspace, a workspace manager or the related project's admin can manage tester groups.
Required
connected_app_idnamebitrise__create_workspace_group2 arguments · 2 required
Create a new group in a workspace.
Required
workspace_sluggroup_namebitrise__delete_all_cache_items1 argument · 1 required
Delete all key-value cache items belonging to an app.
Required
app_slugbitrise__delete_app1 argument · 1 required
Delete an app from Bitrise. When deleting apps belonging to multiple workspaces always confirm that which workspaces' apps the user wants to delete.
Required
app_slugbitrise__delete_artifact3 arguments · 3 required
Delete a build artifact.
Required
app_slugbuild_slugartifact_slugbitrise__delete_cache_item2 arguments · 2 required
Delete a key-value cache item.
Required
app_slugcache_item_idbitrise__delete_outgoing_webhook2 arguments · 2 required
Delete the outgoing webhook of an app.
Required
app_slugwebhook_slugbitrise__finish_bitrise_app4 arguments · 3 required
Finish the setup of a Bitrise app. If this is successful, a build can be triggered via trigger_bitrise_build. If you have access to the repository, decide the project type, the stack ID, and the config to use, based on https://stacks.bitrise.io/, and the config should be also based on the project type.
Required
app_slugproject_typestack_idbitrise__generate_installable_artifact_upload_url7 arguments · 4 required
Generates a signed upload url valid for 1 hour for an installable artifact to be uploaded to Bitrise Release Management. The response will contain an url that can be used to upload an artifact to Bitrise Release Management using a simple curl request with the file data that should be uploaded. The necessary headers and http method will also be in the response. This artifact will need to be processed after upload to be usable. The status of processing can be checked by making another request to a different url giving back the processed status of an installable artifact.
Required
connected_app_idinstallable_artifact_idfile_namefile_size_bytesbitrise__get_app1 argument · 1 required
Get the details of a specific app.
Required
app_slugbitrise__get_artifact3 arguments · 3 required
Get a specific build artifact.
Required
app_slugbuild_slugartifact_slugbitrise__get_bitrise_yml1 argument · 1 required
Get the current Bitrise YML config file of a specified Bitrise app.
Required
app_slugbitrise__get_build3 arguments · 2 required
Get a specific build of a given app.
Required
app_slugbuild_slugbitrise__get_build_bitrise_yml2 arguments · 2 required
Get the bitrise.yml of a build.
Required
app_slugbuild_slugbitrise__get_build_log5 arguments · 2 required
Get the build log of a specified build of a Bitrise app.
Required
app_slugbuild_slugbitrise__get_build_steps3 arguments · 2 required
Get step statuses of a specific build of a given app.
Required
app_slugbuild_slugbitrise__get_cache_item_download_url2 arguments · 2 required
Get the download URL for a cache item.
Required
app_slugcache_item_idbitrise__get_connected_app1 argument · 1 required
Gives back a Release Management connected app for the authenticated account.
Required
idbitrise__get_installable_artifact_upload_and_proc_status2 arguments · 2 required
Gets the processing and upload status of an installable artifact. An artifact will need to be processed after upload to be usable. This endpoint helps understanding when an uploaded installable artifacts becomes usable for later purposes.
Required
connected_app_idinstallable_artifact_idbitrise__get_pipeline3 arguments · 2 required
Get a pipeline of a given app.
Required
app_slugpipeline_idbitrise__get_potential_testers5 arguments · 2 required
Gets a list of potential testers whom can be added as testers to a specific tester group. The list consists of Bitrise users having access to the related Release Management connected app.
Required
connected_app_ididbitrise__get_tester_group2 arguments · 2 required
Gives back the details of the selected tester group.
Required
connected_app_ididbitrise__get_testers4 arguments · 1 required
Gives back a list of testers that has been associated with a tester group related to a specific connected app.
Required
connected_app_idbitrise__get_workspace1 argument · 1 required
Get details for one workspace
Required
workspace_slugbitrise__get_workspace_groups1 argument · 1 required
Get the groups in a workspace
Required
workspace_slugbitrise__get_workspace_members1 argument · 1 required
Get the members of a workspace
Required
workspace_slugbitrise__insights_get_build_series10 arguments · 4 required
Get a build metrics time series for a project from Bitrise Insights: one row per time bucket, oldest first, each with build count, failure rate (0-100 %), p50/p90 duration and total duration in seconds. Use 'group_by' to also split by workflow, pipeline, stage or step. Time window: 'start' is inclusive and 'end' exclusive, both RFC3339 in UTC (e.g. 2026-07-01T00:00:00Z). The window may span at most 7 days hourly, 90 days daily, 1 year weekly and 2 years monthly. Requires a paid Bitrise Insights plan on the workspace. The project is identified by its Insights project ID, not by the app slug.
Required
workspace_slugprojectstartendbitrise__insights_get_build_totals7 arguments · 4 required
Get build aggregates for a project from Bitrise Insights: build count, failure rate (0-100 %), p50/p90 duration and total duration in seconds over the whole time window, without grouping. Time window: 'start' is inclusive and 'end' exclusive, both RFC3339 in UTC (e.g. 2026-07-01T00:00:00Z). The window may span at most 2 years. Requires a paid Bitrise Insights plan on the workspace. The project is identified by its Insights project ID, not by the app slug.
Required
workspace_slugprojectstartendbitrise__insights_get_test_series11 arguments · 4 required
Get a test metrics time series for a project from Bitrise Insights: one row per time bucket, oldest first, each with test run count, failure rate (0-100 %), p50/p90 duration and total duration in seconds, and flaky run count. Use 'group_by' to also split by workflow, pipeline, stage, branch or test_suite. Time window: 'start' is inclusive and 'end' exclusive, both RFC3339 in UTC (e.g. 2026-07-01T00:00:00Z). The window may span at most 7 days hourly, 90 days daily, 1 year weekly and 2 years monthly. Requires a paid Bitrise Insights plan on the workspace. The project is identified by its Insights project ID, not by the app slug.
Required
workspace_slugprojectstartendbitrise__insights_get_test_totals8 arguments · 4 required
Get test aggregates for a project from Bitrise Insights: test run count, failure rate (0-100 %), p50/p90 duration and total duration in seconds, and flaky run count over the whole time window, without grouping. Counts are of test case runs, not of distinct test cases. Time window: 'start' is inclusive and 'end' exclusive, both RFC3339 in UTC (e.g. 2026-07-01T00:00:00Z). The window may span at most 2 years. Requires a paid Bitrise Insights plan on the workspace. The project is identified by its Insights project ID, not by the app slug.
Required
workspace_slugprojectstartendbitrise__insights_list_flaky_tests13 arguments · 4 required
List the flaky test cases of a project from Bitrise Insights: test cases that were rerun after a flaky result in the time window, one page at a time, ranked by rerun count or flaky rate. Time window: 'start' is inclusive and 'end' exclusive, both RFC3339 in UTC (e.g. 2026-07-01T00:00:00Z). The window may span at most 2 years. Requires a paid Bitrise Insights plan on the workspace. The project is identified by its Insights project ID, not by the app slug.
Required
workspace_slugprojectstartendbitrise__invite_member_to_workspace2 arguments · 2 required
Invite new Bitrise users to a workspace.
Required
workspace_slugemailbitrise__list_apps5 arguments
List all apps for the currently authenticated user account
bitrise__list_artifacts4 arguments · 2 required
Get a list of all build artifacts.
Required
app_slugbuild_slugbitrise__list_available_stacks1 argument
List available stacks with their machine configurations and version information. When a workspace_slug is provided, returns stacks available for that workspace including any custom stacks. When omitted, returns globally available stacks.
bitrise__list_branches1 argument · 1 required
List the branches with existing builds of an app's repository.
Required
app_slugbitrise__list_build_distribution_version_test_builds4 arguments · 2 required
Gives back a list of test builds for the given build distribution version.
Required
connected_app_idversionbitrise__list_build_distribution_versions3 arguments · 1 required
Lists Build Distribution versions. Release Management offers a convenient, secure solution to distribute the builds of your mobile apps to testers without having to engage with either TestFlight or Google Play. Once you have installable artifacts, Bitrise can generate both private and public install links that testers or other stakeholders can use to install the app on real devices via over-the-air installation. Build distribution allows you to define tester groups that can receive notifications about installable artifacts. The email takes the notified testers to the test build page, from where they can install the app on their own device. Build distribution versions are the app versions available for testers.
Required
connected_app_idbitrise__list_build_workflows1 argument · 1 required
List the workflows of an app.
Required
app_slugbitrise__list_builds8 arguments
List all the builds of a specified Bitrise app or all accessible builds.
bitrise__list_cache_items3 arguments · 1 required
List the key-value cache items belonging to an app.
Required
app_slugbitrise__list_connected_apps6 arguments · 1 required
List Release Management connected apps available for the authenticated account within a workspace.
Required
workspace_slugbitrise__list_group_roles2 arguments · 2 required
List group roles for an app
Required
app_slugrole_namebitrise__list_installable_artifacts14 arguments · 1 required
List Release Management installable artifacts of a connected app available for the authenticated account.
Required
connected_app_idbitrise__list_outgoing_webhooks3 arguments · 1 required
List the outgoing webhooks of an app.
Required
app_slugbitrise__list_pipelines12 arguments · 1 required
List all pipelines and standalone builds of an app.
Required
app_slugbitrise__list_tester_groups3 arguments · 1 required
Gives back a list of tester groups related to a specific Release Management connected app.
Required
connected_app_idbitrise__list_workspacesno arguments
List the workspaces the user has access to
bitrise__meno arguments
Get user info for the currently authenticated user account
bitrise__notify_tester_group3 arguments · 3 required
Notifies a tester group about a new test build.
Required
connected_app_ididtest_build_idbitrise__rebuild_pipeline4 arguments · 2 required
Rebuild a pipeline.
Required
app_slugpipeline_idbitrise__register_app7 arguments · 3 required
Add a new app to Bitrise. After this app should be finished on order to be registered completely on Bitrise (via the finish_bitrise_app tool). Before doing this step, try understanding the repository details from the repository URL. This is a two-step process. First, you register the app with the Bitrise API, and then you finish the setup. The first step creates a new app in Bitrise, and the second step configures it with the necessary settings. If the user has multiple workspaces, always prompt the user to choose which one you should use. Don't prompt the user for finishing the app, just do it automatically.
Required
repo_urlis_publicorganization_slugbitrise__register_ssh_key4 arguments · 3 required
Add an SSH-key to a specific app.
Required
app_slugauth_ssh_private_keyauth_ssh_public_keybitrise__register_webhook1 argument · 1 required
Register an incoming webhook for a specific application.
Required
app_slugbitrise__replace_group_roles3 arguments · 3 required
Replace group roles for an app.
Required
app_slugrole_namegroup_slugsbitrise__set_installable_artifact_public_install_page3 arguments · 3 required
Changes whether public install page should be available for the installable artifact or not.
Required
connected_app_idinstallable_artifact_idwith_public_pagebitrise__step_inputs1 argument · 1 required
List inputs of a step with their defaults, allowed values etc.
Required
step_refbitrise__step_search3 arguments · 1 required
Find steps for building workflows or step bundles in a Bitrise YML config file. Finds steps based on name, description, tags or maintainers.
Required
querybitrise__trigger_bitrise_build8 arguments · 1 required
Trigger a new build/pipeline for a specified Bitrise app
Required
app_slugbitrise__update_app4 arguments · 1 required
Update an app. Only app_slug is required, add only fields you wish to update
Required
app_slugbitrise__update_artifact4 arguments · 4 required
Update a build artifact.
Required
app_slugbuild_slugartifact_slugis_public_page_enabledbitrise__update_bitrise_yml2 arguments · 2 required
Update the Bitrise YML config stored on Bitrise. This has no effect if it is stored in the repository.
Required
app_slugbitrise_yml_as_jsonbitrise__update_connected_app4 arguments · 1 required
Updates a connected app.
Required
connected_app_idbitrise__update_outgoing_webhook5 arguments · 2 required
Update an outgoing webhook for an app. Even if you do not want to change one of the parameters, you still have to provide that parameter as well: simply use its existing value.
Required
app_slugwebhook_slugbitrise__update_tester_group4 arguments · 2 required
Updates the given tester group. The name and the auto notification setting can be updated optionally.
Required
connected_app_ididbitrise__validate_bitrise_yml2 arguments · 1 required
Validate a Bitrise YML config file. Use this tool to verify any changes made in bitrise.yml.
Required
bitrise_yml
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Switch Bitrise on
Authorize it from your library; the grant is yours and stays yours.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.dev
