LaunchDarkly Automation

Automation Auto-detects your installed agents and installs the skill to each one.

What This Skill Does

• This skill automates Launch Darkly feature flag workflows, enabling users to manage feature flags programmatically.
• It allows users to enumerate projects and environments, create webhook-driven flag triggers, and manage trigger lifecycles.
• This is useful for teams practicing continuous delivery and experimentation.

When to Use

List Launch Darkly projects Get environments for a project Create flag trigger workflows Automate feature rollouts Manage feature flag lifecycle Integrate with CI/CD pipelines

Key Features

• Lists projects and environments.
• Creates webhook-driven flag triggers.
• Manages trigger lifecycle.
• Supports API key authentication.
• Provides core workflows for common tasks.
• Integrates with external event systems.

Manual Installation

Manual installation View Full Skill Content The complete markdown content that gets installedLaunch Darkly Automation

Automate your Launch Darkly feature flag workflows -- enumerate projects and environments, create webhook-driven flag triggers, manage trigger lifecycle, and audit code references across repositories.

Toolkit docs: composio.dev/toolkits/launch_darkly

Setup

Add the Composio MCP server to your client: https://rube.app/mcp Connect your Launch Darkly account when prompted (API key authentication) Start using the workflows below

Core Workflows

1. List Projects

Use LAUNCH_DARKLY_LIST_PROJECTS to discover all projects and their keys for subsequent operations.

Tool: LAUNCH_DARKLY_LIST_PROJECTS Inputs:

• filter: string (e.g., "query:myproject" or "keys:proj1,proj2" or "tags:mytag")
• expand: string (e.g., "environments" to include env list per project)
• limit: integer (default 20)
• offset: integer (pagination start index)
• sort: string (e.g., "name" or "-name" for descending)

2. Get Environments for a Project

Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list all environments within a project (production, staging, test, etc.).

Tool: LAUNCH_DARKLY_GET_ENVIRONMENTS

• project_key: string (required) -- e.g., "my-project", "default"
• filter: string (e.g., "query:production")
• offset: integer (pagination)
• sort: string (e.g., "name" or "-name")

3. Create a Flag Trigger Workflow

Use LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW to set up automated flag toggles triggered by external events (webhooks, Datadog alerts, etc.).

Tool: LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW

• project_key: string (required)
• feature_flag_key: string (required) -- e.g., "new-feature", "enable-dark-mode"
• environment_key: string (required) -- e.g., "production", "staging"
• integration_key: string (default "generic-trigger") -- or "datadog", "honeycomb", "dynatrace"
• instructions: array of objects (optional):
  • kind: "flag_action" (fixed)
  • action: "turnFlagOn" | "turnFlag Off"
• comment: string (optional) -- description of the trigger purpose

The trigger generates a unique webhook URL that can be called to execute the configured flag action.

4. Delete a Flag Trigger Workflow

Use LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW to permanently remove a trigger and its URL.

Tool: LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW

• feature_flag_key: string (required)
• environment_key: string (required)
• id: string (required) -- the trigger ID returned during creation

Warning: Deletion is irreversible. The trigger and its URL cannot be recovered.

5. List Code Reference Repositories

Use LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES to track where feature flags are used in your codebase.

Tool: LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES

• proj Key: string (optional) -- filter by project key
• flag Key: string (optional) -- filter by feature flag key
• with Branches: string (any value to include branch data)
• withReferencesForDefault Branch: string (any value to include code refs for default branch)

Note: Code references is an Enterprise feature requiring code-reference-repository write permissions.

Known Pitfalls

Quick Reference

5. List Code Reference