Launch_darkly Automation

What This Skill Does

• This skill automates Launc Darkly operations through Composio's LaunchDarkly toolkit via Rube MCP.
• It allows users to manage feature flags, environments, and segments programmatically.
• This is useful for teams needing to manage LaunchDarkly at scale or integrate it into automated workflows.

When to Use

• List available Launc Darkly tools.
• Execute LaunchDarkly operations.
• Automate feature flag management.
• Manage environments and segments.
• Integrate with CI/CD pipelines.
• Create multi-step workflows.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Launc Darkly connection.
• Dynamically discovers available tools and schemas.
• Provides a structured workflow for tool execution.
• Emphasizes the importance of checking the connection status.
• Supports multi-step workflows.

Manual Installation

Automate Launc Darkly operations through Composio's LaunchDarkly toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/launch_darkly

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Launc Darkly connection via RUBE_MANAGE_CONNECTIONS with toolkit launch_darkly Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit launch_darkly If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS: queries=[{"use_case": "feature flags, environments, segments, and rollout management", "known_fields": ""}]

This returns: Available tool slugs for Launc Darkly Recommended execution plan steps Known pitfalls and edge cases Input schemas for each tool

Core Workflows

1. Discover Available LaunchDarkly Tools

RUBE_SEARCH_TOOLS: queries: - use_case: "list all available LaunchDarkly tools and capabilities"

Review the returned tools, their descriptions, and input schemas before proceeding.

2. Execute LaunchDarkly Operations

After discovering tools, execute them via:

RUBE_MULTI_EXECUTE_TOOL: tools: - tool_slug: "<discovered_tool_slug>" arguments: {<schema-compliant arguments>} memory: {} sync_response_to_workbench: false

3. Multi-Step Workflows

For complex workflows involving multiple Launc Darkly operations:

Search for all relevant tools: RUBE_SEARCH_TOOLS with specific use case Execute prerequisite steps first (e.g., fetch before update) Pass data between steps using tool responses Use RUBE_REMOTE_WORKBENCH for bulk operations or data processing

Common Patterns

Search Before Action

Always search for existing resources before creating new ones to avoid duplicates.

Pagination

Many list operations support pagination. Check responses for next_cursor or page_token and continue fetching until exhausted.

Error Handling

Check tool responses for errors before proceeding If a tool fails, verify the connection is still ACTIVE Re-authenticate via RUBE_MANAGE_CONNECTIONS if connection expired

Batch Operations

For bulk operations, use RUBE_REMOTE_WORKBENCH with run_composio_tool() in a loop with Threa PoolExecutor for parallel execution.

Known Pitfalls

Always search tools first: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via RUBE_SEARCH_TOOLS. Check connection status: Ensure the Launc Darkly connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. Respect rate limits: If you receive rate limit errors, reduce request frequency and implement backoff. Validate schemas: Always pass strictly schema-compliant arguments. Use RUBE_GET_TOOL_SCHEMAS to load full input schemas when schem Ref is returned instead of input_schema.

Quick Reference

Toolkit docs: composio.dev/toolkits/launch_darklyLaunchDarkly Automation via Rube MCP

Automate Launc Darkly operations through Composio's LaunchDarkly toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/launch_darkly

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Launc Darkly connection via RUBE_MANAGE_CONNECTIONS with toolkit launch_darkly Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit launch_darkly If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS: queries=[{"use_case": "feature flags, environments, segments, and rollout management", "known_fields": ""}]

This returns: Available tool slugs for Launc Darkly Recommended execution plan steps Known pitfalls and edge cases Input schemas for each tool

Core Workflows

1. Discover Available LaunchDarkly Tools

RUBE_SEARCH_TOOLS: queries: - use_case: "list all available LaunchDarkly tools and capabilities"

Review the returned tools, their descriptions, and input schemas before proceeding.

2. Execute LaunchDarkly Operations

After discovering tools, execute them via:

RUBE_MULTI_EXECUTE_TOOL: tools: - tool_slug: "<discovered_tool_slug>" arguments: {<schema-compliant arguments>} memory: {} sync_response_to_workbench: false

3. Multi-Step Workflows

For complex workflows involving multiple Launc Darkly operations:

Search for all relevant tools: RUBE_SEARCH_TOOLS with specific use case Execute prerequisite steps first (e.g., fetch before update) Pass data between steps using tool responses Use RUBE_REMOTE_WORKBENCH for bulk operations or data processing

Common Patterns

Search Before Action

Always search for existing resources before creating new ones to avoid duplicates.

Pagination

Many list operations support pagination. Check responses for next_cursor or page_token and continue fetching until exhausted.

Error Handling

Check tool responses for errors before proceeding If a tool fails, verify the connection is still ACTIVE Re-authenticate via RUBE_MANAGE_CONNECTIONS if connection expired

Batch Operations

For bulk operations, use RUBE_REMOTE_WORKBENCH with run_composio_tool() in a loop with Threa PoolExecutor for parallel execution.

Known Pitfalls

Always search tools first: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via RUBE_SEARCH_TOOLS. Check connection status: Ensure the Launc Darkly connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. Respect rate limits: If you receive rate limit errors, reduce request frequency and implement backoff. Validate schemas: Always pass strictly schema-compliant arguments. Use RUBE_GET_TOOL_SCHEMAS to load full input schemas when schem Ref is returned instead of input_schema.

Quick Reference