All skills
launchdarkly avatar

/onboarding

@45fcc25 official

Scripted onboarding for LaunchDarkly: quiet execution, fixed sequence, SDK install, first flag with a live reveal, MCP offered afterwards. Enforces step completion before advancing and redirects drift. Use when adding LaunchDarkly, setting up or integrating feature flags in a project, SDK integration, or 'onboard me'.

Use this Skill: https://skilld.dev/gh/launchdarkly/agent-skills/onboarding

This session only. Nothing lands on disk.

mcp-configurereferencesmcp-config-templates.md

≈1.2k tokens on demand. Your agent reads this file only when SKILL.md points to it.

MCP Config Templates

Per-agent JSON snippets for configuring the LaunchDarkly hosted MCP server. All configurations use OAuth — no API keys required.

Source: https://launchdarkly.com/docs/home/getting-started/mcp-hosted

Unified Server (Recommended)

Use the unified server URL for new configurations:

Server URL Purpose
LaunchDarkly (unified) https://mcp.launchdarkly.com/mcp/launchdarkly Feature flags and AgentControl

Legacy URLs (deprecated):

  • mcp/fm — deprecated. Migrate to the unified server.
  • mcp/aiconfigs — deprecated. Migrate to the unified server.

See mcp-configure Edge Cases for migration guidance.

Cursor

Config file: .cursor/mcp.json in the project root.

Unified server (recommended)

{
  "mcpServers": {
    "LaunchDarkly": {
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly",
      "headers": {}
    }
  }
}

Legacy feature management only (deprecated)

Deprecated: mcp/fm is deprecated. Use the unified server URL above.

{
  "mcpServers": {
    "LaunchDarkly feature management": {
      "url": "https://mcp.launchdarkly.com/mcp/fm",
      "headers": {}
    }
  }
}

After adding the config: enable the server and complete OAuth in Cursor's MCP UI. Use MCP UI links — Cursor (HTTPS doc + optional command: links); do not rely only on nested Settings menu paths.

Claude Code

Config file: .mcp.json in the project root, or ~/.claude.json for global config.

Unified server (recommended)

{
  "mcpServers": {
    "LaunchDarkly": {
      "type": "http",
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly"
    }
  }
}

Legacy feature management only (deprecated)

Deprecated: mcp/fm is deprecated. Use the unified server URL above.

{
  "mcpServers": {
    "LaunchDarkly feature management": {
      "type": "http",
      "url": "https://mcp.launchdarkly.com/mcp/fm"
    }
  }
}

Authorization happens automatically via OAuth prompt on first MCP tool call.

GitHub Copilot

Configured via the GitHub web UI, not a local config file.

  1. Navigate to the target repository on GitHub
  2. Go to Settings > Code and automation > Copilot > Coding agent
  3. In the MCP configuration section, add:
{
  "mcpServers": {
    "LaunchDarkly": {
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly",
      "headers": {}
    }
  }
}
  1. Click Save

Windsurf

Windsurf uses a similar MCP configuration format. Add to the agent's MCP config:

{
  "mcpServers": {
    "LaunchDarkly": {
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly"
    }
  }
}

Consult Windsurf's documentation for the exact config file location.

Migrating from Deprecated mcp/fm

The mcp/fm URL is deprecated. Replace it with the unified server.

Remove this:

{
  "mcpServers": {
    "LaunchDarkly feature management": {
      "url": "https://mcp.launchdarkly.com/mcp/fm",
      "headers": {}
    }
  }
}

Replace with:

{
  "mcpServers": {
    "LaunchDarkly": {
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly",
      "headers": {}
    }
  }
}

Migrating from Deprecated mcp/aiconfigs

The mcp/aiconfigs URL is deprecated. Replace it with the unified server.

Remove this:

{
  "mcpServers": {
    "LaunchDarkly AI Configs": {
      "url": "https://mcp.launchdarkly.com/mcp/aiconfigs",
      "headers": {}
    }
  }
}

Replace with:

{
  "mcpServers": {
    "LaunchDarkly": {
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly",
      "headers": {}
    }
  }
}

The unified server handles both feature flags and AgentControl. If you also had mcp/fm, migrate it to the unified server — mcp/fm is deprecated and will be removed.

Note: Do not auto-migrate. Always ask the user via a blocking question before making changes (see mcp-configure Edge Cases).

Migrating from the Old Local Server

If the user has the old npx-based server configured with an inline API key, replace it with the hosted unified server:

Remove this:

{
  "mcpServers": {
    "LaunchDarkly": {
      "command": "npx",
      "args": [
        "-y", "--package", "@launchdarkly/mcp-server",
        "--", "mcp", "start",
        "--api-key", "api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
      ]
    }
  }
}

Replace with the unified hosted server:

{
  "mcpServers": {
    "LaunchDarkly": {
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly",
      "headers": {}
    }
  }
}

Also remove any LD_ACCESS_TOKEN or LAUNCHDARKLY_API_KEY environment variables that were used for the local server. The hosted server handles authentication via OAuth.

Source: SKILL.md on GitHub

2 warnings16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides a guided, multi-step onboarding workflow to integrate LaunchDarkly SDKs into a project. It strictly enforces safe defaults such as isolated git branches, avoiding hardcoded secrets by guiding users on environment variable setup with explicit consent, and leverages standard tools or hosted Model Context Protocol (MCP) integrations with no hazardous behaviors identified.

  • Socket16d

    1 alert: gptAnomaly

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Scan incomplete

Signed by skilld at 45fcc25. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated last month
metadata
{
  "author": "launchdarkly",
  "version": "0.3.0"
}
Other metadata
compatibility
Requires an MCP-capable coding agent and `npx` on PATH for optional skill installs. SDK keys, client-side IDs, and mobile keys are only needed when the SDK key step runs.
  • MCP
  • TypeScript
  • launchdarkly
  • feature-flags
  • sdk
  • onboarding
  • integration
  • javascript

README badge

README badge for launchdarkly/agent-skills/onboarding

Orchestrates LaunchDarkly SDK setup in an existing codebase: creates a resumable onboarding log, explores the repo to detect the language and framework, installs companion flag-management skills, configures the LaunchDarkly MCP server, installs and initializes the SDK, and scaffolds a first feature flag. Designed for projects adding LaunchDarkly from scratch or integrating feature flags into an existing codebase.

Generated from the current SKILL.md.

Does this skill require a LaunchDarkly account upfront?
No. Steps 0–3 (log, explore, detect, install skills) run without an account. Account status is confirmed naturally during Step 4 via MCP OAuth, or surfaced at Step 5 if you need to provide SDK keys manually.
What coding agent platforms does this work with?
It requires an MCP-capable coding agent (like Cursor or Claude Code). Task tracking uses your agent's native tool if available (TodoWrite in Cursor, TaskCreate in Claude Code), or falls back to an in-chat checklist.
Do I need SDK keys or API tokens before starting?
No. The skill defers credential collection until the step that actually uses them — MCP uses OAuth (Step 4), and the SDK install collects keys only when wiring environment variables (Step 5).
Can I pause and resume onboarding later?
Yes. Step 0 writes a living onboarding log file (LAUNCHDARKLY_ONBOARDING.md) that tracks progress, so a new session or another agent can pick up where you left off.
What if I do not have the MCP server configured?
The skill falls back to ldcli or REST API for SDK discovery and flag creation, though MCP is preferred. Onboarding remains completable without it.

Generated from the current SKILL.md. These answers refresh after source changes.