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

LaunchDarkly Integrations (BYOK) — connector documentation

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

What LaunchDarkly Integrations (BYOK) is for

LaunchDarkly Integrations (BYOK) lets an AI assistant read your own LaunchDarkly Integrations data through the LaunchDarkly Integrations API with a key you supply (LaunchDarkly API access token (a Reader role token is enough; commercial site, not EU or federal)). Read-only: 9 tools (list_webhooks, get_webhook, list_audit_log_subscriptions, list_data_export_destinations, list_integration_configurations, list_flag_import_configurations, list_feature_store_integrations, list_big_segment_store_integrations, list_environment_delivery_configurations). 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 Integrations. LaunchDarkly Integrations 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 LaunchDarkly webhooks are set up and which are on?"
  • "Show LaunchDarkly webhook 5f1a2b3c"
  • "Which LaunchDarkly audit log events are sent to Slack?"
  • "Where does LaunchDarkly export its event data?"
  • "Which Snowflake integration configurations exist in LaunchDarkly?"
  • "Which flag imports from other tools are set up in LaunchDarkly?"

What it does

  • list_webhooks: List the account's webhooks with name, enabled state and tags. Target URLs and signing secrets are not returned.
  • get_webhook: Get one webhook by id with its name, enabled state, tags and the policy statements that decide which events it receives. The URL and secret are not returned.
  • list_audit_log_subscriptions: List the audit log subscriptions of one integration kind (events pushed to Slack, Datadog, Splunk and others) with name, enabled state, tags and status. Credentials and URLs are not returned.
  • list_data_export_destinations: List Data Export destinations (where LaunchDarkly streams flag evaluation and event data) with name, destination kind, enabled state and creation time. Connection settings are not returned.
  • list_integration_configurations: List the configurations of one integration kind from the integrations framework (for example a warehouse destination) with name, enabled flag, creation time and tags. Configuration values are not returned.
  • list_flag_import_configurations: List flag import configurations (Split or Unleash flags imported into LaunchDarkly) with integration, project, name and import status. Settings are not returned.
  • list_feature_store_integrations: List feature store (persistent store) integrations by project and environment with integration kind, name and enabled state. Settings are not returned.
  • list_big_segment_store_integrations: List big segment store integrations (Redis or DynamoDB) by project and environment with name, enabled state and sync status (availability, staleness, last sync).
  • list_environment_delivery_configurations: List the feature store delivery configurations of one environment (which integration delivers flag data there) with name, enabled state and integration kind.

BYOK key

You bring your own LaunchDarkly Integrations 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 Integrations API (app.launchdarkly.com) with a BYOK key; documentation: https://launchdarkly.com/docs/api/integrations. 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 Integrations. LaunchDarkly Integrations 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 Integrations account.

Built for: Worldwide. Languages: English.