GitLab Runners (BYOK)

GitLab Runners (BYOK) — connector documentation

• MCP endpoint: https://byok-gitlab-runners.connectorbay.com/mcp
• REST API: POST https://byok-gitlab-runners.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-gitlab-runners.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own GitLab Runners 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-runners.connectorbay.com/health · Tool schemas: https://byok-gitlab-runners.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-gitlab-runners · agent@connectorbay.com

What GitLab Runners (BYOK) is for

GitLab Runners (BYOK) lets an AI assistant read your own GitLab Runners data through the GitLab Runners API with a key you supply (personal access token (read_api scope)). Read-only: 6 tools (list_runners, get_runner, list_runner_jobs, list_runner_managers, list_project_runners, list_group_runners). 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 Runners. GitLab Runners 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 of my GitLab CI runners are offline?"
• "Show details of GitLab runner 6"
• "What jobs has GitLab runner 6 processed lately?"
• "Which machines run GitLab runner 6 and which version?"
• "Which CI runners can gitlab-org/gitlab use?"
• "Which CI runners does the gitlab-org group have?"

What it does

• list_runners: List the CI runners you can see (group and project runners you own or maintain, plus instance runners) with type, status and whether they are paused.
• get_runner: Get one runner: description, type, status, last contact time, tags, access level, maximum job timeout and the projects it serves.
• list_runner_jobs: List jobs a runner is running or has run, limited to projects where you have at least Reporter access, with status, ref, timing and project.
• list_runner_managers: List the runner managers (machines) of one runner with version, platform, architecture, last contact and job execution status.
• list_project_runners: List runners available to a project, including group runners and enabled instance runners (needs Maintainer or Auditor access).
• list_group_runners: List runners available to a group, including ancestor group runners and enabled instance runners (needs Owner or Auditor access).

BYOK key

You bring your own GitLab Runners 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/runners/ (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

GitLab Runners (BYOK) — Privacy Policy

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

What GitLab Runners (BYOK) is. GitLab Runners (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own GitLab Runners data: Read GitLab.com CI runners available to you, their status, managers and processed jobs with your own personal access token. You bring your own GitLab Runners 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 Runners 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 Runners 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 Runners receives. The request we make on your behalf, including the key and the arguments, under GitLab Runners's own terms and privacy policy. GitLab Runners 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 Runners 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 Runners 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 Runners (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 Runners at any time to end all access.

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

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

GitLab Runners (BYOK) — Terms of Service

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

1. The Service. GitLab Runners (BYOK) provides: Read GitLab.com CI runners available to you, their status, managers and processed jobs 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 Runners credentials and only access data you are allowed to access. GitLab Runners's terms apply to your use of GitLab Runners; 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 Runners. GitLab Runners 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 Runners returns, lightly trimmed; it may be incomplete, delayed or changed by GitLab Runners. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your GitLab Runners 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 Runners'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 Runners 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 Runners 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 Runners 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-runners

GitLab Runners (BYOK) support

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

• MCP endpoint: https://byok-gitlab-runners.connectorbay.com/mcp
• REST API: https://byok-gitlab-runners.connectorbay.com/openapi.json
• Live status: https://byok-gitlab-runners.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 Runners (BYOK) never asks for them.