# Bitrise MCP MCP Server

> **Bitrise MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Bitrise MCP.
>
> MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows,
> token refresh, and production-grade auto-scaling — so your AI agents can connect to
> third-party services and run freely without you managing any MCP server yourself.
>
> Server page:  https://mewcp.com/mcp/bitrise-mcp
> MewCP docs:   https://docs.mewcp.com
> Full catalog: https://mewcp.com/llms.txt

---

## About

Bitly helps teams manage branded short links, create and customize QR codes, organize campaigns, and track engagement. Generate shareable URLs, update link destinations, retrieve click analytics, and measure traffic by channel to optimize marketing campaigns.

---

## Details

- Server ID: `bitrise-mcp`
- Version: 1.0.0
- Tools: 86
- Authentication: OAuth, managed by MewCP
- Transport: http

---

## Access

The gateway URL below serves your **entire MewCP toolset**, not this server on its
own. Pasting a config snippet is not enough — Bitrise MCP has to be in the toolset
first. In order:

1. Add Bitrise MCP to your toolset at https://mewcp.com/mcp/bitrise-mcp
2. Connect your Bitrise MCP account (OAuth); MewCP stores the credential and attaches it to each call
3. Copy your MewCP API key from the dashboard (Developer)
4. Configure your client with the snippet for it below

Once connected, an agent does **not** see this server's tools as top-level tools.
It sees four meta-tools and reaches everything through them:

- `search(query)` — find tools by keyword across the toolset
- `get_schema(tools)` — full description and arguments for the tools you picked
- `list_accounts(provider)` — only when one app has several connected accounts
- `call_tool(server_maskedId, tool_name, args)` — execute

So the list below is what `search` can return for this server, not a set of
callable tool names on their own.

---

## Tools (86)

Descriptions are truncated to 160 characters; call `get_schema`
for the full text and the argument schema. Where a tool is annotated, its type
is shown — treat `destructive` as irreversible.

- `abort_build` _(destructive)_ — Abort a specific build.
- `abort_pipeline` _(destructive)_ — Abort a pipeline.
- `add_member_to_group` _(destructive)_ — Add a member to a group.
- `add_testers_to_tester_group` _(write)_ — Adds testers to a tester group of a connected app. Testers are added one by one and the request fails only when none could be added, so read the slug-keyed…
- `codepush_create_deployment` _(write)_ — Create a new CodePush deployment for a Bitrise app.
- `codepush_delete_deployment` _(destructive)_ — Delete a CodePush deployment. This action is irreversible.
- `codepush_delete_update` _(destructive)_ — Delete a CodePush update. This action is irreversible.
- `codepush_generate_update_upload_url` _(read)_ — 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…
- `codepush_get_deployment` _(read)_ — Get a specific CodePush deployment by its ID.
- `codepush_get_metrics` _(read)_ — Get workspace-level CodePush usage metrics including data transfer, storage, and monthly active users, along with their limits and billing cycle information.
- `codepush_get_update` _(read)_ — Get a specific CodePush update by its ID.
- `codepush_get_update_status` _(read)_ — Get the processing status of a CodePush update (e.g. pending, ready, failed).
- `codepush_list_deployments` _(read)_ — List CodePush deployments for a Bitrise app.
- `codepush_list_updates` _(read)_ — List CodePush updates for a specific deployment.
- `codepush_patch_update` _(destructive)_ — 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…
- `codepush_promote_deployment` _(destructive)_ — 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.
- `codepush_rollback_deployment` _(destructive)_ — Rollback a CodePush deployment to its previous version, or to a specific package if package_id is provided.
- `codepush_update_deployment` _(write)_ — Update the name of an existing CodePush deployment.
- `create_connected_app` _(write)_ — Add a new Release Management connected app to Bitrise. Adding an internal tester grants the App Tester role on the app; removing them later does not revoke it.
- `create_outgoing_webhook` _(write)_ — Create an outgoing webhook for an app.
- `create_tester_group` _(write)_ — Creates a tester group for a Release Management connected app, optionally with its members: 'user_slugs' for internal groups, 'emails' for external ones.…
- `create_workspace_group` _(write)_ — Create a new group in a workspace.
- `delete_all_cache_items` _(destructive)_ — Delete all key-value cache items belonging to an app.
- `delete_app` _(destructive)_ — Delete an app from Bitrise. When deleting apps belonging to multiple workspaces always confirm that which workspaces' apps the user wants to delete.
- `delete_artifact` _(destructive)_ — Delete a build artifact.
- `delete_cache_item` _(destructive)_ — Delete a key-value cache item.
- `delete_outgoing_webhook` _(destructive)_ — Delete the outgoing webhook of an app.
- `finish_bitrise_app` _(destructive)_ — 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…
- `generate_installable_artifact_upload_url` _(read)_ — 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…
- `get_app` _(read)_ — Get the details of a specific app.
- `get_artifact` _(read)_ — Get a specific build artifact.
- `get_bitrise_yml` _(read)_ — Get the current Bitrise YML config file of a specified Bitrise app.
- `get_build` _(read)_ — Get a specific build of a given app.
- `get_build_bitrise_yml` _(read)_ — Get the bitrise.yml of a build.
- `get_build_log` _(read)_ — Get the build log of a specified build of a Bitrise app.
- `get_build_steps` _(read)_ — Get step statuses of a specific build of a given app.
- `get_cache_item_download_url` _(read)_ — Get the download URL for a cache item.
- `get_connected_app` _(read)_ — Gives back a Release Management connected app for the authenticated account.
- `get_installable_artifact_upload_and_proc_status` _(read)_ — 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…
- `get_pipeline` _(read)_ — Get a pipeline of a given app.
- `get_potential_testers` _(read)_ — Lists the people who can be added to a tester group, with the slug each of them is added by. Pass 'workspace_slug' to list workspace members before a connected…
- `get_tester_group` _(read)_ — Gives back the details of the selected tester group.
- `get_testers` _(read)_ — Gives back a list of testers that has been associated with a tester group related to a specific connected app.
- `get_workspace` _(read)_ — Get details for one workspace
- `get_workspace_groups` _(read)_ — Get the groups in a workspace
- `get_workspace_members` _(read)_ — Get the members of a workspace
- `insights_get_build_series` _(read)_ — 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 %),…
- `insights_get_build_totals` _(read)_ — 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…
- `insights_get_test_series` _(read)_ — 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 %),…
- `insights_get_test_totals` _(read)_ — 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…
- `insights_list_flaky_tests` _(read)_ — 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…
- `invite_member_to_workspace` _(write)_ — Invite new Bitrise users to a workspace.
- `list_apps` _(read)_ — List all apps for the currently authenticated user account
- `list_artifacts` _(read)_ — Get a list of all build artifacts.
- `list_available_stacks` _(read)_ — List available stacks with their machine configurations and version information. When a workspace_slug is provided, returns stacks available for that workspace…
- `list_branches` _(read)_ — List the branches with existing builds of an app's repository.
- `list_build_distribution_version_test_builds` _(read)_ — Gives back a list of test builds for the given build distribution version.
- `list_build_distribution_versions` _(read)_ — Lists Build Distribution versions. Release Management offers a convenient, secure solution to distribute the builds of your mobile apps to testers without…
- `list_build_workflows` _(read)_ — List the workflows of an app.
- `list_builds` _(read)_ — List all the builds of a specified Bitrise app or all accessible builds.
- `list_cache_items` _(read)_ — List the key-value cache items belonging to an app.
- `list_connected_apps` _(read)_ — List Release Management connected apps available for the authenticated account within a workspace.
- `list_group_roles` _(read)_ — List group roles for an app
- `list_installable_artifacts` _(read)_ — List Release Management installable artifacts of a connected app available for the authenticated account.
- `list_outgoing_webhooks` _(read)_ — List the outgoing webhooks of an app.
- `list_pipelines` _(read)_ — List all pipelines and standalone builds of an app.
- `list_tester_groups` _(read)_ — Gives back a list of tester groups related to a specific Release Management connected app.
- `list_workspaces` _(read)_ — List the workspaces the user has access to
- `me` _(read)_ — Get user info for the currently authenticated user account
- `notify_tester_group` _(write)_ — Notifies an internal tester group about a new test build by email.
- `rebuild_pipeline` _(destructive)_ — Rebuild a pipeline.
- `register_app` _(write)_ — 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…
- `register_ssh_key` _(destructive)_ — Add an SSH-key to a specific app.
- `register_webhook` _(write)_ — Register an incoming webhook for a specific application.
- `replace_group_roles` _(destructive)_ — Replace group roles for an app.
- `set_installable_artifact_public_install_page` _(destructive)_ — Changes whether public install page should be available for the installable artifact or not.
- `step_inputs` _(read)_ — List inputs of a step with their defaults, allowed values etc.
- `step_search` _(read)_ — Find steps for building workflows or step bundles in a Bitrise YML config file. Finds steps based on name, description, tags or maintainers.
- `trigger_bitrise_build` _(write)_ — Trigger a new build/pipeline for a specified Bitrise app
- `update_app` _(destructive)_ — Update an app. Only app_slug is required, add only fields you wish to update
- `update_artifact` _(destructive)_ — Update a build artifact.
- `update_bitrise_yml` _(destructive)_ — Update the Bitrise YML config stored on Bitrise. This has no effect if it is stored in the repository.
- `update_connected_app` _(destructive)_ — Updates a connected app.
- `update_outgoing_webhook` _(destructive)_ — 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…
- `update_tester_group` _(destructive)_ — Updates the given tester group. The name and the auto notification setting can be updated optionally.
- `validate_bitrise_yml` _(read)_ — Validate a Bitrise YML config file. Use this tool to verify any changes made in bitrise.yml.

---

## Connect

Gateway URL: https://gateway.mewcp.com/personal/mcp

Every request carries one header:

    Authorization: Bearer <API_KEY>

Replace `API_KEY` with your own key from the dashboard (Developer).

## Apps

### Claude Desktop

Mac & Windows app

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open Claude Desktop → Settings → Developer → "Edit Config"
2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
3. Save the file, then quit Claude Desktop completely and reopen it
4. Start a new conversation — your tool will be available

### VS Code

Copilot / Cline

- Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead.

```json
{
  "mcp.servers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have a "servers" section in your mcp.json? Just add the server entry inside it.

1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
2. Run "MCP: Open User Configuration" to open your mcp.json
3. Paste the snippet and save
4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat

### Cursor

AI-first editor

- macOS: `~/.cursor/mcp.json`
- Windows: `%USERPROFILE%\.cursor\mcp.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it.

1. Open Cursor → Settings → Cursor Settings → MCP
2. Click "Add new global MCP server"
3. Paste the snippet and save
4. Restart Cursor

### Codex

OpenAI's CLI agent

- Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers.

1. Open your Codex MCP config or project-level config file
2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects
3. Save the file and restart Codex
4. Verify the tool is available inside a fresh session

### Claude Code

Anthropic's CLI agent

- ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file and start (or restart) Claude Code
4. Or skip the file entirely and run the CLI command below instead

### OpenCode

Open-source terminal agent

- ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist.

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mewcp": {
      "type": "remote",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcp" section in your opencode.json? Just add the server entry inside it.

1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and start (or restart) OpenCode

### OpenClaw

Self-hosted agent gateway

- ~/.openclaw/openclaw.json — create it if it doesn't exist.

```json
{
  "mcp": {
    "servers": {
      "mewcp": {
        "transport": "streamable-http",
        "url": "https://gateway.mewcp.com/personal/mcp",
        "enabled": true,
        "headers": {
          "Authorization": "Bearer API_KEY"
        }
      }
    }
  }
}
```

Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers".

1. Open ~/.openclaw/openclaw.json in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and restart OpenClaw

### Antigravity

Google's agentic IDE

- ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist.

```json
{
  "mcpServers": {
    "mewcp": {
      "serverUrl": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported.

1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager)
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file — the server connects automatically

### Hermes

Nous Research's CLI agent

- config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key.

```yaml
mcp_servers:
  mewcp:
    url: "https://gateway.mewcp.com/personal/mcp"
    headers:
      Authorization: "Bearer API_KEY"
```

Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it.

1. Open config.yaml in your Hermes config directory
2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any)
3. Save the file, then run /reload-mcp in Hermes (or start a fresh session)
4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected

### DeepSeek Harness

DeepSeek's agent harness

- cordis.yml in your DSH project — or the patch file you mount plugins from.

```yaml
- id: mcp-mewcp
  name: '@deepseek-ai/dsh-mcp-client'
  config:
    serverName: mewcp
    transport: streamable-http
    url: https://gateway.mewcp.com/personal/mcp
    headers:
      Authorization: "Bearer API_KEY"
```

One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry.

1. Open cordis.yml (or your patch file) in your DSH project
2. Paste the entry into your plugin list, keeping the leading dash and indentation
3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__<tool_name>
4. Verify with: dsh web --dump-config | grep -A3 mcp

## SDKs

### Python

fastmcp client

```python
import asyncio
from fastmcp import Client
from fastmcp.client.transports import StreamableHttpTransport

SERVER_URL = "https://gateway.mewcp.com/personal/mcp"
API_KEY = "API_KEY"

transport = StreamableHttpTransport(
    url=SERVER_URL,
    headers={
        "Authorization": f"Bearer {API_KEY}",
    }
)

async def main():
    client = Client(transport)
    async with client:
        tools = await client.list_tools()
        print(tools)

asyncio.run(main())
```

1. Install fastmcp: pip install fastmcp
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run your script

### TypeScript

MCP SDK

```typescript
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const SERVER_URL = "https://gateway.mewcp.com/personal/mcp";
const API_KEY = "API_KEY";

const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), {
  requestInit: {
    headers: {
      Authorization: `Bearer ${API_KEY}`,
    },
  },
});

const client = new Client({ name: "mewcp-client", version: "1.0.0" });
await client.connect(transport);

const tools = await client.listTools();
console.log(tools.tools.map((t) => t.name));
```

1. Install: npm install @modelcontextprotocol/sdk
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)