GitLab CI (BYOK)

GitLab CI (BYOK) — connector documentation

• MCP endpoint: https://byok-gitlab-ci.connectorbay.com/mcp
• REST API: POST https://byok-gitlab-ci.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-gitlab-ci.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own GitLab CI personal access token (read_api scope), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-gitlab-ci.connectorbay.com/health · Tool schemas: https://byok-gitlab-ci.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-gitlab-ci · agent@connectorbay.com

What GitLab CI (BYOK) is for

GitLab CI (BYOK) lets an AI assistant read your own GitLab CI data through the GitLab CI API with a key you supply (personal access token (read_api scope)). Read-only: 12 tools (list_project_jobs, get_job, list_pipeline_jobs, list_pipeline_trigger_jobs, get_latest_pipeline, get_pipeline_test_report_summary, validate_ci_config, list_resource_groups, get_resource_group, list_resource_group_upcoming_jobs, list_ci_templates, get_ci_template). 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 gitlab.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitLab CI. GitLab CI 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 CI jobs failed recently in gitlab-org/gitlab?"
• "What happened in job 7 of gitlab-org/gitlab?"
• "Which jobs ran in pipeline 287 of gitlab-org/gitlab?"
• "Which downstream pipelines did pipeline 287 of gitlab-org/gitlab trigger?"
• "What is the status of the latest pipeline on main in gitlab-org/gitlab?"
• "How many tests failed in pipeline 287 of gitlab-org/gitlab?"

What it does

• list_project_jobs: List the CI jobs of a project, newest first, with stage, status, failure reason, duration and pipeline. Commit and user details are left out.
• get_job: Get one CI job: name, stage, status, failure reason, ref, coverage, timings and the pipeline it belongs to.
• list_pipeline_jobs: List the jobs of one pipeline (retried jobs only on request), with stage, status, failure reason and timings.
• list_pipeline_trigger_jobs: List the trigger jobs of a pipeline (the jobs that start downstream or child pipelines) with status and the downstream pipeline.
• get_latest_pipeline: Get the latest pipeline of a branch or tag (default branch when no ref is given): status, source, commit SHA, timings and coverage.
• get_pipeline_test_report_summary: Get the unit test report summary of a pipeline: total, passed, failed, skipped and errored tests and the totals per test suite.
• validate_ci_config: Check the project's current .gitlab-ci.yml (or the one on a given ref) and report whether it is valid, with errors and warnings. Nothing is changed.
• list_resource_groups: List a project's CI resource groups (they limit concurrent deployments) with key and process mode.
• get_resource_group: Get one CI resource group: key, process mode and timestamps.
• list_resource_group_upcoming_jobs: List the jobs waiting for a resource group, in the order they will run.
• list_ci_templates: List GitLab's built-in .gitlab-ci.yml templates by key and name (for example Ruby, Python, Docker).
• get_ci_template: Get the text of one built-in .gitlab-ci.yml template by its key.

BYOK key

You bring your own GitLab CI personal access token (read_api scope) (https://gitlab.com/-/user_settings/personal_access_tokens). 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 gitlab.com 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://docs.gitlab.com/api/jobs/ (the API this connector calls, with a BYOK key)

Live from the GitLab CI API (gitlab.com) with a BYOK key; documentation: https://docs.gitlab.com/api/jobs/. 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 GitLab CI. GitLab CI 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 GitLab CI account.

Built for: Worldwide. Languages: English.

GitLab CI (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What GitLab CI (BYOK) is. GitLab CI (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own GitLab CI data: Read a GitLab.com project's CI jobs, trigger jobs, latest pipeline, test report summaries, resource groups and CI templates with your own personal access token. You bring your own GitLab CI personal access token (read_api scope); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one GitLab CI call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to gitlab.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If GitLab CI rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What GitLab CI receives. The request we make on your behalf, including the key and the arguments, under GitLab CI's own terms and privacy policy. GitLab CI acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer GitLab CI gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your GitLab CI data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. GitLab CI (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at GitLab CI at any time to end all access.

Children. GitLab CI (BYOK) is a general-audience service operated by the adult using the assistant, under GitLab CI's own age rules.

Changes. We will post changes here with a new effective date.

GitLab CI (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the GitLab CI (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. GitLab CI (BYOK) provides: Read a GitLab.com project's CI jobs, trigger jobs, latest pipeline, test report summaries, resource groups and CI templates with your own personal access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own GitLab CI credentials and only access data you are allowed to access. GitLab CI's terms apply to your use of GitLab CI; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitLab CI. GitLab CI and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data GitLab CI returns, lightly trimmed; it may be incomplete, delayed or changed by GitLab CI. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your GitLab CI account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent GitLab CI's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; GitLab CI may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your GitLab CI key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action GitLab CI takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-gitlab-ci

GitLab CI (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-gitlab-ci.connectorbay.com/mcp
• REST API: https://byok-gitlab-ci.connectorbay.com/openapi.json
• Live status: https://byok-gitlab-ci.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. GitLab CI (BYOK) never asks for them.