Bitrise Insights MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bitrise-insights-get-flaky-testsA | Get comprehensive flaky tests data from Bitrise Insights including test cases and detailed test execution information: build IDs, run durations, pass/fail status, timestamps, branches, stacks, and commit hashes. Uses browser session authentication - a browser window will open automatically when login is required (specialized for flaky test analysis) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. Its purpose is clearly limited to retrieving flaky test data.
The single tool name follows a clear action-oriented convention: bitrise-insights-get-flaky-tests. There is no mixed naming style or contradictory pattern to cause confusion.
A single tool is too few for a server named Bitrise Insights, which implies a broader analytics surface. While it may handle a narrow flaky-test workflow, it feels under-scoped.
The server only exposes flaky-test retrieval, with no tools for other Bitrise Insights data such as builds, test suites, trends, or general analytics. This is a significant coverage gap for the implied domain.