Launchdarkly MCP server

Read from the package source without running it. The installed server may list more.

• add_member_to_teams

  Add a single member to one or more teams. The member will be granted access to all specified teams.

• apply_approval_requestwrite action

  Execute an approval request that has been approved. This operation finalizes the approval workflow for any approval request type.

• copy_feature_flag_between_environments

  Copy feature flag configuration from a source environment to a target environment. This Enterprise-only operation supports selective copying of flag changes and optimistic locking via version matching.

• create_approval_requestwrite action

  Create an approval request for changes to a feature flag, AI Config, or segment. The request includes semantic patch instructions that will be applied upon approval.

• create_data_export_destinationwrite action

  Create a new Data Export destination to stream LaunchDarkly events to external platforms. Configuration requirements vary by destination type (e.g., Azure Event Hubs, Google Pub/Sub, Kinesis, mParticle, Segment, Snowflake, Databricks, BigQuery, or Redshift).

• create_environmentwrite action

  Create a new environment within a project. Specify the environment name, unique key, UI color, and optional settings like caching TTL, secure mode, and change approval requirements. Note: approval settings cannot be configured during creation and must be updated separately.

• create_extinction_eventwrite action

  Create a new extinction event for a specific branch in a repository. Extinction events track code reference removals or deprecations.

• create_feature_flagwrite action

  Create a feature flag in a project with customizable variations, targeting defaults, and optional migration settings. Supports cloning existing flags and configuring SDK availability.

• create_flag_triggerwrite action

  Create a new trigger for a feature flag that automatically performs an action (such as turning the flag on or off) when activated by an integrated system.

• create_metricwrite action
• create_projectwrite action

  Create a new project with a unique key and name. Configure SDK availability, naming conventions, and initial environments for the project.

• create_relay_proxy_configwrite action

  Create a new Relay Proxy configuration that controls which environments and projects the Relay Proxy should include or exclude.

• create_repositorywrite action

  Create a new code repository for tracking feature flag references. Optionally provide URLs for accessing the repository and constructing links to specific commits and code hunks.

• delete_applicationwrite action

  Permanently delete an application by its unique key. This action cannot be undone and will remove all associated data.

• delete_application_versionwrite action

  Permanently delete a specific version of an application. This operation removes the version and all associated data.

• delete_approval_requestwrite action

  Permanently delete an approval request by its ID. This action cannot be undone.

• delete_audit_log_subscriptionwrite action

  Remove an audit log subscription from an integration. This permanently deletes the subscription and stops audit log collection for the specified integration.

• delete_brancheswrite action

  Asynchronously delete multiple branches from a repository. Returns a task that processes the branch deletions in the background.

• delete_destinationwrite action

  Permanently delete a Data Export destination from a specific project and environment. This action cannot be undone.

• delete_environmentwrite action

  Permanently delete an environment from a project by its key. This action cannot be undone.

• delete_feature_flagwrite action

  Permanently delete a feature flag across all environments. This operation cannot be undone, so only use it for flags your application no longer references in code.

• delete_memberwrite action

  Remove an account member by their ID. This operation will fail if SCIM provisioning is enabled for the account.

• delete_metricwrite action

  Permanently delete a metric from a project by its key. This operation removes the metric and all associated data.

• delete_oauth_clientwrite action

  Permanently delete an OAuth 2.0 client application by its unique identifier. This action cannot be undone and will invalidate all tokens issued to this client.

• delete_projectwrite action

  Permanently delete a project and all its associated environments and feature flags. This operation cannot be undone and will fail if the project is the last one in the account.

• delete_relay_auto_configwrite action

  Delete a Relay Proxy auto-configuration by its unique identifier. This operation permanently removes the specified relay auto config from your account.

• delete_release_for_flagwrite action

  Removes a release associated with a feature flag. This operation permanently deletes the release record from the specified flag within a project.

• delete_repositorywrite action

  Permanently delete a repository and all associated code references. This action cannot be undone.

• delete_trigger_for_flagwrite action

  Delete a specific flag trigger by its ID. This removes the trigger configuration that automates flag state changes based on defined conditions.

• generate_warehouse_destination_key_pair

  Generate a public-private key pair for authenticating Data Export operations to a Snowflake warehouse destination. This enables secure credential-based access without storing passwords.

• get_application

  Retrieve a LaunchDarkly application by its unique application key. Optionally expand the response to include evaluated flags and other application details.

• get_approval_request

  Retrieve a specific approval request by its ID. Optionally expand the response to include related resources such as environments, flags, projects, or resource details.

• get_audit_log_entry

  Retrieve a detailed audit log entry with full change history. Returns comprehensive metadata including the previous and current versions of the modified entity, plus the JSON patch or semantic patch that was applied.

• get_audit_log_subscription

  Retrieve a specific audit log subscription by its ID within a given integration. Use this to fetch details about an existing subscription configuration.

• get_branch

  Retrieve detailed information about a specific branch within a repository, optionally filtered to a particular project.

• get_caller_identity

  Retrieve information about the identity used to authenticate the current API request, including details about the session cookie, API token, SDK keys, or other credentials.

• get_code_references_statistics

  Retrieve code reference statistics for flags in a project, showing the number of references to flag keys across repositories in the default branch. Optionally filter results to a single flag using the flagKey query parameter.

• get_context_attribute_values

  Retrieve all values associated with a specific context attribute within a project environment. Use this to discover what values have been recorded or are available for a given attribute name.

• get_destination

  Retrieve a single Data Export destination by its ID within a specific project and environment.

• get_environment

  Retrieve a specific environment within a project. Returns environment configuration including approval settings when the approvals feature is enabled.

• get_feature_flag

  Retrieve a single feature flag by its key, with configurations for all environments by default. Use the `env` parameter to filter results to specific environments for faster responses and smaller payloads.

• get_feature_flag_status

  Retrieve the current status of a specific feature flag within a given project and environment. This includes whether the flag is enabled or disabled and any associated targeting rules.

• get_feature_flag_status_across_environments

  Retrieve the current status and configuration of a feature flag across all environments or a specific environment. Use this to check whether a flag is enabled, its targeting rules, and rollout percentages in your deployment pipeline.

• get_member

  Retrieve a single account member by ID. Use the reserved value `me` to get the caller's own member information. Optionally expand the response to include custom role details and role attributes.

• get_metric

  Retrieve detailed information about a specific metric in a LaunchDarkly project. Optionally expand the response to include related experiments and metric groups.

• get_oauth_client_by_id

  Retrieve a registered OAuth 2.0 client by its unique client ID. Use this to fetch detailed configuration and metadata for a specific OAuth client application.

• get_project

  Retrieve a single project by its key. Optionally expand the response to include related resources such as environments.

• get_relay_proxy_config

  Retrieve a single Relay Proxy auto configuration by its unique identifier. Use this to fetch detailed settings for a specific relay proxy configuration.

• get_release_by_flag_key

  Retrieve the currently active release associated with a specific feature flag. Returns release metadata if an active release exists for the flag.

• get_repository

  Retrieve a single repository by its name. Use this to fetch detailed information about a specific code repository tracked in the system.

• get_trigger_workflow_by_id

  Retrieve a specific flag trigger by its ID within a feature flag, project, and environment context. Use this to fetch detailed configuration and status of an individual trigger workflow.

• invite_members

  Invite one or more new members to join an account via email. Each member receives an invitation and must have a valid email address with either a base role (reader, writer, admin, owner/admin, no_access) or a custom role key. Up to 50 members can be invited per request; the entire request fails if any member's data is invalid or conflicts with existing members.

• list_application_versions

  Retrieve all versions for a specific application identified by its application key. Returns a list of version records associated with the application in the account.

• list_applications

  Retrieve a list of all applications. Optionally expand the response to include additional details such as flags evaluated by each application.

• list_approval_requests

  Retrieve all approval requests with support for filtering by assignee, requestor, resource, status, and review status. Optionally expand the response to include related flag, project, and environment details.

• list_audit_log_entries

  Retrieve audit log entries with optional filtering by date ranges, resource specifiers, or full-text search. Use resource specifier syntax to target specific resources or collections.

• list_audit_subscriptions_by_integration

  Retrieve all audit log subscriptions associated with a specific integration. Use this to view which audit events are being monitored for a given integration.

• list_branches

  Retrieve a list of all branches in the specified repository. Use this to discover available branches for code references and analysis.

• list_code_reference_statistics

  Retrieve code reference statistics and repository links for all projects that have code references configured.

• list_context_attribute_names

  Retrieve all available context attribute names for a specific environment within a project. This returns the list of attributes that can be used to define user context in feature flag evaluations.

• list_context_kinds_by_project

  Retrieve all context kinds configured for a specific project. Context kinds define the types of contextual information that can be associated with feature flags and experiments in the project.

• list_destinations

  Retrieve all Data Export destinations configured across your projects and environments. This provides a comprehensive view of where your data is being exported.

• list_environments_by_project

  Retrieve a paginated list of environments for a specified project, with support for filtering by name/key and tags, and sorting by creation date, criticality, or name.

• list_expiring_context_targets

  Retrieve a list of context targets scheduled for removal from a feature flag. This helps identify and manage temporary targeting rules that are approaching their expiration date.

• list_expiring_user_targets_for_feature_flag

  Retrieve a list of user targets scheduled for removal from a feature flag in a specific environment. Note: This endpoint is deprecated; use list_expiring_context_targets_for_feature_flag instead after upgrading to context-based SDKs.

• list_extinctions

  Retrieve a list of all extinction events, which are created when all code references to a flag are removed. Filter results by repository, branch, project, or commit time window to find specific extinctions.

• list_feature_flag_statuses

  Retrieve the status of all feature flags in a specific project and environment, including their current state (new, active, inactive, or launched) and last request timestamp.

• list_feature_flags

  Retrieve all feature flags in a project with optional filtering by environment, tags, and other criteria. Supports pagination, sorting, and field expansion to optimize response payload and performance.

• list_flag_triggers

  Retrieve all triggers configured for a feature flag in a specific environment. Triggers define automated workflows that respond to flag changes.

• list_members

  Retrieve a paginated list of account members with support for filtering by query, role, ID, email, team membership, and activity status. Optionally expand the response to include custom roles and role attributes.

• list_metrics

  Retrieve all metrics for a specified project with support for filtering by various criteria (data sources, event types, tags, usage context) and optional expansion of related experiment counts.

• list_oauth_clients

  Retrieve all OAuth 2.0 clients registered with your account. Use this to view and manage your application integrations.

• list_projects

  Retrieve a paginated list of projects with support for filtering by name, tags, or keys, and sorting by name or creation date. Results are limited to 20 projects per page by default; use pagination links to navigate through additional pages.

• list_relay_proxy_configs

  Retrieve all Relay Proxy configurations currently configured in your account. Use this to view existing proxy setups and their settings.

• list_repositories

  Retrieve a list of connected repositories with optional branch metadata and code references. Filter results by project key to scope code references to a specific LaunchDarkly project.

• reset_environment_sdk_key

  Reset an environment's SDK key and optionally specify when the old key should expire. During the expiry grace period, both the old and new SDK keys remain valid, allowing for seamless client migration.

• reset_relay_auto_config

  Generate a new secret key for a Relay Proxy configuration, optionally setting an expiration time for the previous key before it becomes invalid.

• schedule_user_target_removal_on_flag

  Schedule, update, or remove a removal date for a user from a feature flag's individual targeting. Use semantic patch instructions to manage when LaunchDarkly will stop serving a specific variation to targeted users.

• search_audit_log_entries

  Search audit log entries by full-text query and resource specifiers. Filter results by date ranges and resource types using query parameters and request body constraints.

• search_context_instances

  Search for context instances within a specific project and environment using filters, sorting, and pagination. Supports advanced filtering syntax for querying context data across your application.

• submit_approval_request_reviewwrite action

  Submit a review decision on an approval request by approving, declining, or adding a comment to the proposed changes.

• update_applicationwrite action

  Update an application's description and kind fields using JSON Patch format. Specify changes as an array of patch operations following RFC 6902 standard.

• update_application_versionwrite action

  Update an application version using JSON Patch operations. Currently supports updating the `supported` field to enable or disable the version.

• update_approval_requestwrite action

  Update an approval request using semantic patch instructions. Supports adding reviewers or updating the request description through a structured instruction format.

• update_audit_log_subscriptionwrite action

  Update an audit log subscription configuration using JSON Patch operations. Specify the changes you want to apply to the subscription settings.

• update_context_kindwrite action

  Create or update a context kind within a project. If the context kind exists, only the provided fields will be updated; otherwise, a new context kind will be created.

• update_destinationwrite action

  Update a Data Export destination using JSON patch or JSON merge patch operations. Specify the changes you want to apply to the destination configuration.

• update_environmentwrite action

  Update an environment's configuration using JSON Patch operations. Supports modifying fields including approval settings, comments requirements, and array-based properties.

• update_expiring_context_targetswrite action

  Schedule, update, or remove the date when a context will be automatically removed from individual targeting on a feature flag. Use semantic patch instructions to add expiration dates, modify existing ones, or cancel scheduled removals.

• update_feature_flagwrite action

  Perform a partial update to a feature flag using semantic patch, JSON patch, or JSON merge patch. Supports targeting rules, variations, prerequisites, flag settings, and lifecycle management across environments.

• update_flag_triggerwrite action

  Update a flag trigger's configuration using semantic patch instructions. Supports actions like enabling/disabling the trigger, replacing trigger actions, or cycling the trigger URL.

• update_memberwrite action

  Update an account member's role or custom roles using JSON Patch format. Changes are applied to the member object, though IdP-managed accounts may be overridden by the Identity Provider shortly after.

• update_members_bulkwrite action

  Perform bulk updates to member roles and custom roles using semantic patch instructions. Supports targeted updates to specific members or filtered bulk updates across all members (Enterprise feature).

• update_metricwrite action

  Update a metric using JSON Patch operations. Specify the changes you want to make to the metric's properties such as name, description, or other attributes.

• update_oauth_clientwrite action

  Update an OAuth 2.0 client's configuration using JSON Patch operations. Only the client name, description, and redirect URI can be modified.

• update_projectwrite action

  Update a project using JSON Patch operations. Supports modifying project fields including adding, removing, or replacing values. Array fields like tags are automatically deduplicated and sorted alphabetically.

• update_relay_auto_configwrite action

  Update a Relay Proxy configuration using JSON patch or JSON merge patch operations. Changes are applied incrementally to the specified configuration.

• update_release_phase_status_by_flag_keywrite action

  Update the completion status of a release phase for a flag in a legacy release pipeline. Use JSON patch format to mark specific phases as complete or incomplete by their array index.

• update_repositorywrite action

  Update a repository's settings using JSON patch or JSON merge patch operations. Changes are applied according to RFC 6902 or RFC 7386 standards.

• upsert_branchwrite action

  Create a new branch or update an existing branch in a repository. Use this to sync branch metadata including the current HEAD commit and last sync timestamp.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

100

the typical server has 7

Tools that change things

47%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Downloads a week

160

more than 72% of 12,191 servers with a package

Launchdarkly: common questions

Is Launchdarkly MCP server safe?

Mostly: it is graded B (80/100). Read the Launchdarkly safety report

How do I install Launchdarkly?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Launchdarkly need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Launchdarkly maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.4.

How does Launchdarkly compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 100 (the typical server has 7); tools that change things 47% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.