GitLab Planning (BYOK)

GitLab Planning (BYOK) — connector documentation

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

What GitLab Planning (BYOK) is for

GitLab Planning (BYOK) lets an AI assistant read your own GitLab Planning data through the GitLab Planning API with a key you supply (personal access token (read_api scope)). Read-only: 9 tools (list_milestones, get_milestone, list_milestone_issues, list_milestone_merge_requests, list_labels, get_label, list_boards, get_board, list_board_lists). 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 Planning. GitLab Planning 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:

• "What active milestones does gitlab-org/gitlab have?"
• "Show milestone 12 of gitlab-org/gitlab"
• "Which issues are in milestone 12 of gitlab-org/gitlab?"
• "Which merge requests are in milestone 12 of gitlab-org/gitlab?"
• "What labels does gitlab-org/gitlab use and how many open issues has each?"
• "Show the 'bug' label of gitlab-org/gitlab"

What it does

• list_milestones: List a project's milestones with state, start and due dates and whether they have expired.
• get_milestone: Get one milestone with its dates, state and description.
• list_milestone_issues: List the issues assigned to a milestone with state, author, labels and dates.
• list_milestone_merge_requests: List the merge requests assigned to a milestone with state, branches and dates.
• list_labels: List a project's labels (including ancestor group labels by default) with colour, description and optional issue and merge request counts.
• get_label: Get one project label by numeric ID or by its title.
• list_boards: List a project's issue boards with their name, whether the backlog and closed lists are hidden, and the board milestone.
• get_board: Get one issue board with its name and display options.
• list_board_lists: List the lists (columns) of an issue board in order with their label, position and issue limit; the open and closed lists are not included.

BYOK key

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

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

Built for: Worldwide. Languages: English.

GitLab Planning (BYOK) — Privacy Policy

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

What GitLab Planning (BYOK) is. GitLab Planning (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own GitLab Planning data: Read a GitLab.com project's milestones, labels, issue boards and board lists with your own personal access token. You bring your own GitLab Planning 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 Planning 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 Planning 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 Planning receives. The request we make on your behalf, including the key and the arguments, under GitLab Planning's own terms and privacy policy. GitLab Planning 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 Planning 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 Planning 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 Planning (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 Planning at any time to end all access.

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

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

GitLab Planning (BYOK) — Terms of Service

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

1. The Service. GitLab Planning (BYOK) provides: Read a GitLab.com project's milestones, labels, issue boards and board lists 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 Planning credentials and only access data you are allowed to access. GitLab Planning's terms apply to your use of GitLab Planning; 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 Planning. GitLab Planning 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 Planning returns, lightly trimmed; it may be incomplete, delayed or changed by GitLab Planning. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your GitLab Planning 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 Planning'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 Planning 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 Planning 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 Planning 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-planning

GitLab Planning (BYOK) support

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

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