
How to add Bitrise MCP Server to Windsurf
Manage Bitrise apps, builds, artifacts, pipelines and releases from your AI assistant. Paste the config into ~/.codeium/windsurf/mcp_config.json and restart Windsurf.
Last updated June 14, 2026 · 39★ · http · oauth
Windsurf config for Bitrise MCP Server
claude mcp add --transport http bitrise https://mcp.bitrise.io{
"mcpServers": {
"bitrise-mcp-server": {
"serverUrl": "https://mcp.bitrise.io"
}
}
}Remote server — no local install needed. Restart the client after saving the config.
Setup steps
- 1Open Windsurf → Cascade → the hammer/MCP icon → Configure (or edit ~/.codeium/windsurf/mcp_config.json).
- 2Paste the Bitrise MCP Server config below.
- 3Fill in placeholder secrets, then save.
- 4Click Refresh in the MCP panel.
- 5Bitrise MCP Server's tools become available to Cascade.
Before you start
- A Bitrise account
- An MCP client that supports Streamable HTTP (and MCP OAuth for the recommended remote setup), e.g. Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Gemini CLI, or AWS Kiro
- For the local stdio server: Go (>=1.25) installed and a Bitrise Personal Access Token (BITRISE_TOKEN)
What Bitrise MCP Server can do in Windsurf
list_appsList all the apps available for the authenticated account.
register_appAdd a new app to Bitrise.
finish_bitrise_appFinish the setup of a Bitrise app.
get_appGet the details of a specific app.
delete_appDelete an app from Bitrise.
update_appUpdate an app.
get_bitrise_ymlGet the current Bitrise YML config file of a specified app.
update_bitrise_ymlUpdate the Bitrise YML config file of a specified app.
Security
The recommended remote server uses OAuth — you sign in to your Bitrise account in the browser and approve a consent screen on first tool use; no token to store. For PAT-based fallback, create a Bitrise API token under Account Settings -> Security and pass it as an Authorization: Bearer header; avoid hardcoding it (store it in a gitignored .env and reference it). The local stdio server requires a BITRISE_TOKEN environment variable. Tools include destructive operations (delete app, delete artifacts, abort builds, replace group roles, irreversible CodePush deletes), so review tool calls before approving.
Bitrise MCP Server + Windsurf FAQ
Where is the Windsurf config file?
Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Paste the Bitrise MCP Server config there under the "mcpServers" key and restart the client.
Is Bitrise MCP Server safe to use with Windsurf?
The recommended remote server uses OAuth — you sign in to your Bitrise account in the browser and approve a consent screen on first tool use; no token to store. For PAT-based fallback, create a Bitrise API token under Account Settings -> Security and pass it as an Authorization: Bearer header; avoid hardcoding it (store it in a gitignored .env and reference it). The local stdio server requires a BITRISE_TOKEN environment variable. Tools include destructive operations (delete app, delete artifacts, abort builds, replace group roles, irreversible CodePush deletes), so review tool calls before approving.
How do I authenticate?
The recommended remote server at https://mcp.bitrise.io uses OAuth: on first tool use your client opens a browser to sign in to Bitrise and approve a consent screen — no token to copy. For clients without MCP OAuth, you can pass a Bitrise Personal Access Token as an Authorization: Bearer header instead. The local stdio server uses a BITRISE_TOKEN environment variable.
Do I need to run anything locally?
No. The recommended setup is the hosted remote server over Streamable HTTP, so there is nothing to install. A local stdio server is available as an alternative and requires Go (>=1.25) plus a Bitrise PAT (run via `go run github.com/bitrise-io/bitrise-mcp/v2@v2`).
Which clients are supported?
Installation guides are provided for Claude Desktop and Claude Code, Cursor, VS Code, GitHub Copilot in JetBrains/Visual Studio/Eclipse/Xcode, Windsurf, Gemini CLI, and AWS Kiro.