Bitrise Config (BYOK) — connector documentation
- MCP endpoint:
https://byok-bitrise-config.connectorbay.com/mcp - REST API:
POST https://byok-bitrise-config.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-bitrise-config.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Bitrise Config personal access token, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-bitrise-config.connectorbay.com/health· Tool schemas:https://byok-bitrise-config.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-bitrise-config · agent@connectorbay.com
What Bitrise Config (BYOK) is for
Bitrise Config (BYOK) lets an AI assistant read your own Bitrise Config data through the Bitrise Config API with a key you supply (personal access token). Read-only: 7 tools (list_addons, list_app_addons, list_app_secret_names, list_org_secret_names, list_cache_items, search_steps, list_step_inputs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.bitrise.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitrise Config. Bitrise Config and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which add-ons does Bitrise offer?"
- "Which add-ons are enabled on my Bitrise app?"
- "Which secrets are defined for my Bitrise app and are any exposed to pull requests?"
- "Which organization-wide secrets does my Bitrise organization have?"
- "How big is the Bitrise build cache of my app and when was it last used?"
- "Find Bitrise steps for deploying to Firebase."
What it does
list_addons: List the Bitrise add-ons available on the platform with title, summary, categories, platforms and whether they are in beta.list_app_addons: List the add-ons of one app with whether each is enabled, its plan name and price.list_app_secret_names: List an app's Secrets by name with scope and flags (protected, exposed for pull requests, expand in step inputs). Secret values are never returned.list_org_secret_names: List an organization's Secrets by name with scope and flags. Secret values are never returned.list_cache_items: List an app's key-value cache items with cache key, archive size, creation, expiry and last use time. Page with the 'next' cursor.search_steps: Search the Bitrise Step library by phrase, optionally by category or maintainer (bitrise, verified, community), with latest version and inputs.list_step_inputs: List the inputs of one Step version with title, summary, whether required, default value and allowed options.
BYOK key
You bring your own Bitrise Config personal access token (https://docs.bitrise.io/en/bitrise-platform/accounts/personal-access-tokens.html). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.bitrise.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://api-docs.bitrise.io/ (the API this connector calls, with a BYOK key)
Live from the Bitrise Config API (api.bitrise.io) with a BYOK key; documentation: https://api-docs.bitrise.io/. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitrise Config. Bitrise Config and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Bitrise Config account.
Built for: Worldwide. Languages: English.