Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

LaunchDarkly Releases (BYOK) — connector documentation

  • MCP endpoint: https://byok-launchdarkly-releases.connectorbay.com/mcp
  • REST API: POST https://byok-launchdarkly-releases.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-launchdarkly-releases.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own LaunchDarkly Releases LaunchDarkly API access token (a Reader role token is enough; commercial site, not EU or federal), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-launchdarkly-releases.connectorbay.com/health · Tool schemas: https://byok-launchdarkly-releases.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-launchdarkly-releases · agent@connectorbay.com

What LaunchDarkly Releases (BYOK) is for

LaunchDarkly Releases (BYOK) lets an AI assistant read your own LaunchDarkly Releases data through the LaunchDarkly Releases API with a key you supply (LaunchDarkly API access token (a Reader role token is enough; commercial site, not EU or federal)). Read-only: 8 tools (list_release_pipelines, get_release_pipeline, list_pipeline_releases, get_flag_release, list_flag_workflows, list_approval_requests, list_flag_approval_requests, get_flag_status_across_environments). 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 app.launchdarkly.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LaunchDarkly Releases. LaunchDarkly Releases 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 release pipelines does the default LaunchDarkly project have?"
  • "Show the phases of the standard-rollout release pipeline"
  • "Which flags are currently releasing through standard-rollout?"
  • "Is flag new-checkout part of a release pipeline and which phase is it in?"
  • "What workflows are set up for flag new-checkout in production?"
  • "Which approval requests are still pending?"

What it does

  • list_release_pipelines: List a project's release pipelines with description, default flag and creation time.
  • get_release_pipeline: Get one release pipeline with its ordered phases (name and audiences).
  • list_pipeline_releases: List the flag releases moving through a pipeline with the active phase, its status and start and completion time. Counts of active and completed releases come with it.
  • get_flag_release: Get the release a feature flag is part of: pipeline, phases and when it was canceled, if it was.
  • list_flag_workflows: List the workflows (scheduled and conditional changes) of a flag in one environment with kind, creation time and execution state.
  • list_approval_requests: List approval requests across the account with status, review status, resource and timing. Filter expressions are passed through; example: status anyOf ["pending"].
  • list_flag_approval_requests: List the approval requests for one flag in one environment.
  • get_flag_status_across_environments: Show a flag's lifecycle status (new, inactive, active or launched) and last request time in each environment.

BYOK key

You bring your own LaunchDarkly Releases LaunchDarkly API access token (a Reader role token is enough; commercial site, not EU or federal) (https://app.launchdarkly.com/settings/authorization). 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 app.launchdarkly.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 LaunchDarkly Releases API (app.launchdarkly.com) with a BYOK key; documentation: https://launchdarkly.com/docs/api/release-pipelines. 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 LaunchDarkly Releases. LaunchDarkly Releases 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 LaunchDarkly Releases account.

Built for: Worldwide. Languages: English.