Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
GitLab Repository (BYOK) icon

GitLab Repository (BYOK)

Read a GitLab.com project's branches, tags, file tree, commit detail, contributors and comparisons between refs with your own personal access token

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderGitLab Repositoryunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which branches does gitlab-org/gitlab have that start with 'fix'?
Tools called
list_branches
Is the 'main' branch of gitlab-org/gitlab protected?
Tools called
get_branch
What are the latest tags of gitlab-org/gitlab?
Tools called
list_tags
What files are in the doc folder of gitlab-org/gitlab on main?
Tools called
list_repository_tree
How many lines did commit 61049424 of gitlab-org/gitlab change?
Tools called
get_commit
Which branches and tags contain commit 61049424 in gitlab-org/gitlab?
Tools called
list_commit_refs

About

GitLab Repository (BYOK) lets an AI assistant read your own GitLab Repository data through the GitLab Repository API with a key you supply (personal access token (read_api or read_repository scope)). Read-only: 10 tools (list_branches, get_branch, list_tags, list_repository_tree, get_commit, list_commit_refs, list_commit_statuses, list_commit_merge_requests, list_contributors, compare_refs). 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 Repository. GitLab Repository and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the GitLab Repository API (gitlab.com) with a BYOK key; documentation: https://docs.gitlab.com/api/rest/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

10 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data10 tools
  • List branchesList a project's branches alphabetically with default, protected and merged flags and the head commit title and date.
  • Get branchGet one branch: head commit, protected and merged flags, whether it is the default branch.
  • List tagsList a project's tags, newest first by default, with message, target commit and any linked release.
  • List repository treeList the files and folders at a path of a project's repository for a branch, tag or commit, optionally recursively.
  • Get commitGet one commit by SHA, branch or tag name: title, author, dates, line statistics and the last pipeline run on it.
  • List commit refsList the branches and tags that contain a commit.
  • List commit statusesList the CI statuses posted for a commit (latest per job by default) with name, state, stage, pipeline and timing.
  • List commit merge requestsList the merge requests that contain a commit, with state, branches and merge time.
  • List contributorsList the contributors of a project's repository by commit count with additions and deletions; email addresses are left out.
  • Compare refsCompare two branches, tags or commits and list the commits between them (the diff text is left out).

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-gitlab-repository.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 10 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-gitlab-repository.connectorbay.com/mcp
RESTPOST https://byok-gitlab-repository.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-gitlab-repository.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your personal access token (read_api or read_repository scope) in the X-Upstream-Key header (get one at gitlab.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

GitLab Repository connector: questions and answers

What is the GitLab Repository connector?

GitLab Repository (BYOK) lets an AI assistant read your own GitLab Repository data through the GitLab Repository API with a key you supply… It is a hosted MCP server with 10 tools such as List branches, Get branch, List tags, List repository tree, Get commit, List commit refs, published by Unify Dynamics LLC. It is independent and not affiliated with GitLab Repository.

How do I connect GitLab Repository to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-gitlab-repository.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-gitlab-repository.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-gitlab-repository.json.

Do I need a GitLab Repository account or API key?

Yes: this is a bring-your-own-key connector. Create a personal access token (read_api or read_repository scope) at https://gitlab.com/-/user_settings/personal_access_tokens and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is GitLab Repository read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the GitLab Repository connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

updown.io (BYOK)

Read your updown.io website monitors: status, uptime, downtime periods, response-time metrics, SSL and domain expiry with BYOK

Live · MCP + REST5 tools

Upstash (BYOK)

Read your Upstash Redis databases, usage stats, backups, teams and audit log with BYOK

Live · MCP + REST7 tools

Upstash QStash EU (BYOK)

Read your Upstash QStash queues, schedules, URL groups, delivery logs, dead letter queue and flow control on the EU Central region with your own QStash token

Live · MCP + REST12 tools

Upstash QStash US (BYOK)

Read your Upstash QStash queues, schedules, URL groups, delivery logs, dead letter queue and flow control on the US East region with your own QStash token

Live · MCP + REST12 tools

UptimeRobot (BYOK)

Read your UptimeRobot monitors, uptime and response-time statistics, incidents, maintenance windows and status pages with your own API key

Live · MCP + REST10 tools

UserCheck (BYOK)

Check email addresses and domains for disposable, spam, relay and role-account signals, and read your UserCheck blocklist, gates and usage with your own API key

Live · MCP + REST9 tools

Documentation

Back to top

GitLab Repository (BYOK) — connector documentation

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

What GitLab Repository (BYOK) is for

GitLab Repository (BYOK) lets an AI assistant read your own GitLab Repository data through the GitLab Repository API with a key you supply (personal access token (read_api or read_repository scope)). Read-only: 10 tools (list_branches, get_branch, list_tags, list_repository_tree, get_commit, list_commit_refs, list_commit_statuses, list_commit_merge_requests, list_contributors, compare_refs). 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 Repository. GitLab Repository 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 branches does gitlab-org/gitlab have that start with 'fix'?"
  • "Is the 'main' branch of gitlab-org/gitlab protected?"
  • "What are the latest tags of gitlab-org/gitlab?"
  • "What files are in the doc folder of gitlab-org/gitlab on main?"
  • "How many lines did commit 61049424 of gitlab-org/gitlab change?"
  • "Which branches and tags contain commit 61049424 in gitlab-org/gitlab?"

What it does

  • list_branches: List a project's branches alphabetically with default, protected and merged flags and the head commit title and date. Up to 100 per page.
  • get_branch: Get one branch: head commit, protected and merged flags, whether it is the default branch.
  • list_tags: List a project's tags, newest first by default, with message, target commit and any linked release.
  • list_repository_tree: List the files and folders at a path of a project's repository for a branch, tag or commit, optionally recursively.
  • get_commit: Get one commit by SHA, branch or tag name: title, author, dates, line statistics and the last pipeline run on it.
  • list_commit_refs: List the branches and tags that contain a commit.
  • list_commit_statuses: List the CI statuses posted for a commit (latest per job by default) with name, state, stage, pipeline and timing.
  • list_commit_merge_requests: List the merge requests that contain a commit, with state, branches and merge time.
  • list_contributors: List the contributors of a project's repository by commit count with additions and deletions; email addresses are left out.
  • compare_refs: Compare two branches, tags or commits and list the commits between them (the diff text is left out).

BYOK key

You bring your own GitLab Repository personal access token (read_api or read_repository 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

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

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

GitLab Repository (BYOK) — Privacy Policy

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

What GitLab Repository (BYOK) is. GitLab Repository (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own GitLab Repository data: Read a GitLab.com project's branches, tags, file tree, commit detail, contributors and comparisons between refs with your own personal access token. You bring your own GitLab Repository personal access token (read_api or read_repository scope); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one GitLab Repository 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 Repository 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 Repository receives. The request we make on your behalf, including the key and the arguments, under GitLab Repository's own terms and privacy policy. GitLab Repository 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 Repository 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 Repository 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 Repository (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 Repository at any time to end all access.

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

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

Terms of service

Back to top

GitLab Repository (BYOK) — Terms of Service

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

  1. The Service. GitLab Repository (BYOK) provides: Read a GitLab.com project's branches, tags, file tree, commit detail, contributors and comparisons between refs 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 Repository credentials and only access data you are allowed to access. GitLab Repository's terms apply to your use of GitLab Repository; 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 Repository. GitLab Repository 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 Repository returns, lightly trimmed; it may be incomplete, delayed or changed by GitLab Repository. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your GitLab Repository 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 Repository'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 Repository 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 Repository 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 Repository 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-repository

GitLab Repository (BYOK) support

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

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 Repository (BYOK) never asks for them.

Get GitLab Repository (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own GitLab Repository personal access token (read_api or read_repository scope). Create one at https://gitlab.com/-/user_settings/personal_access_tokens, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to GitLab Repository. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with GitLab Repository.