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

Mergify (BYOK)

Read your Mergify merge queue state, queue statistics, activity log and CI test health for GitHub repositories with your own application key

Unify Dynamics LLC

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

Try asking

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

Which Mergify application key and account scope am I using?
Tools called
get_application
What is in the Mergify merge queue of acme/web right now?
Tools called
get_merge_queue_status
Which pull requests are in the Mergify queues of acme/web?
Tools called
list_merge_queues
Which merge queue rules does acme/web have in Mergify?
Tools called
get_queue_configuration
Is the Mergify merge queue of acme/web paused?
Tools called
get_queue_pause
What did Mergify do on pull request 42 of acme/web?
Tools called
list_activity_events

About

Mergify (BYOK) lets an AI assistant read your own Mergify data through the Mergify API with a key you supply (Mergify application key). Read-only: 12 tools (get_application, get_merge_queue_status, list_merge_queues, get_queue_configuration, get_queue_pause, list_activity_events, get_time_to_merge, get_queue_size_stats, get_queue_failure_rate, search_ci_tests, get_ci_test, list_quarantined_tests). 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.mergify.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mergify. Mergify and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Mergify API (api.mergify.com) with a BYOK key; documentation: https://docs.mergify.com/api/. 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

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

OpenAPI
Read your data12 tools
  • Get applicationShow which Mergify application key is in use: its ID, name, scope and the GitHub account it is limited to.
  • Get merge queue statusShow the live merge queue of a repository: queue mode, pause state, batches being tested and pull requests waiting, with estimated merge times.
  • List merge queuesList the merge queues of a repository with the branch of each and the pull requests in it.
  • Get queue configurationShow the merge queue rules (names and settings) Mergify reads from a repository's configuration.
  • Get queue pauseShow whether the merge queue of a repository is paused, with the reason and pause date.
  • List activity eventsList recent Mergify activity events of a repository (queue entries, merges, check results, failures) newest first, filterable by pull request,…
  • Get time to mergeShow time to merge statistics for every merge queue of a repository, optionally at a given moment or for one branch.
  • Get queue size statsShow how many pull requests were in the merge queue over time, grouped by base branch and queue.
  • Get queue failure rateShow the merge queue failure rate over time, grouped by base branch and queue.
  • Search ci testsSearch the CI tests Mergify tracks in a repository with flakiness metrics, filtered by name (globs allowed), pipeline, job or quarantine state.
  • Get ci testGet one CI test by ID: health status, success, failure and flakiness ratios, first and last failure, framework and file path.
  • List quarantined testsList the CI tests quarantined in a repository with reason, scope (branch, pipeline, job), source and health.

Information

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

More like this

More in Other

Cumulocity Operations (BYOK)

List your Cumulocity devices and device operations, and send confirmed restart and configuration operations to a device with your own tenant user

Live · MCP + REST6 tools

Golioth RPC (BYOK)

Look up your Golioth projects and devices and call confirmed remote procedures on a device with your own project API key

Live · MCP + REST4 tools

Losant Commands (BYOK)

Look up your Losant devices, their state and recent commands, and send confirmed commands to a device with your own access token

Live · MCP + REST5 tools

Ubidots Values (BYOK)

Read your Ubidots devices and variables and write confirmed variable values (for example a relay or setpoint variable) with your own account token

Live · MCP + REST6 tools

Things Board Control (BYOK)

Look up your ThingsBoard Cloud devices and send confirmed one-way RPC commands to them with your own API key

Live · MCP + REST6 tools

Govee (BYOK)

Read your Govee devices and their state and change lights and plugs (power, brightness, color, color temperature) with your own Govee API key

Live · MCP + REST8 tools

Get Mergify (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Mergify Mergify application key. Create one at https://dashboard.mergify.com, 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 Mergify. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Mergify.