A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/bitrise-io/bitrise-mcp below:

bitrise-io/bitrise-mcp: MCP Server for the Bitrise API, enabling app management, build operations, artifact management and more.

MCP Server for the Bitrise API, enabling app management, build operations, artifact management and more.

Example setting up the environment

Please read the official documentation for uv and pylint for more options.

# Install pyenv and python 3.12.6
curl -fsSL https://pyenv.run | bash
pyenv install 3.12.6

# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh

Create a Bitrise API Token:

This guide uses Claude Desktop as the MCP client, but you can use any other MCP-compatible client and adapt the following config options to your preferred client.

Open Claude settings, then navigate to the Developer tab.

Click Edit config. This creates a config file called claude_desktop_config.json. Open this file with your preferred editor and add the Bitrise MCP server:

{
  "mcpServers": {
    "bitrise": {
      "command": "uvx",
      "env": {
        "BITRISE_TOKEN": "<YOUR_TOKEN>"
      },
      "args": [
        "--from",
        "git+https://github.com/bitrise-io/bitrise-mcp@v1.1.0",
        "bitrise-mcp"
      ]
    }
  }
}

Save the config file and restart Claude Desktop. If everything is set up correctly, you should see a hammer icon next to the message composer.

Follow the official guide to enable Agent mode in Copilot Chat.

Then, open VSCode's settings.json (either the workspace level or the user level settings), and add the Bitrise MCP server configuration under the mcp.servers key, and the workspace token input under the mcp.inputs key:

{
  "mcp": {
    "inputs": [
      {
        "id": "bitrise-workspace-token",
        "type": "promptString",
        "description": "Bitrise workspace token",
        "password": true
      }
    ],
    "servers": {
      "bitrise": {
        "command": "uvx",
        "args": [
          "--from",
          "git+https://github.com/bitrise-io/bitrise-mcp@v1.0.1",
          "bitrise-mcp"
        ],
        "type": "stdio",
        "env": {
          "BITRISE_TOKEN": "${input:bitrise-workspace-token}"
        }
      },
    }
  }
}

Save the configuration. VS Code will automatically recognize the change and load the tools into Copilot Chat.

You can limit the number of tools exposed to the MCP client. This is useful if you want to optimize token usage or your MCP client has a limit on the number of tools.

Tools are grouped by their "API group", and you can pass the groups you want to expose as tools. Possible values: apps, builds, workspaces, webhooks, build-artifacts, group-roles, cache-items, pipelines, account, read-only, release-management.

We recommend using the release-management API group separately to avoid any confusion with the apps API group.

Example configuration:

{
  "mcpServers": {
    "bitrise": {
      "command": "uvx",
      "env": {
        "BITRISE_TOKEN": "<YOUR_PAT>"
      },
      "args": [
        "--from",
        "git+https://github.com/bitrise-io/bitrise-mcp@v1.1.0",
        "bitrise-mcp",
        "--enabled-api-groups",
        "cache-items,pipelines"
      ]
    },
  }
}

  1. list_apps

  2. register_app

  3. finish_bitrise_app

  4. get_app

  5. delete_app

  6. update_app

  7. get_bitrise_yml

  8. update_bitrise_yml

  9. list_branches

  10. register_ssh_key

  11. register_webhook

  1. list_builds

  2. trigger_bitrise_build

  3. get_build

  4. abort_build

  5. get_build_log

  6. get_build_bitrise_yml

  7. list_build_workflows

  1. list_artifacts

  2. get_artifact

  3. delete_artifact

  4. update_artifact

  1. list_outgoing_webhooks

  2. delete_outgoing_webhook

  3. update_outgoing_webhook

  4. create_outgoing_webhook

  1. list_cache_items

  2. delete_all_cache_items

  3. delete_cache_item

  4. get_cache_item_download_url

  1. list_pipelines

  2. get_pipeline

  3. abort_pipeline

  4. rebuild_pipeline

  1. list_group_roles

  2. replace_group_roles

  1. list_workspaces

  2. get_workspace

  3. get_workspace_groups

  4. create_workspace_group

  5. get_workspace_members

  6. invite_member_to_workspace

  7. add_member_to_group

  1. me
  1. create_connected_app
  1. list_connected_apps
  1. get_connected_app
  1. update_connected_app
  1. list_installable_artifacts
  1. generate_installable_artifact_upload_url
  1. get_installable_artifact_upload_and_processing_status
  1. set_installable_artifact_public_install_page
  1. list_build_distribution_versions
  1. list_build_distribution_version_test_builds
  1. create_tester_group
  1. notify_tester_group
  1. add_testers_to_tester_group
  1. update_tester_group
  1. list_tester_groups
  1. get_tester_group
  1. get_potential_testers

The Bitrise MCP server organizes tools into API groups that can be enabled or disabled via command-line arguments. The table below shows which API groups each tool belongs to:

Tool apps builds workspaces webhooks build-artifacts group-roles cache-items pipelines account read-only release-management list_apps ✅ ✅ register_app ✅ finish_bitrise_app ✅ get_app ✅ ✅ delete_app ✅ update_app ✅ get_bitrise_yml ✅ ✅ update_bitrise_yml ✅ list_branches ✅ ✅ register_ssh_key ✅ register_webhook ✅ list_builds ✅ ✅ trigger_bitrise_build ✅ get_build ✅ ✅ abort_build ✅ get_build_log ✅ ✅ get_build_bitrise_yml ✅ ✅ list_build_workflows ✅ ✅ list_artifacts ✅ ✅ get_artifact ✅ ✅ delete_artifact ✅ update_artifact ✅ list_outgoing_webhooks ✅ ✅ delete_outgoing_webhook ✅ update_outgoing_webhook ✅ create_outgoing_webhook ✅ list_cache_items ✅ ✅ delete_all_cache_items ✅ delete_cache_item ✅ get_cache_item_download_url ✅ ✅ list_pipelines ✅ ✅ get_pipeline ✅ ✅ abort_pipeline ✅ rebuild_pipeline ✅ list_group_roles ✅ ✅ replace_group_roles ✅ list_workspaces ✅ ✅ get_workspace ✅ ✅ get_workspace_groups ✅ ✅ create_workspace_group ✅ get_workspace_members ✅ ✅ invite_member_to_workspace ✅ add_member_to_group ✅ me ✅ ✅ create_connected_app ✅ list_connected_apps ✅ get_connected_app ✅ update_connected_app ✅ list_installable_artifacts ✅ generate_installable_artifact_upload_url ✅ get_installable_artifact_upload_and_processing_status ✅ set_installable_artifact_public_install_page ✅ list_build_distribution_versions ✅ list_build_distribution_version_test_builds ✅ create_tester_group ✅ notify_tester_group ✅ add_testers_to_tester_group ✅ update_tester_group ✅ list_tester_groups ✅ get_tester_group ✅ get_potential_testers ✅

By default, all API groups are enabled. You can specify which groups to enable using the --enabled-api-groups command-line argument with a comma-separated list of group names.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4