For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/feature_flags/feature_flag_mcp_server.md. A documentation index is available at /llms.txt.

Feature Flags MCP Server

This product is not supported for your selected Datadog site. ().

Overview

The Datadog MCP Server uses the Model Context Protocol (MCP) to provide AI agents with access to Feature Flags management capabilities. These capabilities include flag creation, configuration, and React/JavaScript integration guidance.

Setup

See the Datadog MCP Server documentation to enable the feature-flags toolset and view the available Feature Flags tools, permissions, and example prompts.

Use cases

The MCP Server includes tools to help you manage feature flags in your codebase. The following use cases provide sample prompts for using the tools.

The code implementation tools, such as check_datadog_flag_implementation, target React applications. Other tools, such as list_datadog_feature_flags and update_datadog_feature_flag_environment, are framework-agnostic.

Create feature flags

Use the create_datadog_feature_flag tool to create feature flags. You do not need to specify the tool name in the prompt. Including it can provide more consistent results. The MCP Server has access to Datadog’s documentation and uses it to implement the flag in your codebase.

If you do not yet have feature flags implemented, mention in the prompt that you want to implement Datadog feature flags.

Example prompts:

  • Use the create_datadog_feature_flag tool to create a flag to control the title on the main page.
  • Show a confirmation modal when <SOME_EVENT> happens. Use a Datadog feature flag to control whether the confirmation modal is shown.

Check feature flag implementation

Use the check_datadog_flag_implementation tool to check if a feature flag is implemented correctly.

The tool checks whether the flag uses the correct value type, subject attributes, and default value. The default value should match the default in production environments.

Example prompts:

  • Check if the show-confirmation-modal flag is implemented correctly.
  • Check if all feature flags in /some/directory are implemented correctly.

Note: This may not find all issues. Checking flags individually is more reliable.

This tool can also be used to add feature flags created in the UI to your codebase. For example:

  • Use the show-confirmation-modal flag to control whether the confirmation modal is shown when <SOME_EVENT> happens.

List feature flags

Use the list_datadog_feature_flags tool to list all feature flags. For example:

  • List all feature flags.

List environments

Use the list_datadog_feature_flag_environments tool to list all environments. For example:

  • List the flagging environments.

Update feature flag environments

Use the update_datadog_feature_flag_environment tool to update a feature flag environment. This tool controls default variants and can enable or disable the flag. It cannot modify flags in production environments.

Example prompts:

  • Serve true for show-confirmation-modal in development.
  • Disable show-confirmation-modal in staging.

Further reading