Bitrise
Server Details
Set up & manage mobile CI/CD on Bitrise: build, test, distribute iOS, Android, Flutter, RN apps.
- Status
- Unhealthy
- OAuth
- Not connectable
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- bitrise-io/bitrise-mcp
- GitHub Stars
- 41
- Server Listing
- Bitrise MCP Server
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Added
register - Added
verify_registration
14 tool updates
- Added
codepush_create_deployment - Added
codepush_delete_deployment - Added
codepush_delete_update - Added
codepush_generate_update_upload_url - Added
codepush_get_deployment - Added
codepush_get_metrics - Added
codepush_get_update - Added
codepush_get_update_status - Added
codepush_list_deployments - Added
codepush_list_updates - Added
codepush_patch_update - Added
codepush_promote_deployment - Added
codepush_rollback_deployment - Added
codepush_update_deployment
2 tool updates
- Changed
get_pipeline1 field changed- added
Input schema / properties / verboseAdded value: +{ + "description": "Include all pipeline details. Default: false", + "type": "boolean" +}
- Changed
list_pipelines1 field changed- added
Input schema / properties / verboseAdded value: +{ + "description": "Include all pipeline details. Default: false", + "type": "boolean" +}
3 tool updates
- Changed
get_build1 field changed- added
Input schema / properties / verboseAdded value: +{ + "description": "Include all build details. Default: false", + "type": "boolean" +}
- Changed
get_build_steps1 field changed- added
Input schema / properties / verboseAdded value: +{ + "description": "Include all build details. Default: false", + "type": "boolean" +}
- Changed
list_builds1 field changed- added
Input schema / properties / verboseAdded value: +{ + "description": "Include all build details. Default: false", + "type": "boolean" +}
1 tool update
- Changed
register_app1 field changed- changed
Input schema / properties / default_branch_name / descriptionPrevious value: -"The default branch of the repository"New value: +"The default branch of the repository. Verify this branch exists in the remote repository."
67 tool updates
- First observed
abort_build - First observed
abort_pipeline - First observed
add_member_to_group - First observed
add_testers_to_tester_group - First observed
create_connected_app - First observed
create_outgoing_webhook - First observed
create_tester_group - First observed
create_workspace_group - First observed
delete_all_cache_items - First observed
delete_app - First observed
delete_artifact - First observed
delete_cache_item - First observed
delete_outgoing_webhook - First observed
finish_bitrise_app - First observed
generate_installable_artifact_upload_url - First observed
get_app - First observed
get_artifact - First observed
get_bitrise_yml - First observed
get_build - First observed
get_build_bitrise_yml - First observed
get_build_log - First observed
get_build_steps - First observed
get_cache_item_download_url - First observed
get_connected_app - First observed
get_installable_artifact_upload_and_proc_status - First observed
get_pipeline - First observed
get_potential_testers - First observed
get_tester_group - First observed
get_testers - First observed
get_workspace - First observed
get_workspace_groups - First observed
get_workspace_members - First observed
invite_member_to_workspace - First observed
list_apps - First observed
list_artifacts - First observed
list_available_stacks - First observed
list_branches - First observed
list_build_distribution_version_test_builds - First observed
list_build_distribution_versions - First observed
list_build_workflows - First observed
list_builds - First observed
list_cache_items - First observed
list_connected_apps - First observed
list_group_roles - First observed
list_installable_artifacts - First observed
list_outgoing_webhooks - First observed
list_pipelines - First observed
list_tester_groups - First observed
list_workspaces - First observed
me - First observed
notify_tester_group - First observed
rebuild_pipeline - First observed
register_app - First observed
register_ssh_key - First observed
register_webhook - First observed
replace_group_roles - First observed
set_installable_artifact_public_install_page - First observed
step_inputs - First observed
step_search - First observed
trigger_bitrise_build - First observed
update_app - First observed
update_artifact - First observed
update_bitrise_yml - First observed
update_connected_app - First observed
update_outgoing_webhook - First observed
update_tester_group - First observed
validate_bitrise_yml
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Build, run, and inspect iOS apps in disposable hosted Simulators from cloud coding agents.
- LimrunOAuthcom.limrun
Cloud iOS simulators and Android emulators your agent can create, drive, and throw away.
Manage test suites, run tests, view results, and automate QA workflows via AI with testRigor.
Deploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs.
Related MCP Servers
- AlicenseAqualityBmaintenanceBuild, sign, and publish iOS and Android apps through AI agents. Integrates Codemagic CI/CD, App Store Connect, and Google Play in one server.63181MIT
- AlicenseAqualityBmaintenanceManage the full Google Play Store release lifecycle directly — from uploading artifacts to managing testers, rollouts, and Android Vitals.166MIT
- AlicenseBqualityDmaintenanceTransforms AI assistants into mobile development powerhouses with 36 tools for Flutter, Android, and iOS development, including intelligent device management, automated builds, testing, and deployment workflows.31217MIT

appcircle-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to interact with Appcircle mobile CI/CD platform for build management, signing identities, testing distribution, and reporting.25MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Most tools have clear, distinct purposes with detailed descriptions. While the high number of tools could cause potential confusion, each tool targets a specific action and resource, reducing ambiguity.
All tools follow a consistent snake_case naming pattern, predominantly verb_noun or domain_prefix_verb_noun (e.g., 'list_apps', 'codepush_create_deployment'). No mixing of conventions.
With 81 tools, the server is extremely large. While Bitrise is a comprehensive CI/CD platform, this many tools likely leads to unnecessary complexity and may overwhelm agents.
The tool set covers a wide range of CI/CD operations including builds, pipelines, artifacts, cache, webhooks, code push, and release management. Minor gaps exist (e.g., no update build), but overall it's quite thorough.