com.mcparmory/launchdarkly
PYPI · MCPARMORY-LAUNCHDARKLY · 2 COMPONENTS · SCANNED SEP 20
Manage feature flags, segments, projects, environments, and team members
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 36460 tokens (~133/item across 274 items; 274 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 43 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 274 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/launchdarkly MCP server?
com.mcparmory/launchdarkly runs locally as a PyPI package, launched with uvx mcparmory-launchdarkly. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-launchdarkly
claude mcp add com-mcparmory-launchdarkly -- uvx mcparmory-launchdarkly
{
"mcpServers": {
"com-mcparmory-launchdarkly": {
"command": "uvx",
"args": [
"mcparmory-launchdarkly"
]
}
}
} {
"servers": {
"com-mcparmory-launchdarkly": {
"command": "uvx",
"args": [
"mcparmory-launchdarkly"
]
}
}
} codex mcp add com-mcparmory-launchdarkly -- uvx mcparmory-launchdarkly
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-launchdarkly": {
"type": "local",
"command": [
"uvx",
"mcparmory-launchdarkly"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-launchdarkly --command uvx --arg mcparmory-launchdarkly
mcp_servers:
com-mcparmory-launchdarkly:
command: "uvx"
args: ["mcparmory-launchdarkly"] {
"McpServers": {
"com-mcparmory-launchdarkly": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-launchdarkly"
]
}
}
} assistant mcp add com-mcparmory-launchdarkly -t stdio -c uvx -a mcparmory-launchdarkly
{
"mcpServers": {
"com-mcparmory-launchdarkly": {
"command": "uvx",
"args": [
"mcparmory-launchdarkly"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.83 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcparmory-launchdarkly@1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_flag_follower Add Flag Follower ~139
Subscribe a team member to receive updates about a feature flag's changes in a specific project and environment. Members with reader roles can only add themselves as followers.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the flag follower relationship applies. |
| featureFlagKey | string | yes | The unique identifier for the feature flag to follow. |
| memberId | string | yes | The unique identifier of the team member to add as a follower. Members with reader-level permissions can only add themselves, while higher-privileged members can add any team member. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
add_flag_to_release_pipeline Add Flag to Release Pipeline ~133
Adds a flag to a release pipeline, optionally specifying which variation to release across all phases. This initiates the flag's progression through the release pipeline's defined stages.
| Name | Type | Req | Description |
|---|---|---|---|
| flagKey | string | yes | The unique identifier for the flag to be added to the release pipeline. |
| projectKey | string | yes | The unique identifier for the project containing the flag. |
| releasePipelineKey | string | yes | The unique identifier of the release pipeline to attach the flag to. |
| releaseVariationId | string | – | The variation to release across all phases of the pipeline. If not specified, the default variation will be used. |
No output schema declared.
No examples provided.
add_member_to_teams Add Member to Teams ~83
Add a single member to one or more teams. The member will be granted access to all specified teams.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the member to add to teams. |
| teamKeys | array | yes | An array of team keys identifying which teams the member should be added to. Provide one or more team keys as strings in the array. |
No output schema declared.
No examples provided.
add_members_to_team Add Members to Team ~129
Add multiple team members to an existing team by uploading a CSV file containing email addresses. The operation validates all entries before adding any members—a single invalid entry prevents all additions.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Base64-encoded file content for upload. A CSV file containing email addresses in the first column (headers optional). LaunchDarkly ignores additional columns. File must not exceed 25MB and must conta… |
| teamKey | string | yes | The unique identifier for the team. Used to route the request to the correct team. |
No output schema declared.
No examples provided.
add_restricted_models Add Restricted Models ~132
Add one or more AI models to the restricted list for a project. Restricted models cannot be used in AI configurations for that project. Model keys are obtained from the List AI model configs endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| keys | array | yes | An array of AI model keys to add to the restricted list. Each key must be a valid model key returned by the List AI model configs endpoint. Duplicate keys in the array will be deduplicated. |
| projectKey | string | yes | The project key that identifies which project's restricted model list to update. Use the project key from your LaunchDarkly workspace (e.g., 'default'). |
No output schema declared.
No examples provided.
apply_approval_request Apply Approval Request ~62
Execute an approval request that has been approved. This operation finalizes the approval workflow for any approval request type.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the approval request to apply. This is a string value that identifies which approval request should be executed. |
No output schema declared.
No examples provided.
apply_approval_request_for_flag Apply Approval Request for Flag ~128
Apply an approval request that has been approved for a feature flag in a specific environment. This executes the changes specified in the approval request.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the approval request will be applied. |
| featureFlagKey | string | yes | The unique identifier for the feature flag associated with the approval request. |
| id | string | yes | The unique identifier for the approval request to apply. The request must have been previously approved before it can be applied. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
associate_repositories_with_projects Associate Repositories with Projects ~71
Create or update associations between repositories and projects. Use this operation to map one or more repositories to their corresponding projects for engineering insights tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| mappings | array | yes | Array of repository-to-project mappings. Each mapping object should specify which repository associates with which project. Order is preserved and processed sequentially. |
No output schema declared.
No examples provided.
copy_feature_flag_between_environments Copy Feature Flag Between Environments ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currentVersion | integer | – | Optional flag version number. When provided, the copy operation only succeeds if the target environment's current flag version matches this value, enabling optimistic locking to prevent concurrent mo… |
| featureFlagKey | string | yes | The feature flag key that uniquely identifies the flag within the project. |
| includedActions | array | – | Optional list of specific flag changes to copy (e.g., 'updateOn'). Use this to copy only selected changes rather than the entire flag configuration. Cannot be combined with excludedActions; if neithe… |
| projectKey | string | yes | The project key that identifies which project contains the feature flag. |
| sourceKey | string | yes | The environment key of the source environment to copy flag settings from. |
| targetKey | string | yes | The environment key of the target environment to copy flag settings to. |
No output schema declared.
No examples provided.
create_agent_graph Create Agent Graph ~216
Create a new agent graph within a project. The graph can be initialized with a root configuration node and edges, or created as metadata-only if neither is provided.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Currently only 'beta' is supported. |
| edges | array | – | An array of edges defining connections between nodes in the graph. Each edge specifies the relationship between two nodes. Required if rootConfigKey is provided; both must be present together or both… |
| key | string | yes | A unique identifier for the agent graph within the project. Must be distinct from other graphs in the same project. |
| name | string | yes | A human-readable display name for the agent graph. |
| projectKey | string | yes | The unique identifier of the project where the agent graph will be created. |
| rootConfigKey | string | – | The AI Config key that serves as the root node of the graph. Required if edges are provided; omit both this and edges to create a metadata-only graph. |
No output schema declared.
No examples provided.
create_agent_optimization Create Agent Optimization ~351
Create a new agent optimization configuration within a project to define how an AI agent should be evaluated and optimized using specified models, judges, and acceptance criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceStatements | array | – | An optional list of acceptance criteria statements that define successful agent behavior. The agent must satisfy these conditions within the maximum attempts. |
| aiConfigKey | string | yes | The key of the AI configuration that this optimization applies to. |
| groundTruthResponses | array | – | An optional list of expected or reference responses used to measure agent accuracy and performance against ground truth. |
| judgeModel | string | yes | The key of the model to use as the judge for evaluating agent performance against acceptance criteria. |
| judges | array | – | An optional list of judge configurations or identifiers used to evaluate agent responses. Multiple judges can provide consensus evaluation. |
| key | string | yes | A unique key to identify this agent optimization configuration within the project. |
| maxAttempts | integer | yes | The maximum number of attempts the agent should make when trying to meet acceptance criteria. Must be a positive integer. |
| metricKey | string | – | An optional key referencing a specific metric to track and optimize for during the agent optimization process. |
| modelChoices | array | – | An optional list of AI model identifiers to evaluate and compare during optimization. Order may indicate priority or evaluation sequence. |
| projectKey | string | yes | The unique identifier of the project where the agent optimization will be created. |
| userInputOptions | array | – | An optional list of user input options or scenarios that the agent should handle during optimization testing. |
| variableChoices | array | – | An optional list of variable configurations that the agent can choose from or adjust during optimization. Order may indicate priority or evaluation sequence. |
No output schema declared.
No examples provided.
create_ai_config Create AI Config ~389
Create a new AI Config within a project to define AI model behavior, variations, and evaluation criteria. Supports multiple modes (completion, agent, or judge) with customizable instructions, messages, and evaluation metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| defaultVariationKey | string | yes | A unique identifier for the default variation of this AI Config. |
| defaultVariationName | string | yes | The display name of the default variation. |
| description | string | – | Optional description of the AI Config to provide context about its purpose and usage. |
| evaluationMetricKey | string | – | Optional key referencing an evaluation metric to assess the performance of this AI Config. |
| instructions | string | – | Instructions for agent behavior. Only applicable and returned when the mode is set to 'agent'. |
| isInverted | boolean | – | Optional boolean flag indicating whether the evaluation metric is inverted, meaning lower values indicate better performance when set to true. |
| judges | array | – | Optional array of judges attached to this variation for evaluation purposes. When provided, this replaces all existing judge attachments; an empty array removes all judges. |
| key | string | yes | A unique identifier for the AI Config within the project, used for referencing and management. |
| messages | array | – | Optional array of messages that define the conversation context or system prompts for the AI Config. |
| mode | string | – | The operational mode of the AI Config. Choose 'completion' for standard text generation, 'agent' for agentic behavior with instructions, or 'judge' for evaluation purposes. Defaults to 'completion'. |
| modelConfigKey | string | – | Optional reference to a model configuration key that specifies the underlying model settings and parameters. |
| name | string | yes | The display name of the AI Config. |
| projectKey | string | yes | The unique identifier of the project where the AI Config will be created. |
| tags | array | – | Optional array of tags for categorizing and organizing the AI Config. |
No output schema declared.
No examples provided.
create_ai_config_variation Create AI Config Variation ~231
Create a new variation for an AI Config, specifying model configuration, instructions, and optional judges for evaluation.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier of the AI Config for which to create a variation. |
| instructions | string | – | Instructions for the agent behavior. Only applicable and returned for agent-type variations. |
| judges | array | – | List of judge configurations for evaluating this variation. When provided, replaces all existing judges; an empty array removes all judge attachments. |
| key | string | yes | The unique identifier for this variation within the AI Config. |
| messages | array | – | Array of message objects defining the conversation or prompt structure for this variation. Order and format depend on the model type. |
| modelConfigKey | string | – | Optional reference to a model configuration key. If provided, uses a predefined model configuration; otherwise, model details must be specified in the request body. |
| name | string | yes | A human-readable name for this variation to distinguish it from other variations of the same AI Config. |
| projectKey | string | yes | The unique identifier of the project containing the AI Config. |
No output schema declared.
No examples provided.
create_ai_tool Create AI Tool ~172
Create a new AI tool within a project that defines custom functionality for LLM consumption. The tool's parameters are specified via JSON Schema, with optional custom metadata for application-level configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| customParameters | object | – | Optional object containing custom metadata and configuration settings for application-level use. These values are not exposed to the LLM and are used only by your application logic. |
| key | string | yes | The unique identifier for the AI tool within the project. Used to reference this tool in subsequent operations. |
| projectKey | string | yes | The unique identifier of the project where the AI tool will be created. |
| schema | object | yes | A JSON Schema object that defines the tool's input parameters and their constraints. This schema is sent to the LLM to describe what inputs the tool accepts and how to invoke it. |
No output schema declared.
No examples provided.
create_announcement Create Announcement ~243
Create a new announcement to notify users about system events, maintenance, or important updates. The announcement will be displayed to users during the specified time window.
| Name | Type | Req | Description |
|---|---|---|---|
| endTime | string | – | The Unix timestamp in milliseconds when the announcement stops being displayed to users. If omitted, the announcement remains active indefinitely after the start time. |
| isDismissible | boolean | yes | Whether users can dismiss this announcement from their view. Set to true to allow users to close the announcement, or false to make it persistent. |
| message | string | yes | The full announcement message body. Supports markdown formatting for emphasis, links, and structure. Use this to provide detailed information about the announcement. |
| severity | string | yes | The urgency level of the announcement. Use 'info' for general notices, 'warning' for important alerts, or 'critical' for urgent system issues requiring immediate attention. |
| startTime | string | yes | The Unix timestamp in milliseconds when the announcement becomes visible to users. This marks the start of the announcement's active period. |
| title | string | yes | A concise headline for the announcement (e.g., 'System Maintenance Notice'). This is the primary text users see first. |
No output schema declared.
No examples provided.
create_approval_request Create Approval Request ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | A brief summary of the requested changes. This helps reviewers understand the intent of the approval request. |
| instructions | array | yes | An ordered list of semantic patch instructions to apply when the approval is granted. Instructions vary by resource type: use addVariation, removeVariation, updateVariation, or updateDefaultVariation… |
| integrationConfig | object | – | Optional object containing additional fields for third-party approval system integrations. Field requirements are defined in the manifest.json of the specific integration being used. |
| resourceId | string | yes | The resource identifier in the format proj/projKey:env/envKey:flag/flagKey (or equivalent for AI Configs and segments). Specifies which resource the approval request applies to. |
No output schema declared.
No examples provided.
create_approval_request_for_feature_flag Create Approval Request for Feature Flag ~283
Submit an approval request to modify a feature flag in a specific environment. The request includes semantic patch instructions that will be applied upon approval, with optional scheduling and third-party integration metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | A concise summary of the requested changes to the feature flag, helping reviewers understand the intent of the approval request. |
| environmentKey | string | yes | The unique identifier for the environment where the flag changes will be applied. |
| executionDate | string | – | Optional Unix timestamp (in milliseconds) specifying when the approval request instructions should be automatically executed. If omitted, execution occurs immediately upon approval. |
| featureFlagKey | string | yes | The unique identifier for the feature flag that requires approval for changes. |
| instructions | array | yes | An ordered list of semantic patch instructions that define the exact changes to apply to the feature flag. Instructions must follow the semantic patch format documented in the feature flag update API. |
| integrationConfig | object | – | Optional custom fields for third-party approval system integrations. Field definitions are provided in the integration's manifest.json file in the LaunchDarkly integration framework repository. |
| operatingOnId | string | – | The ID of an existing scheduled change, required only if your instructions modify or delete a previously scheduled change to the flag. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the feature flag. |
No output schema declared.
No examples provided.
create_big_segment_export Create Big Segment Export ~107
Initiates an export process for a large segment (synced or list-based) containing more than 15,000 entries. The export runs asynchronously and can be monitored for completion status.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project where the segment exists. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the segment to export. |
| segmentKey | string | yes | The unique identifier for the big segment to export. |
No output schema declared.
No examples provided.
create_big_segment_import Create Big Segment Import ~198
Initiate an import process for a big segment to add or replace list-based segment entries. This operation supports importing large datasets with more than 15,000 entries from a CSV file.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project. |
| file | string | – | Base64-encoded file content for upload. A CSV file containing the segment keys to import. Each row should contain one key entry. |
| mode | string | – | The import strategy: use `merge` to add new entries while preserving existing ones, or `replace` to overwrite all existing entries with the imported data. |
| projectKey | string | yes | The unique identifier for the project containing the segment. |
| segmentKey | string | yes | The unique identifier for the big segment to import data into. |
| waitOnApprovals | boolean | – | If true, the import process will pause and wait for any required approvals before processing the data. |
No output schema declared.
No examples provided.
create_data_export_destination Create Data Export Destination ~340
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).
| Name | Type | Req | Description |
|---|---|---|---|
| config | – | – | An object containing the configuration parameters required for your chosen destination type. Required fields vary: Azure Event Hubs needs namespace, name, policyName, and policyKey; Google Pub/Sub ne… |
| environmentKey | string | yes | The environment key that uniquely identifies the environment within the project where the destination will be created. |
| kind | string | – | The type of Data Export destination. Choose from: google-pubsub, kinesis, mparticle, segment, azure-event-hubs, snowflake-v2, databricks, bigquery, or redshift. Each type requires specific configurat… |
| name | string | – | A human-readable name for the Data Export destination. This name appears in the LaunchDarkly UI for easy identification. |
| on | boolean | – | Whether the Data Export destination is active and exporting events. When true, events are streamed to the destination; when false, the destination is paused. Displayed as the integration status in th… |
| projectKey | string | yes | The project key that uniquely identifies the LaunchDarkly project where the destination will be created. |
No output schema declared.
No examples provided.
create_deployment_event Create Deployment Event ~310
Record a deployment event for an application to track deployment lifecycle and metrics in engineering insights. Events can mark deployment start, completion, failure, or custom milestones.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | yes | The application key that identifies the service or component being deployed. LaunchDarkly automatically creates a new application record for each unique key. Typically matches your GitHub repository… |
| applicationKind | string | – | The type of application being deployed. Defaults to 'server' if not specified. Choose from: server, browser, or mobile. |
| deploymentMetadata | object | – | Optional JSON object with deployment-wide metadata such as build number or other information relevant to the entire deployment. |
| environmentKey | string | yes | The environment key (e.g., production, staging) where the deployment occurred. |
| eventMetadata | object | – | Optional JSON object with event-specific metadata such as build system version or other contextual information about this particular event. |
| eventType | string | yes | The type of deployment event being recorded. Choose from: 'started' (deployment beginning), 'finished' (deployment completed successfully), 'failed' (deployment failed), or 'custom' (for other event… |
| projectKey | string | yes | The project key that identifies which LaunchDarkly project this deployment belongs to. |
| version | string | yes | The version identifier for this deployment. Use at least the first seven characters of the commit SHA or a git tag. Only alphanumeric characters, periods, hyphens, and underscores are allowed. |
No output schema declared.
No examples provided.
create_environment Create Environment ~417
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.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | A hex color code (without '#') to visually distinguish this environment in the LaunchDarkly UI (e.g., 'F5A623' for orange). |
| confirmChanges | boolean | – | Optional: When enabled, requires explicit confirmation in the UI before applying any flag or segment changes in this environment. |
| critical | boolean | – | Optional: Marks this environment as critical, which may trigger additional safeguards or notifications for changes. |
| defaultTrackEvents | boolean | – | Optional: When enabled, automatically tracks detailed event data for newly created feature flags in this environment. |
| defaultTtl | integer | – | Optional: The default cache duration in minutes for the PHP SDK to store feature flag rules locally. Reduces API calls but may delay flag updates. |
| key | string | yes | A project-unique identifier for the environment, used in API calls and SDKs (e.g., 'prod', 'staging', 'dev'). |
| name | string | yes | A human-readable name for the environment (e.g., 'Production', 'Staging', 'Development'). |
| projectKey | string | yes | The unique identifier for the project where the environment will be created. |
| requireComments | boolean | – | Optional: When enabled, requires users to provide comments explaining the reason for any flag or segment changes made via the UI. |
| secureMode | boolean | – | Optional: When enabled, prevents client-side SDK users from viewing flag variations assigned to other users, enhancing security for sensitive environments. |
| sourceKey | string | – | Optional: The key of an existing environment to clone configuration from, including flags and segments. |
| tags | array | – | Optional: An array of tags to categorize and organize the environment (e.g., ['ops', 'production'], ['team:backend']). |
No output schema declared.
No examples provided.
create_experiment Create Experiment ~853
Create a new experiment in a LaunchDarkly project environment. After creation, you must create an iteration and update the experiment with the `startIteration` instruction to run it.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | array | – | Array of attribute names (e.g., 'country', 'device', 'os') that can be used to segment and analyze experiment results by user characteristics. |
| bayesianThreshold | string | – | For Bayesian analysis, the probability threshold (as a percentage) for determining if a variation is likely better than the baseline. Higher values require stronger evidence. |
| canReshuffleTraffic | boolean | – | Whether traffic can be reassigned to different variations when audience size changes. Defaults to true, allowing dynamic reallocation. |
| covariateId | string | – | The identifier of an uploaded covariate CSV file used to adjust analysis for known variables that may affect results. |
| dataSource | string | – | The source system for metric data analysis: 'launchdarkly' (default) uses LaunchDarkly's event data, 'snowflake' or 'databricks' connect to external data warehouses. |
| environmentKey | string | yes | The unique identifier for the environment within the project where the experiment will run. |
| flags | object | yes | Object containing the feature flag key and targeting rules that determine which users see which variations in this iteration. |
| holdoutId | string | – | The identifier of a holdout group to exclude from the experiment while measuring their metrics separately for comparison. |
| hypothesis | string | yes | A clear statement of the expected outcome or business hypothesis being tested by this experiment. |
| key | string | yes | A unique identifier for the experiment, used in API calls and references. Must be URL-safe. |
| methodology | string | – | The statistical methodology for analyzing results: 'bayesian' (default) uses probability-based analysis, 'frequentist' uses traditional hypothesis testing, or 'export_only' for external analysis. |
| metrics | array | yes | Array of metric objects defining which metrics will be measured and analyzed for this experiment. Each metric specifies how success is measured. |
| multipleComparisonCorrectionMethod | string | – | Method to correct for multiple comparisons in Frequentist analysis: 'bonferroni' is conservative, 'benjamini-hochberg' is less conservative. |
| multipleComparisonCorrectionScope | string | – | Scope of multiple comparison correction: 'variations' corrects across variations only, 'metrics' corrects across metrics only, or 'variations-and-metrics' corrects across both. |
| name | string | yes | A human-readable name for the experiment that describes its purpose. |
| primaryFunnelKey | string | – | The key of the primary funnel group (multi-step metric) to analyze. Either this or `primarySingleMetricKey` must be specified, but not both. |
| primarySingleMetricKey | string | – | The key of the primary metric to analyze. Either this or `primaryFunnelKey` must be specified, but not both. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project where the experiment will be created. |
| randomizationUnit | string | – | The unit used to consistently assign users to variations (e.g., 'user', 'account', 'organization'). Defaults to 'user'. |
| reallocationFrequencyMillis | integer | – | For multi-armed bandit experiments, the frequency in milliseconds at which traffic allocation is automatically rebalanced across variations based on performance. |
| sequentialTestingEnabled | boolean | – | Whether to enable sequential testing for Frequentist analysis, allowing results to be checked at interim points rather than only at the end. |
| significanceThreshold | string | – | For Frequentist analysis, the significance threshold (as a percentage) for statistical significance. Typical values are 5 for 95% confidence. |
| tags | array | – | Array of tags for organizing and categorizing the experiment for easier discovery and management. |
| testDirection | string | – | For Frequentist analysis, whether the test is one-sided (directional) or two-sided (non-directional) when comparing variations to baseline. |
| treatments | array | yes | Array of treatment objects defining the variations being tested. Each treatment corresponds to a feature flag variation. |
No output schema declared.
No examples provided.
create_extinction_event Create Extinction Event ~95
Create a new extinction event for a specific branch in a repository. Extinction events track code reference removals or deprecations.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | Array of extinction event objects defining the code references and metadata for the extinction event. |
| branch | string | yes | The branch name, URL-encoded, where the extinction event applies. |
| repo | string | yes | The repository name where the extinction event will be created. |
No output schema declared.
No examples provided.
create_feature_flag Create Feature Flag ~442
Create a feature flag in a project with customizable variations, targeting defaults, and optional migration settings. Supports cloning existing flags and configuring SDK availability.
| Name | Type | Req | Description |
|---|---|---|---|
| clone | string | – | Optional key of an existing feature flag to clone. Cloning copies the full targeting configuration across all environments, including on/off state, to the new flag. |
| customProperties | object | – | Custom metadata as key-value pairs where each key maps to a name and array of values. Typically used for integration-related data. |
| initialPrerequisites | array | – | Array of prerequisite flags that must be satisfied before this flag is evaluated in all environments. |
| isFlagOn | boolean | – | Automatically enable the flag across all environments upon creation. Defaults to false. |
| key | string | yes | A unique identifier for the flag used in your application code. Must be distinct within the project. |
| name | string | yes | A human-readable name for the feature flag to display in the UI. |
| offVariation | integer | yes | The index of the variation to serve when targeting is disabled. Must correspond to a valid variation index. |
| onVariation | integer | yes | The index of the variation to serve when targeting is enabled. Must correspond to a valid variation index. |
| projectKey | string | yes | The project key that uniquely identifies the project where the feature flag will be created. |
| purpose | string | – | The intended purpose of the flag. Use 'migration' for migration flags (which auto-generate variations based on stage count) or 'holdout' for holdout flags. |
| tags | array | – | Array of tags to organize and categorize the feature flag. Defaults to an empty array. |
| temporary | boolean | – | Mark the flag as temporary (intended for short-term use). Defaults to true. |
| usingEnvironmentId | boolean | yes | Enable or disable availability for client-side SDKs. Defaults to false. |
| usingMobileKey | boolean | yes | Enable or disable availability for mobile SDKs. Defaults to true. |
| variations | array | – | Array of possible flag variations with unique values. If omitted, defaults to two boolean variations: true and false. Order matters as variations are referenced by index. |
No output schema declared.
No examples provided.
create_flag_copy_approval_request Create Flag Copy Approval Request ~208
Create an approval request to copy a feature flag's configuration from a source environment to a target environment. This allows controlled promotion of flag settings across your deployment environments.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | A brief summary explaining the purpose of this configuration copy request (e.g., 'copy flag settings to another environment'). |
| environmentKey | string | yes | The unique identifier for the target environment where the flag configuration will be copied to. |
| featureFlagKey | string | yes | The unique identifier for the feature flag whose configuration will be copied. |
| includedActions | array | – | Optional list of specific flag changes to copy from source to target environment (e.g., 'updateOn'). You may specify either included or excluded actions, but not both. If omitted, all flag changes wi… |
| key | string | yes | The unique identifier for the source environment from which the flag configuration will be copied. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
create_flag_trigger Create Flag Trigger ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier of the environment where the trigger will be active. |
| featureFlagKey | string | yes | The unique identifier of the feature flag that will be triggered. |
| instructions | array | – | An array containing a single object that specifies the action to perform when the trigger is activated. The object must have a 'kind' field set to either 'turnFlagOn' or 'turnFlagOff' to control the… |
| integrationKey | string | yes | The unique identifier of the integration that will activate this trigger. Use 'generic-trigger' for integrations that are not explicitly supported by the system. |
| projectKey | string | yes | The unique identifier of the project containing the feature flag. |
No output schema declared.
No examples provided.
create_insight_group Create Insight Group ~222
Create a new insight group to organize and monitor engineering insights across a specific project and environment. Optionally scope the group to specific applications.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKeys | array | – | Optional list of application keys to include in this insight group (e.g., ['billing-service', 'inventory-service']). If omitted, the group will automatically include data from all applications in the… |
| environmentKey | string | yes | The environment key (e.g., 'production', 'staging') that this insight group monitors. Scopes insights to a specific deployment environment. |
| key | string | yes | A unique identifier key for the insight group in kebab-case format (e.g., 'default-production-all-apps'). Used for API references and internal lookups. |
| name | string | yes | A human-readable name for the insight group (e.g., 'Production - All Apps'). Used for display and identification in the UI. |
| projectKey | string | yes | The project key that this insight group belongs to. Determines which project's data and configuration the group operates within. |
No output schema declared.
No examples provided.
create_layer Create Layer ~176
Create a new layer within a project to enable mutually-exclusive traffic allocation across experiments. Experiments running in the same layer will have their traffic split exclusively among them.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | A detailed description explaining the layer's purpose and scope within the application. This helps team members understand what experiments belong in this layer. |
| key | string | yes | A unique identifier for the layer, typically in kebab-case format (e.g., 'checkout-flow'). This key is used to reference the layer in API calls and must be distinct within the project. |
| name | string | yes | A human-readable name for the layer that describes its purpose (e.g., 'Checkout Flow'). This is displayed in the UI and should be clear and descriptive. |
| projectKey | string | yes | The unique identifier for the project where the layer will be created. |
No output schema declared.
No examples provided.
create_metric Create Metric ~812
Create a new metric in a specified project to track user interactions or custom events. The metric structure varies based on the kind (pageview, click, or custom) and whether it measures conversions or numeric values.
| Name | Type | Req | Description |
|---|---|---|---|
| attribute | string | – | The name of the context attribute or event property to filter on (e.g., 'country'). Not applicable for group-type filters. |
| dataSourceKey | string | yes | The unique identifier for the data source that will provide events for this metric. |
| dataSourceName | string | – | The human-readable name of the data source providing events for this metric. |
| disabled | boolean | – | Set to true to disable automatic default values for missing unit events during result calculation. Defaults to false. |
| environmentKey | string | – | The environment key associated with this metric (e.g., 'production', 'staging'). |
| eventKey | string | – | The event key identifier used in your application code to trigger this metric. Required for custom conversion and numeric metrics (e.g., 'Order placed'). |
| integrationKey | string | – | The integration key for connecting this metric to an external data source or service. |
| isNumeric | boolean | – | For custom metrics only: set to true to track numeric value changes against a baseline, or false to track conversions when users take an action. |
| key | string | yes | A unique identifier for the metric, used as a reference key in your codebase (e.g., 'metric-key-123abc'). |
| kind | string | yes | The type of event this metric tracks: 'pageview' for page views, 'click' for user clicks, or 'custom' for application-defined events. |
| name | string | – | A human-readable name for the metric to display in the UI (e.g., 'Example metric'). |
| negate | boolean | yes | Set to true to invert the filter logic (e.g., 'in' becomes 'not in'). Defaults to false. |
| op | string | yes | The comparison operator to apply (e.g., 'in', 'equals', 'contains'). Determines how values are matched against the filter. |
| projectKey | string | yes | The unique identifier for the project where the metric will be created. |
| randomizationUnits | array | – | An array of randomization units allowed for this metric (e.g., ['user']). Determines how experiment variations are assigned. |
| selector | string | – | One or more CSS selectors identifying the elements to track. Required only for click metrics (e.g., '.dropdown-toggle'). |
| successCriteria | string | – | Success criteria for numeric custom metrics: 'HigherThanBaseline' if increases are favorable, 'LowerThanBaseline' if decreases are favorable. Optional for conversion metrics. |
| tags | array | – | An array of tags to organize and categorize the metric (e.g., ['example-tag']). |
| traceQuery | string | – | A trace query to identify relevant traces for this metric (e.g., 'service.name = "checkout"'). Required only for trace metrics. |
| traceValueLocation | string | – | The location within a trace to extract numeric values from (e.g., 'duration'). Required only for numeric trace metrics. |
| type | string | yes | The filter type: 'contextAttribute' to filter on user context attributes, 'eventProperty' to filter on event properties, or 'group' to filter on group membership. |
| unit | string | – | The unit of measurement for numeric custom metrics (e.g., 'orders', 'revenue'). Only applicable when tracking numeric values. |
| urls | array | – | One or more target URLs to track. Required for click and pageview metrics. Specify as an array of URL strings. |
| value | number | – | The default numeric value applied to missing unit events when disabled is false. Currently only 0 is supported. |
| values | array | yes | An array of values to match against the filter. For numeric values, do not exceed 14 decimal places (e.g., ['JP'] for country filtering). |
No output schema declared.
No examples provided.
create_metric_group Create Metric Group ~226
Create a new metric group within a project to organize and track related metrics. Metric groups can be configured as standard collections or funnel-type progressions.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | A unique identifier for the metric group used in API references and integrations. If not provided, one will be auto-generated. |
| kind | string | yes | The classification type for the metric group: 'standard' for a regular collection of metrics, or 'funnel' for a sequential progression of steps. |
| maintainerId | string | yes | The ID of the team member responsible for maintaining and managing this metric group. |
| metrics | array | yes | An ordered list of metrics to include in the group. The order is significant and determines the sequence in which metrics are displayed and processed. |
| name | string | yes | A human-readable name for the metric group that appears in the UI and reports. |
| projectKey | string | yes | The unique identifier of the project where the metric group will be created. |
| tags | array | yes | One or more tags to categorize and organize the metric group for easier discovery and filtering. |
No output schema declared.
No examples provided.
create_model_config Create Model Config ~324
Create a new AI model configuration for your project. This configuration defines model identity, provider details, and cost metrics for use across AI features in your project.
| Name | Type | Req | Description |
|---|---|---|---|
| costPerInputToken | number | – | The cost in USD per input token for this model, used for tracking and billing calculations. |
| costPerOutputToken | number | – | The cost in USD per output token for this model, used for tracking and billing calculations. |
| customParams | object | – | Optional object for custom parameters specific to your implementation or use case. |
| icon | string | – | An optional icon identifier or URL to visually represent this model in the UI. |
| id | string | yes | The model identifier recognized by the third-party provider (e.g., 'gpt-4', 'claude-3-opus'). This is the identifier sent to the provider's API. |
| key | string | yes | A unique identifier key for this model configuration within the project, used for internal references and API calls. |
| name | string | yes | A human-readable display name for the model that will appear in the UI. |
| params | object | – | Optional object containing provider-specific parameters and configuration settings for this model. |
| projectKey | string | yes | The project identifier where this model configuration will be created (e.g., 'default'). |
| provider | string | – | The AI service provider for this model (e.g., 'openai', 'anthropic', 'google'). Determines how requests are routed and authenticated. |
| tags | array | – | Optional array of tags for categorizing and organizing this model configuration. |
No output schema declared.
No examples provided.
create_project Create Project ~246
Create a new project with a unique key and name. Configure SDK availability, naming conventions, and initial environments for the project.
| Name | Type | Req | Description |
|---|---|---|---|
| case | string | – | Optional casing convention to enforce for new flag keys in this project. Choose from: camelCase, upperCamelCase, snakeCase, kebabCase, or constantCase. |
| environments | array | – | Optional list of environments to create for this project. If omitted, default environments will be created automatically. |
| key | string | yes | A unique identifier for the project used in code references (e.g., 'project-key-123abc'). Must be unique within your account. |
| name | string | yes | A human-friendly display name for the project (e.g., 'My Project'). |
| prefix | string | – | Optional prefix to enforce for all new flag keys in this project (e.g., 'enable-'). |
| tags | array | – | Optional list of tags to organize and categorize the project (e.g., ['ops']). |
| usingEnvironmentId | boolean | yes | Enable or disable availability of this project for client-side SDKs. |
| usingMobileKey | boolean | yes | Enable or disable availability of this project for mobile SDKs. |
No output schema declared.
No examples provided.
create_prompt_snippet Create Prompt Snippet ~120
Create a new prompt snippet within a project to store reusable AI prompt text for use in AI configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | A unique key identifier for the prompt snippet within the project, used for referencing the snippet in configurations. |
| name | string | yes | A human-readable name for the prompt snippet to help identify its purpose. |
| projectKey | string | yes | The unique identifier for the project where the prompt snippet will be created. |
| text | string | yes | The text content of the prompt snippet that will be stored and reused in AI configurations. |
No output schema declared.
No examples provided.
create_relay_proxy_config Create Relay Proxy Configuration ~100
Create a new Relay Proxy configuration that controls which environments and projects the Relay Proxy should include or exclude.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A human-readable name for this Relay Proxy configuration. Used to identify and manage the configuration. |
| policy | array | yes | An inline policy array that defines which environments and projects this Relay Proxy should include or exclude. Policy items are evaluated in order to determine scope. Refer to the inline policy docu… |
No output schema declared.
No examples provided.
create_release_pipeline Create Release Pipeline ~276
Create a new release pipeline for a project. The first pipeline created automatically becomes the default; subsequent pipelines can be set as default via the project update API. Projects support up to 20 release pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| isLegacy | boolean | – | Optional boolean flag. When true, enables this pipeline for Release Automation features. Controls whether the pipeline participates in automated release workflows. |
| isProjectDefault | boolean | – | Optional boolean flag. When true, sets this pipeline as the default for the project. If not specified, only the first pipeline created becomes the default. |
| key | string | yes | A unique identifier for this release pipeline within the project (e.g., 'standard-pipeline'). Used to reference the pipeline in API calls and configurations. |
| name | string | yes | A human-readable name for the release pipeline (e.g., 'Standard Pipeline'). Displayed in the UI and used for identification. |
| phases | array | yes | An ordered array of phase objects that define logical groupings of environments. Each phase shares attributes for coordinating feature rollouts across its environments. |
| projectKey | string | yes | The project key that uniquely identifies the project where the release pipeline will be created. |
| tags | array | – | An optional list of tags to categorize and organize the release pipeline (e.g., ['example-tag']). Useful for filtering and searching pipelines. |
No output schema declared.
No examples provided.
create_repository Create Repository ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commitUrlTemplate | string | – | A URL template for constructing links to specific commits. Use the placeholder ${sha} to represent the commit hash (e.g., 'https://github.com/launchdarkly/LaunchDarkly-Docs/commit/${sha}'). |
| defaultBranch | string | – | The repository's default branch name. Defaults to 'main' if not specified (e.g., 'main', 'master', or 'develop'). |
| hunkUrlTemplate | string | – | A URL template for constructing links to specific code hunks or lines. Use placeholders ${sha} for commit hash, ${filePath} for file path, and ${lineNumber} for line number (e.g., 'https://github.com… |
| name | string | yes | The name of the repository (e.g., 'LaunchDarkly-Docs'). Used as the unique identifier for this repository. |
| sourceLink | string | – | A URL where the repository can be accessed (e.g., a GitHub repository URL). Provides a direct link to the repository source. |
No output schema declared.
No examples provided.
create_scheduled_changes_for_flag Create Scheduled Changes for Flag ~191
Schedule semantic patch instructions to be applied to a feature flag at a specified future date. Optionally allow the operation to succeed even if scheduled changes conflict with existing ones.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key where the scheduled changes will be applied. |
| executionDate | string | yes | Unix timestamp (milliseconds) indicating when the scheduled changes should be executed. |
| featureFlagKey | string | yes | The feature flag key to schedule changes for. |
| ignoreConflicts | boolean | – | If true, the operation succeeds even when these instructions conflict with existing scheduled changes. If false (default), the operation fails on conflicts. |
| instructions | array | yes | Array containing a single object with `kind: "scheduled_action"` and semantic patch instructions. Supported instructions are the same as those available when updating a feature flag directly. |
| projectKey | string | yes | The project key that contains the feature flag. |
No output schema declared.
No examples provided.
create_segment Create Segment ~237
Create a new segment in a LaunchDarkly project environment. Segments can be standard (rule-based or small list-based) or big segments (large list-based or synced) for targeting contexts.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project where the segment will be created. |
| key | string | yes | A unique identifier for the segment used in code and API references. Must be distinct within the project. |
| name | string | yes | A human-readable name for the segment that describes its purpose or audience. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project where the segment will be created. |
| tags | array | – | Optional labels to organize and categorize the segment for easier management and filtering. |
| unbounded | boolean | – | Set to true to create a big segment for handling more than 15,000 individual targets; false for standard segments with rule-based or smaller list-based criteria. |
| unboundedContextKind | string | – | For big segments, specifies the context kind (e.g., 'device', 'user') that the segment targets. Required when creating a big segment. |
No output schema declared.
No examples provided.
create_team Create Team ~223
Create a new team in LaunchDarkly with optional members, custom roles, and permission grants. Supports expanding the response to include members, roles, projects, and maintainers.
| Name | Type | Req | Description |
|---|---|---|---|
| customRoleKeys | array | – | List of custom role keys to assign to the team, granting access to those roles. Provide as an array of role key strings. |
| key | string | yes | Unique identifier for the team. Used to reference the team in API calls and must be URL-safe. |
| memberIDs | array | – | Array of member IDs to add to the team upon creation. Each ID should be a valid LaunchDarkly member identifier. |
| name | string | yes | Human-readable name for the team. This is displayed in the LaunchDarkly UI and should be descriptive. |
| permissionGrants | array | – | Array of permission grants that define specific actions the team can perform without requiring a custom role. Each grant specifies an action and resource scope. |
| roleAttributes | object | – | Object containing role attributes as key-value pairs. Attributes provide additional context or metadata for the team's roles. |
No output schema declared.
No examples provided.
create_view Create View ~202
Create a new view within a specified project. Views are used to organize and filter feature flags and other resources within your LaunchDarkly project.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Currently only 'beta' is supported. |
| generateSdkKeys | boolean | – | Whether to automatically generate SDK keys associated with this view. Defaults to false if not specified. |
| key | string | yes | A unique identifier for the view within the project. This key is used to reference the view in API calls and must be distinct from other views in the same project. |
| name | string | yes | A human-readable display name for the view that appears in the user interface. |
| projectKey | string | yes | The project key that uniquely identifies the project where the view will be created (e.g., 'default'). |
| tags | array | – | An optional list of tags to categorize and organize the view. Tags help with filtering and searching views. |
No output schema declared.
No examples provided.
delete_agent_graph Delete Agent Graph ~93
Permanently delete an agent graph and all of its associated edges from a project. This operation cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Must be set to 'beta'. |
| graphKey | string | yes | The unique identifier for the agent graph to delete. |
| projectKey | string | yes | The unique identifier for the project containing the agent graph to delete. |
No output schema declared.
No examples provided.
delete_agent_optimization Delete Agent Optimization ~64
Permanently delete an agent optimization configuration from a project. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| optimizationKey | string | yes | The unique identifier of the agent optimization to delete. |
| projectKey | string | yes | The unique identifier of the project containing the agent optimization to delete. |
No output schema declared.
No examples provided.
delete_ai_config Delete AI Config ~79
Permanently delete an AI Config from a project. This operation removes the configuration and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier of the AI Config to delete. |
| projectKey | string | yes | The unique identifier of the project containing the AI Config. Use 'default' for the default project or specify a custom project key. |
No output schema declared.
No examples provided.
delete_ai_config_variation Delete AI Config Variation ~90
Permanently delete a specific variation of an AI Config. This removes the variation and all its associated data from the project.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config whose variation should be deleted. |
| projectKey | string | yes | The unique identifier for the project containing the AI Config. |
| variationKey | string | yes | The unique identifier for the specific variation to delete. |
No output schema declared.
No examples provided.
delete_ai_tool Delete AI Tool ~71
Permanently delete an AI tool from a project. This action cannot be undone and will remove the tool and all associated configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier of the project containing the AI tool to delete. |
| toolKey | string | yes | The unique identifier of the AI tool to delete. |
No output schema declared.
No examples provided.
delete_announcement Delete Announcement ~55
Permanently delete an announcement by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| announcementId | string | yes | The unique identifier of the announcement to delete, provided as a numeric string (e.g., '1234567890'). |
No output schema declared.
No examples provided.
delete_application Delete Application ~60
Permanently delete an application by its unique key. This action cannot be undone and will remove all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | yes | The unique identifier for the application to delete. This is a string value that uniquely identifies the application within the system. |
No output schema declared.
No examples provided.
What is the com.mcparmory/launchdarkly MCP server?
com.mcparmory/launchdarkly is an MCP server listed in the public MCP registry as com.mcparmory/launchdarkly. Manage feature flags, segments, projects, environments, and team members. This page covers its PyPI package (mcparmory-launchdarkly).
Is the com.mcparmory/launchdarkly MCP server safe to use?
com.mcparmory/launchdarkly scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/launchdarkly MCP server expose?
com.mcparmory/launchdarkly exposes 274 tools: list_relay_proxy_configs, create_relay_proxy_config, get_relay_proxy_config, update_relay_auto_config, delete_relay_auto_config, and 269 more. Their descriptions and schemas cost roughly 36,460 tokens of context every time the server is loaded.
Is the com.mcparmory/launchdarkly MCP server still maintained?
com.mcparmory/launchdarkly is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.