Trunk Merge Queue (BYOK)

Trunk Merge Queue (BYOK) — connector documentation

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

What Trunk Merge Queue (BYOK) is for

Trunk Merge Queue (BYOK) lets an AI assistant read your own Trunk Merge Queue data through the Trunk Merge Queue API with a key you supply (Trunk organization API token). Read-only: 5 tools (get_queue, list_queue_pull_requests, get_submitted_pull_request, list_testing_results, get_testing_details). 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 api.trunk.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Trunk Merge Queue. Trunk Merge Queue 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 is the state of the Trunk merge queue for main?"
• "Which pull requests are in the Trunk merge queue?"
• "What is the status of PR 482 in the Trunk merge queue?"
• "How did the Trunk merge queue tests go this week?"
• "What is the Trunk merge queue testing for run tr_1?"

What it does

• get_queue: Get one merge queue: state (running, paused, draining), mode, concurrency, batching and merge settings, required statuses, and the pull requests currently enqueued.
• list_queue_pull_requests: List pull requests in a merge queue, optionally by state and time range, with state, priority and PR title, sha and author.
• get_submitted_pull_request: Get one submitted pull request in a merge queue: state, readiness, and optionally the state timeline with test run details.
• list_testing_results: List completed merge queue testing for a time range: PR number, outcome, duration and whether it entered bisection.
• get_testing_details: Get details of a merge queue test run: test branch and sha, status, required status checks and the pull requests tested together.

BYOK key

You bring your own Trunk Merge Queue Trunk organization API token (https://app.trunk.io/). 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 api.trunk.io 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.trunk.io/merge-queue/reference/merge (the API this connector calls, with a BYOK key)

Live from the Trunk Merge Queue API (api.trunk.io) with a BYOK key; documentation: https://docs.trunk.io/merge-queue/reference/merge. 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 Trunk Merge Queue. Trunk Merge Queue 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 Trunk Merge Queue account.

Built for: Worldwide. Languages: English.

Trunk Merge Queue (BYOK) — Privacy Policy

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

What Trunk Merge Queue (BYOK) is. Trunk Merge Queue (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Trunk Merge Queue data: Read your Trunk Merge Queue: queue settings, queued pull requests, their state timeline and testing results, with your own API token. You bring your own Trunk Merge Queue Trunk organization API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Trunk Merge Queue 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 api.trunk.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Trunk Merge Queue 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 Trunk Merge Queue receives. The request we make on your behalf, including the key and the arguments, under Trunk Merge Queue's own terms and privacy policy (https://trunk.io/terms). Trunk Merge Queue acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Trunk Merge Queue 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 Trunk Merge Queue 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. Trunk Merge Queue (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 Trunk Merge Queue at any time to end all access.

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

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

Trunk Merge Queue (BYOK) — Terms of Service

Effective 16 October 2026. These terms govern use of the Trunk Merge Queue (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Trunk Merge Queue (BYOK) provides: Read your Trunk Merge Queue: queue settings, queued pull requests, their state timeline and testing results, with your own API 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 Trunk Merge Queue credentials and only access data you are allowed to access. Trunk Merge Queue's terms (https://trunk.io/terms) apply to your use of Trunk Merge Queue; 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 Trunk Merge Queue. Trunk Merge Queue 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 Trunk Merge Queue returns, lightly trimmed; it may be incomplete, delayed or changed by Trunk Merge Queue. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Trunk Merge Queue 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 Trunk Merge Queue'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; Trunk Merge Queue 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 Trunk Merge Queue 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 Trunk Merge Queue 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-trunk-merge-queue

Trunk Merge Queue (BYOK) support

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

• MCP endpoint: https://byok-trunk-merge-queue.connectorbay.com/mcp
• REST API: https://byok-trunk-merge-queue.connectorbay.com/openapi.json
• Live status: https://byok-trunk-merge-queue.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. Trunk Merge Queue (BYOK) never asks for them.