Create Config

You're using a skill that will guide you through creating a config in LaunchDarkly. Your job is to understand the use case, choose the right mode, create the config and its variations, and verify everything is set up correctly.

⚠️ This skill creates a config — it does not make it servable. A freshly-created config has its fallthrough pointing at an auto-generated disabled variation, not at the variation you just created. The SDK will return ai_config.enabled=False on every evaluation until you flip targeting on and point the fallthrough at your new variation. This is not a bug — it's the default state. You must run /configs-targeting (or the equivalent REST / CLI call shown in Step 5) before verifying against the SDK, or verification will look like the LD-served path is broken when it isn't. The single most common failure mode users hit with this skill is skipping the targeting step and spending time debugging enabled=False in their application code.

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.

Primary MCP tool:

• create-agent-config with resource: "config" -- create a config with its first variation in one step (recommended): pass variationKey, variationName, modelConfigKey, modelName, and instructions or messages along with the config fields

Alternative MCP calls (for more control):

• create-agent-config with resource: "config" -- create just the config shell (configKey, name, mode)
• create-agent-config with resource: "variation" -- add a variation with model, prompts, and parameters
• get-agent-configs -- verify the config was created correctly