launchdarkly-automationlisted

# LaunchDarkly Automation Automate your LaunchDarkly 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](https://composio.dev/toolkits/launch_darkly) --- ## Setup 1. Add the Composio MCP server to your client: `https://rube.app/mcp` 2. Connect your LaunchDarkly account when prompted (API key authentication) 3. 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 Inputs: - project_key: string (required) -- e.g., "my-project", "default" - filter: string (e.g., "query:production") - limit: integer (default 20) - offset: integer (pagination) - sort: string (e.g., "name" or "-name") ``` ### 3. Create a Flag Trigger Workflow Use `LAUNCH_D