Mcp Configure
Paste OAuth-based LaunchDarkly hosted MCP server JSON into Cursor, Claude Code, Copilot, or Windsurf so your agent can manage feature flags without storing API keys.
Overview
mcp-configure is an agent skill for the Build phase that supplies per-client JSON templates to connect Cursor, Claude Code, Copilot, or Windsurf to LaunchDarkly’s OAuth-hosted MCP server.
Install
npx skills add https://github.com/launchdarkly/agent-skills --skill mcp-configureWhat is this skill?
- Copy-paste JSON for Cursor (.cursor/mcp.json), Claude Code (.mcp.json / ~/.claude.json), GitHub Copilot repo MCP UI, and
- Hosted endpoint https://mcp.launchdarkly.com/mcp/launchdarkly with OAuth—no API keys in config
- Cursor: enable server and complete OAuth in MCP UI; references MCP UI link patterns instead of brittle menu paths
- Claude Code: http transport type; OAuth prompt on first tool call
- GitHub Copilot: repository Settings → Coding agent → MCP configuration (web UI, not local file)
- 4 agent clients documented (Cursor, Claude Code, GitHub Copilot, Windsurf)
- OAuth-based config with empty headers object in snippets
Adoption & trust: 1.2k installs on skills.sh; 16 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want your coding agent to read and change LaunchDarkly flags but do not know which config file or GitHub UI field each client expects.
Who is it for?
Indie builders already on LaunchDarkly who are standardizing MCP setup across Cursor, Claude Code, Copilot, or Windsurf in a new repo.
Skip if: Teams that need on-prem MCP, custom auth headers, or flag-design workflows without any MCP client configuration.
When should I use this skill?
You are adding or fixing LaunchDarkly hosted MCP configuration for a supported coding agent.
What do I get? / Deliverables
You have valid MCP entries for your agent client and can complete OAuth so LaunchDarkly tools are callable from the IDE.
- .cursor/mcp.json or .mcp.json entries
- Saved GitHub Copilot MCP configuration block
Recommended Skills
Journey fit
Canonical shelf is Build because the skill only delivers per-client MCP wiring before you use LaunchDarkly tools during implementation. Agent-tooling fits best: it is config templates and OAuth setup steps for MCP clients, not application backend code.
How it compares
Use this for hosted-MCP wiring snippets, not a full LaunchDarkly SDK or feature-flag methodology skill.
Common Questions / FAQ
Who is mcp-configure for?
Solo and small-team builders using AI coding agents who want LaunchDarkly’s hosted MCP connected with OAuth instead of pasting API keys into JSON.
When should I use mcp-configure?
During Build agent-tooling when you add LaunchDarkly to a project: open the snippet for Cursor, Claude Code, Copilot repo settings, or Windsurf, save config, then authorize in that client’s MCP UI.
Is mcp-configure safe to install?
Configs use OAuth to a LaunchDarkly-hosted URL rather than checked-in secrets; review the Security Audits panel on this Prism page and your org’s LaunchDarkly access policies before enabling production projects.
SKILL.md
READMESKILL.md - Mcp Configure
# 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 ## Cursor Config file: `.cursor/mcp.json` in the project root. ```json { "mcpServers": { "LaunchDarkly": { "url": "https://mcp.launchdarkly.com/mcp/launchdarkly", "headers": {} } } } ``` **After adding the config:** enable the server and complete OAuth in Cursor's MCP UI. Use [MCP UI links — Cursor](mcp-ui-links.md#clients) (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. ```json { "mcpServers": { "LaunchDarkly": { "type": "http", "url": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } ``` 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: ```json { "mcpServers": { "LaunchDarkly": { "url": "https://mcp.launchdarkly.com/mcp/launchdarkly", "headers": {} } } } ``` 4. Click **Save** ## Windsurf Windsurf uses a similar MCP configuration format. Add to the agent's MCP config: ```json { "mcpServers": { "LaunchDarkly": { "url": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } ``` Consult Windsurf's documentation for the exact config file location. ## Migrating from Old Configurations ### From the old local npx-based server If the user has the old npx-based server configured, replace it: **Remove this:** ```json { "mcpServers": { "LaunchDarkly": { "command": "npx", "args": [ "-y", "--package", "@launchdarkly/mcp-server", "--", "mcp", "start", "--api-key", "api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" ] } } } ``` **Replace with the hosted config for the relevant agent** (see sections above). 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. ### From deprecated split servers (`mcp/fm` and `mcp/aiconfigs`) Both `mcp/fm` and `mcp/aiconfigs` are deprecated. All functionality is now in the unified server (`mcp/launchdarkly`). If the user has either endpoint configured, **ask before removing** — see the edge case flow in [SKILL.md](../SKILL.md#edge-cases). The user should confirm the migration. **Entries to remove (after user confirms):** ```json { "mcpServers": { "LaunchDarkly Feature Management": { "url": "https://mcp.launchdarkly.com/mcp/fm" }, "LaunchDarkly AgentControl": { "url": "https://mcp.launchdarkly.com/mcp/aiconfigs" } } } ``` **Replace with the single unified server** (see sections above). # Open MCP settings (links instead of menu paths) Use this reference when onboarding tells the user to enable MCP, connect OAuth, or open MCP configuration. **Give clickable links**—do not rely only on "Settings → … → Tools & MCP" prose. ## How to use (agents) 1. Use the row for the detected client (see parent onboarding **Step 2: Detect the Agent**). 2. **Always include the HTTPS documentation link** for that client—it opens in the browser and works from any environment. 3. When the user is in **VS Code or Cursor**, also include the **`command:` links** on their own lines so they can click in the editor chat (same scheme VS Code uses for trusted markdown). If a `command:` link is not clickable or does nothing, fall back to the doc link or Command Palette text below. 4. **Path caveat:** LaunchDarkly's Cursor template uses **project** `.cursor/mcp.json`. VS Code's **MCP: Open User/Workspace Confi