Index of every page on this site: llms.txt
All skills
launchdarkly avatar

/mcp-configure

@f0ee110 official
Run it yourself

Configure the LaunchDarkly hosted MCP server during onboarding. Use when the parent LaunchDarkly onboarding skill reaches the MCP offer, after the first flag works. Supports Cursor, Claude Code, Windsurf, GitHub Copilot, and other MCP-compatible agents. OAuth authentication; no API keys for the hosted server.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/mcp-configure

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈81 tokens for metadata: the name and description. ≈2.7k when used: this file. ≈2.1k more on demand in 2 files.

Description uses 4.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈326 characters, or 4.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

LaunchDarkly MCP Server Configuration (onboarding)

Configures the LaunchDarkly hosted MCP server so flag management skills and onboarding can use MCP tools. Uses OAuth for authentication — no API keys needed for the hosted server.

This skill is nested under LaunchDarkly onboarding; the parent skill hands off here once the first flag works.

Prerequisites

  • A LaunchDarkly account (when directing users to sign up, use the resolved signup URL from the parent skill's Source Attribution; default: https://app.launchdarkly.com/signup?source=agent)
  • An MCP-compatible coding agent

Hosted MCP Servers

LaunchDarkly provides a unified hosted MCP server for all functionality:

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

The legacy mcp/fm and mcp/aiconfigs URLs are deprecated — migrate any existing usage to the unified server (see Edge Cases).

For onboarding, the unified server is all that's needed.

Workflow

Step 1: Detect the Agent

If the parent onboarding skill already identified the agent, use that context. Otherwise infer from agent-specific directories, config files, and the tools available to you at runtime. Do not ask the user — pick the strongest match.

Step 2: Try Quick Install

The fastest path is the quick install link. Present it to the user:

LaunchDarkly MCP: https://mcp.launchdarkly.com/mcp/launchdarkly/install

Important: tell the user what to expect after clicking the link. The install link may open in the browser, but the authorization or "add server" prompt typically appears back in the coding environment (the editor or host app where the agent runs), not in the browser. Immediately after presenting the link, include guidance like:

  • After clicking the link, watch your coding environment (the editor where this conversation is running) for an approval dialog, an "add MCP server" prompt, or a tools/integrations panel notification.
  • The browser may start the OAuth flow, but you'll likely need to confirm or approve the server in the editor itself.
  • If no prompt appears: check the editor's MCP, integrations, or tools settings area to see if the server was added but needs to be enabled. If it's not there at all, fall back to manual setup (Step 3 below).

If the quick install link doesn't work (agent doesn't support it, or user prefers manual setup), proceed to Step 3.

Step 3: Manual Configuration

Locate the MCP config file for the detected agent and add the hosted server entry. See MCP Config Templates for the exact JSON per agent.

Agent Config file location
Cursor .cursor/mcp.json (project) or global Cursor settings
Claude Code .mcp.json (project) or ~/.claude.json (global)
GitHub Copilot Repo Settings on GitHub.com → Copilot → Cloud agent → MCP (see MCP UI links)
Windsurf Agent-specific MCP config

Add the unified LaunchDarkly server for onboarding. This single server handles feature flags and AgentControl.

Step 4: Agent-Specific Authorization

After writing the config, some agents need extra steps. Do not send users through long manual menu paths only—use MCP UI links (HTTPS docs + command: shortcuts for VS Code / Cursor).

Cursor:

  1. Open MCP in Cursor using the Cursor MCP doc link and in-app shortcuts (e.g. Settings search via command: link when clickable).
  2. Toggle on LaunchDarkly (or the name from your config).
  3. Click Connect to authorize with the LaunchDarkly account.

VS Code (when applicable):

Claude Code:

  • Claude Code loads MCP servers only when a session starts, so a server added mid-session is not available yet. The user quits, resumes the session with claude --continue, then runs /mcp, selects the LaunchDarkly server, and authenticates. File-based setup: Claude Code MCP doc.

GitHub Copilot:

  • Click Save after adding the MCP configuration in repo settings. Use the GitHub Copilot MCP doc for the exact Settings path on github.com.

Step 5: Verify MCP Tools

Cursor does not need a restart after enabling an MCP server. Claude Code does: it loads MCP servers only at session start (see Step 4). Probe for tools immediately after the user confirms they've enabled and authorized the server.

  1. Tell the user to enable and authorize the server. In Cursor: toggle on the LaunchDarkly server in MCP settings and click Connect. In Claude Code: quit, resume with claude --continue, then authenticate the server from /mcp. Do not tell Cursor users to restart yet.

  2. Probe immediately. After the user confirms the server is enabled, call a lightweight MCP tool (e.g. get-flags with the user's project key). Do not ask the user whether MCP is working — just try it.

    • Success (normal response, even an empty flag list): MCP is live. Continue.
    • Auth error (401, 403, "unauthorized", "forbidden", or OAuth-related message): the server was found but authorization failed. Go to step 3a.
    • Tool not found or timeout (tool not recognized, connection refused, no response): the editor hasn't picked up the server yet. Go to step 3b.

3a. Auth failure path. The MCP server is reachable but OAuth is incomplete or expired — restarting the editor won't help.

  • Tell the user: "The MCP server responded but authorization failed. In Cursor: open MCP settings, find the LaunchDarkly server, and click Connect to re-authorize. In Claude Code: run /mcp, select the LaunchDarkly server, and authenticate."
  • Use MCP UI links to give the user a direct shortcut to their agent's MCP settings.
  • Re-probe after the user confirms they re-authorized.
  • If the re-probe succeeds: continue with onboarding.
  • If it fails again: offer the retry one-liner (see step 4 below). Do not suggest a restart for a persistent auth problem.

3b. Server-not-found path. The editor likely hasn't loaded the new MCP config yet.

  • Tell the user: "The MCP tools aren't visible yet. Some editors need a restart to pick up new MCP servers. Restart your editor and say 'continue LaunchDarkly onboarding' when you're back — I'll resume from here."
  • Be specific about how to restart: "Restart Cursor" / "quit Claude Code and resume with claude --continue" / "refresh the Copilot agent" depending on what you detected in Step 1.
  1. On resume after restart: The parent onboarding skill detects live state, so no log file is needed. When the next turn starts:

    • Re-probe for MCP tools silently.
    • If tools are now available: "MCP is connected." Continue with onboarding.
    • If tools still missing: do not block the rest of onboarding — remaining steps must still be completable without MCP. Offer a one-liner to retry later: "You can set up MCP anytime by clicking [quick install link] and restarting."
  2. If the failure looks like a config issue (wrong file path, server not enabled), mention the likely cause so the user can fix it on their own time — but do not block progress.

Edge Cases

  • User already has MCP configured: Verify by checking for existing LD MCP entries in the config. If the unified server (https://mcp.launchdarkly.com/mcp, or the older /mcp/launchdarkly path, which still works) is present and working, skip configuration. If the deprecated mcp/fm or mcp/aiconfigs is present, see below.
  • User has the deprecated mcp/aiconfigs or mcp/fm server: These URLs are deprecated. Do not auto-migrate. Use a blocking question:
{
  "questions": [
    {
      "id": "legacy_migration",
      "prompt": "I found a deprecated LaunchDarkly MCP URL in your config (mcp/fm or mcp/aiconfigs). It should be replaced with the unified LaunchDarkly server (mcp.launchdarkly.com/mcp), which handles both feature flags and AgentControl. Do you want me to migrate?",
      "options": [
        { "id": "yes", "label": "Yes, remove the old server and add the unified one" },
        { "id": "no", "label": "No, leave it as is for now" }
      ]
    }
  ]
}
  • If yes: remove the deprecated entry, ensure the unified https://mcp.launchdarkly.com/mcp server is present (do not duplicate if it, or the older /mcp/launchdarkly path, is already there), and continue.

  • If no: leave the config untouched and continue with onboarding — the deprecated server may still work for now.

  • User has the old npx-based local server: Migrate them to the hosted server. Remove the old npx @launchdarkly/mcp-server entry and any LD_ACCESS_TOKEN env vars. Replace with the hosted server config.

  • Agent not in known list: Provide the generic pattern: the user needs to add an MCP server entry pointing to https://mcp.launchdarkly.com/mcp using whatever format their agent expects.

  • User opts out of MCP during onboarding: Document that choice and continue; do not block SDK work.

What NOT to Do

  • Don't configure a local npx-based server. Always use the hosted server.
  • Don't ask for or store API keys. The hosted server uses OAuth.
  • Don't auto-migrate from the deprecated mcp/aiconfigs — always ask via the blocking question.
  • Don't suggest restart as the first step in Cursor — probe for tools immediately after the user enables the server.
  • Don't suggest restart for auth errors (401/403) — the server was found, so a restart won't help. Guide the user to re-authorize instead.

References

  • MCP UI links — HTTPS + command: links to open MCP settings (Cursor, VS Code, Claude Code, Windsurf, GitHub)
  • MCP Config Templates — hosted OAuth JSON per agent; migration from deprecated configs
  • Official MCP docs — full hosted setup guide

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts11d3 checks · Risk SAFE
  • Gen Agent Trust Hub14d

    The skill is safe. It assists users in configuring a Model Context Protocol (MCP) server for LaunchDarkly, using secure methods like OAuth and providing guidance for various development environments without any malicious behavior.

  • Socket11d

    No alerts

  • Snyk14d

    Risk: LOW · No issues

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

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
compatibility
Requires an MCP-compatible coding agent and a LaunchDarkly account
metadata
{
  "author": "launchdarkly",
  "version": "0.1.1"
}
  • MCP
  • launchdarkly
  • oauth
  • cursor
  • claude
  • github-copilot
  • windsurf
  • feature-flags
  • onboarding

README badge

README badge for launchdarkly/ai-tooling/mcp-configure

Configures the LaunchDarkly hosted MCP server for Cursor, Claude Code, Windsurf, GitHub Copilot, and other MCP-compatible agents during onboarding. Uses OAuth authentication to enable feature flag management and AgentControl tools without API keys.

Generated from the current SKILL.md.

Does this skill work with my coding agent?
Yes, if it's MCP-compatible. Cursor, Claude Code, Windsurf, and GitHub Copilot are explicitly supported. For other agents, you need to add an MCP server entry pointing to https://mcp.launchdarkly.com/mcp/launchdarkly in whatever config format your agent expects.
Do I need an API key to use the hosted MCP server?
No. The hosted server uses OAuth authentication, so no API keys are required.
What if I already have a deprecated MCP server configured?
The skill detects old endpoints (mcp/fm, mcp/aiconfigs, or the npx-based local server) and walks you through migrating to the unified mcp/launchdarkly server. You can choose to update or leave it as-is.
What happens if the quick install link doesn't work?
The skill falls back to manual configuration. You'll edit your agent's MCP config file (e.g. .cursor/mcp.json or .mcp.json) to add the hosted server entry, then authorize in your editor's MCP settings.
Do I need to restart my editor after configuring MCP?
Not always. Some agents (Cursor, Claude Code) enable MCP tools immediately. If tools don't appear, the skill will suggest a restart and resume from where you left off.

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