For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
      • Developer tools
        • LaunchDarkly CLI
        • LaunchDarkly MCP server
          • LaunchDarkly hosted MCP server
          • LaunchDarkly local MCP server
        • LaunchDarkly developer toolbar
        • LaunchDarkly agent skills
        • Vega
        • IDE connectors and agents
      • Setting up an SDK
      • Joining an account
      • Using feature management
      • Getting started in different roles
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Configure the MCP server
  • Quick configuration
  • Manual configuration
  • Migrate to the hosted server
Get startedGet startedDeveloper toolsLaunchDarkly MCP server

LaunchDarkly hosted MCP server

Was this page helpful?
Previous

LaunchDarkly local MCP server

Next
Built with
The hosted MCP server is not available in LaunchDarkly's European Union (EU) instance
Instead, consider using the local MCP server. To learn more, read LaunchDarkly in the European Union (EU).

Overview

This topic describes how to connect your AI client to the LaunchDarkly hosted Model Context Protocol (MCP) server. To use the hosted MCP server, you must have an AI client that supports MCP, such as Cursor, Claude Code, VS Code with Copilot, or Windsurf.

Configure the MCP server

The hosted MCP server at https://mcp.launchdarkly.com/mcp/launchdarkly connects your AI client to LaunchDarkly using OAuth and supports feature flag management, AgentControl configs, and observability.

You have two options for configuring it:

  • Quick configuration
  • Manual configuration

Quick configuration

To configure your AI client, open the install page and click the AI client you want to install it for. The AI client opens and prompts you to authorize and connect to the hosted MCP server.

Manual configuration

You can also manually configure the MCP server in your AI client. Here, we show examples for Cursor and Claude Code.

Cursor

To manually configure the MCP server in Cursor:

  1. Create or update .cursor/mcp.json in your project root:

    Cursor
    1{
    2 "mcpServers": {
    3 "launchdarkly": {
    4 "url": "https://mcp.launchdarkly.com/mcp/launchdarkly",
    5 "headers": {}
    6 }
    7 }
    8}
  2. In Cursor, navigate to Settings > Cursor Settings > Tools & Integrations > MCP Tools.

  3. Toggle on the LaunchDarkly server.

  4. Click Connect to authorize with your LaunchDarkly account.

Claude Code

To manually configure the MCP server in Claude Code, add the server to your Claude Code MCP configuration:

Claude Code
1{
2 "mcpServers": {
3 "launchdarkly": {
4 "type": "http",
5 "url": "https://mcp.launchdarkly.com/mcp/launchdarkly"
6 }
7 }
8}

GitHub Copilot

To manually configure the MCP server with GitHub Copilot, add the server to the MCP configuration for a target GitHub repo:

  1. Navigate to a target repository on GitHub.

  2. Select Settings -> Code and automation -> Copilot -> Coding agent.

  3. In the MCP configuration section, add the following .json configuration:

    GitHub Copilot
    1{
    2 "mcpServers": {
    3 "launchdarkly": {
    4 "url": "https://mcp.launchdarkly.com/mcp/launchdarkly",
    5 "headers": {}
    6 }
    7 }
    8}
  4. Click Save.

Migrate to the hosted server

If you use the local npx-based server, you can migrate to the hosted server. Here’s how:

  1. Replace your old server configuration. Your old configuration looks like this:

    Old configuration to remove
    1{
    2 "mcpServers": {
    3 "LaunchDarkly": {
    4 "command": "npx",
    5 "args": [
    6 "-y", "--package", "@launchdarkly/mcp-server",
    7 "--", "mcp", "start",
    8 "--api-key", "api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    9 ]
    10 }
    11 }
    12}

    and should be replaced with this:

    New configuration to add
    1{
    2 "mcpServers": {
    3 "launchdarkly": {
    4 "type": "http",
    5 "url": "https://mcp.launchdarkly.com/mcp/launchdarkly"
    6 }
    7 }
    8}
  2. Remove any environment variables for the local server, such as LD_ACCESS_TOKEN. Instead, OAuth now handles authentication.

  3. Close and reopen your AI client.

  4. (Cursor only) If you are using Cursor, authorize your LaunchDarkly account:

    • Navigate to Settings > Cursor Settings > Tools & Integrations > MCP Tools.
    • Toggle on the LaunchDarkly server.
    • Click connect.

To learn how to use the MCP server in your AI client, read Use the MCP server.