skilld
All skills
launchdarkly avatar

/mcp-configure

@45fcc25 official
by launchdarklylaunchdarkly/agent-skills25 stars
10

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.

Ask your Agent

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

This session only. Nothing lands on disk.

referencesmcp-ui-links.md

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

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 Configuration commands open VS Code's mcp.json locations (often under .vscode/ or the user profile)—not .cursor/mcp.json. If the user edited .cursor/mcp.json, point them at the Cursor doc link or "open .cursor/mcp.json in the editor" plus Cursor's MCP panel.

Clients

Client Documentation (open in browser) In-app shortcuts (VS Code–compatible hosts)
Cursor Model Context Protocol (MCP) — Cursor Docs Open Settings (filtered search: mcp)
VS Code (GitHub Copilot Chat, built-in MCP, etc.) Add and manage MCP servers in VS Code Open user mcp.json · Open workspace folder mcp.json · Open Settings (filtered search: mcp)
Claude Code Connect Claude Code to tools through MCP Config is file-based (project .mcp.json or user config)—open those files in the editor; no shared command: URI across versions.
Windsurf MCP — Windsurf Docs Use Windsurf's documented MCP / Cascade UI.
GitHub Copilot (cloud agent, repo settings) Extend Copilot coding agent with MCP — GitHub Docs Configuration is on github.com under the repository's Settings (see doc). Optional: MCP and Copilot coding agent (concepts).

Command Palette text (fallback)

If links are not clickable:

  • VS Code / Cursor: Run MCP: Open User Configuration, MCP: Open Workspace Folder Configuration, or MCP: List Servers from the Command Palette (⇧⌘P / Ctrl+Shift+P). Alternatively Preferences: Open Settings (UI) and search mcp.
  • Cursor: See the Cursor MCP doc for the current location of the MCP tools list and OAuth Connect (labels such as Tools & MCP or MCP vary by version).

Command link encoding note

command:workbench.action.openSettings? links pass a JSON array argument (URL-encoded). Example: query mcp → ?%5B%22mcp%22%5D is ["mcp"]. Adjust the search string if the UI does not filter as expected (e.g. try "Tools MCP").

Source: SKILL.md on GitHub

Third-party checks

1 alert4mo4 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    This skill provides configuration guidance for the LaunchDarkly Model Context Protocol (MCP) server. It includes robust security practices for handling API tokens, such as explicit user warnings, blocking decision points, and instructions for using .gitignore to protect local secrets.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: HIGH · 2 issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

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

Capability

compatibility
Requires an MCP-compatible coding agent and a LaunchDarkly account
metadata
{
  "author": "launchdarkly",
  "version": "0.1.0"
}

Topics

  • MCP
  • launchdarkly
  • oauth
  • cursor
  • claude
  • github-copilot
  • windsurf
  • feature-flags
  • onboarding

README badge

README badge for launchdarkly/agent-skills/mcp-configure

What it does

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.

Frequently asked

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.