mcp-configure

Name: mcp-configure
Author: launchdarkly

20stars6forks

How to install mcp-configure?

launchdarkly/ai-tooling/mcp-configure

$npx -y skills add launchdarkly/ai-tooling --skill mcp-configure

Installs into the current project.

Summary

Configure the LaunchDarkly hosted MCP server during onboarding. Use when the parent LaunchDarkly onboarding skill reaches Step 4 (MCP). Supports Cursor, Claude Code, Windsurf, GitHub Copilot, and other MCP-compatible agents. OAuth authentication; no API keys for the hosted server

Files · 1

View on GitHub

SKILL.md

1	# LaunchDarkly MCP Server Configuration (onboarding)
2
3	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.
4
5	This skill is nested under [LaunchDarkly onboarding](../SKILL.md); the parent skill's Step 4 hands off here. Hosted MCP is the default and the only supported option for this onboarding flow.
6
7	## Prerequisites
8
9	- A LaunchDarkly account (sign up at the resolved signup URL — see [Source Attribution](../SKILL.md#source-attribution) in the parent skill; default: `https://app.launchdarkly.com/signup?source=agent`)
10	- An MCP-compatible coding agent
11
12	## Hosted MCP Server
13
14	LaunchDarkly provides a unified hosted MCP server that handles feature management, AgentControl, and other LaunchDarkly capabilities.
15
16	\| Server \| URL \| Purpose \|
17	\| ----------- \| ------------------------------------------------ \| -------------------------------------------- \|
18	\| LaunchDarkly \| `https://mcp.launchdarkly.com/mcp/launchdarkly` \| Feature flags, AgentControl, and more \|
19
20	## Workflow
21
22	### Step 1: Detect the Agent
23
24	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.
25
26	### Step 2: Try Quick Install
27
28	The fastest path is the quick install link. Present it to the user:
29
30	LaunchDarkly MCP: [https://mcp.launchdarkly.com/mcp/launchdarkly/install](https://mcp.launchdarkly.com/mcp/launchdarkly/install)
31
32	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:
33
34	- 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.
35	- The browser may start the OAuth flow, but you'll likely need to confirm or approve the server in the editor itself.
36	- 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).
37
38	If the quick install link doesn't work (agent doesn't support it, or user prefers manual setup), proceed to Step 3.
39
40	### Step 3: Manual Configuration
41
42	Locate the MCP config file for the detected agent and add the hosted server entry. See [MCP Config Templates](references/mcp-config-templates.md) for the exact JSON per agent.
43
44	\| Agent \| Config file location \|
45	\| -------------- \| ---------------------------------------------------------- \|
46	\| Cursor \| `.cursor/mcp.json` (project) or global Cursor settings \|
47	\| Claude Code \| `.mcp.json` (project) or `~/.claude.json` (global) \|
48	\| GitHub Copilot \| Repo Settings on GitHub.com → Copilot → Cloud agent → MCP (see [MCP UI links](references/mcp-ui-links.md)) \|
49	\| Windsurf \| Agent-specific MCP config \|
50
51	The unified server handles both feature management and AgentControl, so only one server entry is needed.
52
53	### Step 4: Agent-Specific Authorization
54
55	After writing the config, some agents need extra steps. Do not send users through long manual menu paths only—use [MCP UI links](references/mcp-ui-links.md) (HTTPS docs + `command:` shortcuts for VS Code / Cursor).
56
57	Cursor:
58
59	1. Open MCP in Cursor using the [Cursor MCP doc link and in-app shortcuts](references/mcp-ui-links.md#clients) (e.g. Settings search via `command:` link when clickable).
60	2. Toggle on LaunchDarkly (or the name from your config).
61	3. Click Connect to authorize with the LaunchDarkly account.
62
63	VS Code (when applicable):
64
65	- Use [VS Code MCP doc + `mcp.json` / Settings links](references/mcp-ui-links.md#clients); trust or start the server if prompted.
66
67	Claude Code:
68
69	- Authorization happens automatically on first MCP tool call via OAuth prompt. File-based setup: [Claude Code MCP doc](https://docs.claude.com/en/docs/claude-code/mcp).
70
71	GitHub Copilot:
72
73	- Click Save after adding the MCP confi

People who liked this also viewed

6 picks

Type

mcp-configure

20stars6forks

View on GitHub

How to install mcp-configure?

launchdarkly/ai-tooling/mcp-configure

$npx -y skills add launchdarkly/ai-tooling --skill mcp-configure

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# LaunchDarkly MCP Server Configuration (onboarding)
2
3	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.
4
5	This skill is nested under [LaunchDarkly onboarding](../SKILL.md); the parent skill's Step 4 hands off here. Hosted MCP is the default and the only supported option for this onboarding flow.
6
7	## Prerequisites
8
9	- A LaunchDarkly account (sign up at the resolved signup URL — see [Source Attribution](../SKILL.md#source-attribution) in the parent skill; default: `https://app.launchdarkly.com/signup?source=agent`)
10	- An MCP-compatible coding agent
11
12	## Hosted MCP Server
13
14	LaunchDarkly provides a unified hosted MCP server that handles feature management, AgentControl, and other LaunchDarkly capabilities.
15
16	\| Server \| URL \| Purpose \|
17	\| ----------- \| ------------------------------------------------ \| -------------------------------------------- \|
18	\| LaunchDarkly \| `https://mcp.launchdarkly.com/mcp/launchdarkly` \| Feature flags, AgentControl, and more \|
19
20	## Workflow
21
22	### Step 1: Detect the Agent
23
24	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.
25
26	### Step 2: Try Quick Install
27
28	The fastest path is the quick install link. Present it to the user:
29
30	LaunchDarkly MCP: [https://mcp.launchdarkly.com/mcp/launchdarkly/install](https://mcp.launchdarkly.com/mcp/launchdarkly/install)
31
32	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:
33
34	- 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.
35	- The browser may start the OAuth flow, but you'll likely need to confirm or approve the server in the editor itself.
36	- 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).
37
38	If the quick install link doesn't work (agent doesn't support it, or user prefers manual setup), proceed to Step 3.
39
40	### Step 3: Manual Configuration
41
42	Locate the MCP config file for the detected agent and add the hosted server entry. See [MCP Config Templates](references/mcp-config-templates.md) for the exact JSON per agent.
43
44	\| Agent \| Config file location \|
45	\| -------------- \| ---------------------------------------------------------- \|
46	\| Cursor \| `.cursor/mcp.json` (project) or global Cursor settings \|
47	\| Claude Code \| `.mcp.json` (project) or `~/.claude.json` (global) \|
48	\| GitHub Copilot \| Repo Settings on GitHub.com → Copilot → Cloud agent → MCP (see [MCP UI links](references/mcp-ui-links.md)) \|
49	\| Windsurf \| Agent-specific MCP config \|
50
51	The unified server handles both feature management and AgentControl, so only one server entry is needed.
52
53	### Step 4: Agent-Specific Authorization
54
55	After writing the config, some agents need extra steps. Do not send users through long manual menu paths only—use [MCP UI links](references/mcp-ui-links.md) (HTTPS docs + `command:` shortcuts for VS Code / Cursor).
56
57	Cursor:
58
59	1. Open MCP in Cursor using the [Cursor MCP doc link and in-app shortcuts](references/mcp-ui-links.md#clients) (e.g. Settings search via `command:` link when clickable).
60	2. Toggle on LaunchDarkly (or the name from your config).
61	3. Click Connect to authorize with the LaunchDarkly account.
62
63	VS Code (when applicable):
64
65	- Use [VS Code MCP doc + `mcp.json` / Settings links](references/mcp-ui-links.md#clients); trust or start the server if prompted.
66
67	Claude Code:
68
69	- Authorization happens automatically on first MCP tool call via OAuth prompt. File-based setup: [Claude Code MCP doc](https://docs.claude.com/en/docs/claude-code/mcp).
70
71	GitHub Copilot:
72
73	- Click Save after adding the MCP confi

People who liked this also viewed

6 picks

Type