com.mcparmory/launchdarkly
OCI · GHCR.IO/MCPARMORY/LAUNCHDARKLY:1.0.4 · 2 COMPONENTS · SCANNED SEP 21
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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
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: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 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 Management83
- Stability observed for 25 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/launchdarkly MCP server?
com.mcparmory/launchdarkly runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/launchdarkly:1.0.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/launchdarkly:1.0.4
claude mcp add com-mcparmory-launchdarkly -- docker run --rm -i ghcr.io/mcparmory/launchdarkly:1.0.4
{
"mcpServers": {
"com-mcparmory-launchdarkly": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/launchdarkly:1.0.4"
]
}
}
} {
"servers": {
"com-mcparmory-launchdarkly": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/launchdarkly:1.0.4"
]
}
}
} codex mcp add com-mcparmory-launchdarkly -- docker run --rm -i ghcr.io/mcparmory/launchdarkly:1.0.4
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-launchdarkly": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/launchdarkly:1.0.4"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-launchdarkly:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/launchdarkly:1.0.4"] {
"McpServers": {
"com-mcparmory-launchdarkly": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/launchdarkly:1.0.4"
]
}
}
} {
"mcpServers": {
"com-mcparmory-launchdarkly": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/launchdarkly:1.0.4"
]
}
}
} 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 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 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 +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.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 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.
- 8 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.
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 21 Sept 2026 · Analysed oci/ghcr.io/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 | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
list_repositories_insights List Repositories Insights ~39
Retrieve a list of repositories integrated with LaunchDarkly's engineering insights. Optionally expand the response to include associated project details for each repository.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_scheduled_changes_for_flag List Scheduled Changes for Flag ~106
Retrieve all scheduled changes pending application to a feature flag in a specific environment. This shows future modifications that will be automatically applied at their scheduled times.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which to list scheduled changes for the feature flag. |
| featureFlagKey | string | yes | The unique identifier for the feature flag whose scheduled changes you want to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
list_segments List Segments ~90
Retrieve all segments in a project environment, including rule-based, list-based, and synced segments. Supports filtering by tags, keys, segment type, external sync status, and fuzzy search across segment metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project from which to retrieve segments. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the segments. |
No output schema declared.
No examples provided.
list_tags List Tags ~168
Retrieve a list of tags, optionally filtered by resource type, prefix, or archived status, and as of a specific point in time.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Include or exclude archived tags in the results. When true, returns archived tags; when false or omitted, returns only active tags. |
| asOf | string | – | Retrieve tags as they existed at a specific point in time, specified in ISO 8601 format. Defaults to the current time if not provided. |
| kind | array | – | Filter tags by resource type. Accepts multiple types including flag, project, environment, segment, metric, metric-data-source, aiconfig, and view. If not specified, returns tags of all types. |
| pre | string | – | Return only tags that begin with the specified prefix string. |
No output schema declared.
No examples provided.
list_team_maintainers List Team Maintainers ~56
Retrieve the list of maintainers assigned to a specific team. Maintainers have elevated permissions to manage team settings and members.
| Name | Type | Req | Description |
|---|---|---|---|
| teamKey | string | yes | The unique identifier for the team whose maintainers you want to retrieve. |
No output schema declared.
No examples provided.
list_team_roles List Team Roles ~52
Retrieve all custom roles assigned to a specific team. Custom roles define granular permissions for team members within LaunchDarkly.
| Name | Type | Req | Description |
|---|---|---|---|
| teamKey | string | yes | The unique identifier for the team whose roles you want to retrieve. |
No output schema declared.
No examples provided.
list_teams List Teams ~44
Retrieve a paginated list of teams with optional filtering and field expansion. By default returns the first 20 teams; use pagination links and the limit parameter to navigate through results.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_views List Views ~84
Retrieve all views available in a specified project. Views are saved configurations or perspectives for organizing and displaying project data.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | API version specification. Must be set to 'beta' to access this endpoint. |
| projectKey | string | yes | The unique identifier for the project. Use 'default' for the default project or specify a custom project key. |
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~34
Retrieve a complete list of all configured webhooks for the account. Use this to view all active webhook endpoints and their configurations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_workflow_templates List Workflow Templates ~107
Retrieve workflow templates for your account with optional filtering and summary mode. Use the summary parameter to get lightweight template metadata or the search parameter to filter templates by name or description.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Filter templates by searching for a substring within template names or descriptions. The search is case-sensitive and matches partial strings. |
| summary | boolean | – | Return lightweight template summaries instead of full template objects. When true, returns only essential metadata; when false or omitted, returns complete template details. |
No output schema declared.
No examples provided.
list_workflows_for_feature_flag List Workflows for Feature Flag ~152
Retrieve all workflows associated with a feature flag in a specific environment. Optionally filter results by workflow status to view active, completed, or failed workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which to retrieve workflows. |
| featureFlagKey | string | yes | The unique identifier for the feature flag whose workflows you want to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
| status | string | – | Filter workflows by their current status. Supported values are `active` (ongoing workflows), `completed` (finished workflows), and `failed` (workflows that encountered errors). Omit to retrieve workf… |
No output schema declared.
No examples provided.
remove_flag_follower Remove Flag Follower ~133
Remove a member as a follower of a feature flag in a specific project and environment. Members with reader roles can only remove themselves as followers.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the flag follower relationship exists. |
| featureFlagKey | string | yes | The unique identifier for the feature flag from which to remove the follower. |
| memberId | string | yes | The unique identifier of the member to remove as a follower. Members with reader roles can only remove themselves; other roles can remove any member. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
remove_repository_project_association Remove Repository Project Association ~81
Remove the association between a repository and a project in engineering insights. This operation disassociates the specified project from the given repository.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project to be disassociated from the repository. |
| repositoryKey | string | yes | The unique identifier for the repository from which the project association will be removed. |
No output schema declared.
No examples provided.
remove_restricted_models Remove Restricted Models ~92
Remove one or more AI models from the project's restricted list by their keys. This allows previously restricted models to be used again in the project.
| Name | Type | Req | Description |
|---|---|---|---|
| keys | array | yes | An array of model keys to remove from the restricted list. Each key identifies a specific model to unrestrict. |
| projectKey | string | yes | The project identifier (e.g., 'default') that contains the restricted model list to modify. |
No output schema declared.
No examples provided.
reorder_release_policies Reorder Release Policies ~136
Reorder the release policies for a project by specifying their desired sequence. This operation updates the policy execution order without modifying individual policy configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this operation. Currently only the beta version is available. |
| body | array | yes | An ordered array of release policy keys that defines the new execution sequence. The order of keys in this array determines the order in which policies are evaluated and applied. |
| projectKey | string | yes | The unique identifier for the project whose release policies should be reordered. Use the project key assigned during project creation (e.g., 'default'). |
No output schema declared.
No examples provided.
reset_environment_sdk_key Reset Environment SDK Key ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment whose SDK key should be reset. |
| expiry | string | – | Optional grace period for the old SDK key expiration, specified in UNIX milliseconds. If not provided, the old key expires immediately. This allows clients using the old key to transition to the new… |
| projectKey | string | yes | The unique identifier for the project containing the environment. |
No output schema declared.
No examples provided.
reset_mobile_key_for_environment Reset Mobile Key for Environment ~79
Reset an environment's mobile SDK key, immediately expiring the previous key. This operation generates a new mobile key for the specified environment within a project.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment whose mobile SDK key should be reset. |
| projectKey | string | yes | The unique identifier for the project containing the environment. |
No output schema declared.
No examples provided.
reset_relay_auto_config Reset Relay Auto Config ~85
Generate a new secret key for a Relay Proxy configuration, optionally setting an expiration time for the previous key before it becomes invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| expiry | string | – | Optional Unix epoch time in milliseconds when the old configuration key should expire. If not provided, the old key expires immediately upon reset. |
| id | string | yes | The unique identifier of the Relay Proxy configuration to reset. |
No output schema declared.
No examples provided.
reset_token Reset Token ~86
Generate a new secret key for an access token, optionally setting an expiration time for the old key. Use this to rotate credentials while maintaining token validity.
| Name | Type | Req | Description |
|---|---|---|---|
| expiry | string | – | Optional Unix epoch time in milliseconds when the old token key should expire. If not provided, the old key expires immediately upon reset. |
| id | string | yes | The unique identifier of the access token to reset. |
No output schema declared.
No examples provided.
review_approval_request_for_flag Review Approval Request for Flag ~142
Submit a review decision on a pending approval request for a feature flag, either approving, declining, or commenting on the proposed changes.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the approval request applies. |
| featureFlagKey | string | yes | The unique identifier for the feature flag being reviewed. |
| id | string | yes | The unique identifier for the approval request being reviewed. |
| kind | string | – | The type of review action: approve to accept the changes, decline to reject them, or comment to provide feedback without a final decision. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
schedule_user_target_removal_on_flag Schedule User Target Removal on Flag ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key where the feature flag is configured. |
| featureFlagKey | string | yes | The feature flag key to update expiring user targets for. |
| instructions | array | yes | Array of semantic patch instructions to add, update, or remove user target removal dates. Each instruction must specify a kind (addExpireUserTargetDate, updateExpireUserTargetDate, or removeExpireUse… |
| projectKey | string | yes | The project key that contains the feature flag. |
No output schema declared.
No examples provided.
search_audit_log_entries Search Audit Log Entries ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | Array of resource specifiers to restrict results to specific resources or resource collections. Use LaunchDarkly resource specifier syntax to target particular entities (e.g., projects, environments,… |
| q | string | – | Full-text search query to filter audit log entries by resource name or partial matches. Searches across resource names and related metadata. |
No output schema declared.
No examples provided.
search_context_instances Search Context Instances ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| continuationToken | string | – | Pagination token for retrieving subsequent result pages. Use the `next` link from previous responses when available, or provide a continuation token to fetch results after a specific sort value. |
| environmentKey | string | yes | The environment key that identifies which environment within the project to search. |
| filter | string | – | Filter expression to narrow results by context attributes. Supports nested filter syntax for querying kindKeys, timestamps, and other context properties. See LaunchDarkly filtering documentation for… |
| includeTotalCount | boolean | – | Whether to include the total count of all matching context instances in the response (defaults to true). |
| limit | integer | – | Maximum number of context instances to return in a single response, between 1 and 50 items (defaults to 20). |
| projectKey | string | yes | The project key that identifies which project contains the context instances to search. |
| sort | string | – | Field to sort results by. Use `ts` for ascending timestamp order or `-ts` for descending timestamp order. |
No output schema declared.
No examples provided.
search_contexts Search Contexts ~218
Search for contexts in a LaunchDarkly environment using filters, sorting, and pagination. Supports advanced filtering by context attributes and kinds to find specific contexts matching your criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key that identifies the specific environment within the project where contexts will be searched. |
| filter | string | – | Filter expression to narrow results by context attributes and kinds. Supports multiple conditions using operators like 'startsWith' and 'anyOf', separated by commas. |
| includeTotalCount | boolean | – | Whether to include the total count of all matching contexts in the response. Defaults to true if not specified. |
| limit | integer | – | Maximum number of contexts to return in the response. Accepts values up to 50, with a default of 20 if not specified. |
| projectKey | string | yes | The project key that identifies the LaunchDarkly project containing the environment to search. |
| sort | string | – | Field to sort results by. Use 'ts' for ascending chronological order or '-ts' for descending order by timestamp. |
No output schema declared.
No examples provided.
submit_approval_request_review Submit Approval Request Review ~92
Submit a review decision on an approval request by approving, declining, or adding a comment to the proposed changes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the approval request being reviewed. |
| kind | string | – | The type of review action to perform: 'approve' to accept the changes, 'decline' to reject them, or 'comment' to provide feedback without making a final decision. |
No output schema declared.
No examples provided.
update_agent_graph Update Agent Graph ~235
Update an existing agent graph by modifying its configuration. Provide only the fields you want to change; unspecified fields retain their current values. If updating the root node or graph structure, both rootConfigKey and edges must be provided together as they are treated as a complete replacement.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Must be set to 'beta'. |
| edges | array | – | An ordered array of edges defining the graph structure and connections between nodes. When provided, rootConfigKey must also be included in the same request, and both will completely replace all exis… |
| graphKey | string | yes | The unique identifier for the agent graph to update. |
| name | string | – | A human-readable name for the agent graph. Use this to provide a descriptive label for the graph. |
| projectKey | string | yes | The unique identifier for the project containing the agent graph. |
| rootConfigKey | string | – | The AI Config key designating the root node of the graph. When provided, edges must also be included in the same request, and both will completely replace existing values. |
No output schema declared.
No examples provided.
update_agent_optimization Update Agent Optimization ~302
Update an existing agent optimization configuration for a project. This operation creates a new version of the optimization with the provided changes.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceStatements | array | – | A list of acceptance criteria statements that define successful agent behavior. Each statement should clearly specify expected outcomes. |
| groundTruthResponses | array | – | A list of ground truth responses corresponding to test inputs. Used as reference standards for evaluating agent accuracy. |
| judgeModel | string | – | The model identifier to use as a judge for evaluating agent performance against acceptance criteria. |
| judges | array | – | A list of judge configurations or identifiers used to evaluate agent responses. Multiple judges can be specified for consensus-based evaluation. |
| maxAttempts | integer | – | The maximum number of attempts allowed for the agent during optimization execution. |
| metricKey | string | – | The identifier of the metric to optimize against. Specifies which performance metric should be the primary optimization target. |
| modelChoices | array | – | An ordered list of model identifiers to evaluate during optimization. Order may affect evaluation priority. |
| optimizationKey | string | yes | The unique identifier of the agent optimization to update. |
| projectKey | string | yes | The unique identifier of the project containing the agent optimization. |
| userInputOptions | array | – | A list of user input options or scenarios to test during optimization. Defines the range of inputs the agent should handle. |
| variableChoices | array | – | An ordered list of variable configurations to test during optimization. Order may affect evaluation sequence. |
No output schema declared.
No examples provided.
update_ai_config Update AI Config ~171
Update an existing AI Config by modifying specific fields. Only the fields included in the request body will be updated; other fields remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config to update. |
| evaluationMetricKey | string | – | The unique identifier of the evaluation metric to use for assessing this AI Config's performance. |
| isInverted | boolean | – | Set to true if the evaluation metric is inverted, meaning lower values indicate better performance. Set to false if higher values are better. |
| name | string | – | The new name for the AI Config. |
| projectKey | string | yes | The unique identifier for the project containing the AI Config to update. |
| tags | array | – | A list of tags to associate with the AI Config. Tags are used for organization and filtering. |
No output schema declared.
No examples provided.
update_ai_config_targeting Update AI Config Targeting ~170
Update an AI Config's targeting rules, variations, and rollouts using semantic patch instructions. Supports adding/removing rules and clauses, managing individual context targets, and configuring percentage-based rollouts.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config to update. |
| environmentKey | string | yes | The unique identifier for the LaunchDarkly environment where the AI Config targeting applies. |
| instructions | array | yes | An array of semantic patch instructions that define the targeting changes to apply. Each instruction must include a `kind` property specifying the operation type (e.g., addRule, addClauses, removeTar… |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the AI Config. |
No output schema declared.
No examples provided.
update_ai_config_variation Update AI Config Variation ~257
Update an existing AI Config variation by modifying its properties. Changes create a new version of the variation while preserving the original.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config containing the variation to update. |
| instructions | string | – | Instructions that guide the agent's behavior when this AI Config operates in agent mode. |
| judges | array | – | Array of judge objects that evaluate this variation's performance. Replaces all existing judges; provide an empty array to remove all judge attachments. |
| messages | array | – | Array of message objects defining the conversation structure. Each message has a role (e.g., 'system', 'user', 'assistant') and content text. Order matters and represents the conversation sequence. |
| modelConfigKey | string | – | The unique identifier for the model configuration to use with this variation. |
| name | string | – | A human-readable name for this variation. |
| projectKey | string | yes | The unique identifier for the project containing the AI Config. |
| state | string | – | The lifecycle state of the variation. Must be either 'archived' to hide the variation or 'published' to make it active. |
| variationKey | string | yes | The unique identifier for the variation to update. |
No output schema declared.
No examples provided.
update_ai_tool Update AI Tool ~149
Update an existing AI tool's configuration, including its parameter schema for LLM consumption and custom application-level settings.
| Name | Type | Req | Description |
|---|---|---|---|
| customParameters | object | – | Custom metadata and configuration settings for application-level use. These parameters are not exposed to or used by the LLM, allowing you to store tool-specific application logic and settings. |
| projectKey | string | yes | The unique identifier for the project containing the AI tool. |
| schema | object | – | A JSON Schema object that defines the tool's input parameters and their constraints for LLM consumption. This schema is used by language models to understand how to invoke the tool correctly. |
| toolKey | string | yes | The unique identifier for the AI tool to be updated. |
No output schema declared.
No examples provided.
update_announcement Update Announcement ~98
Update an existing announcement by applying a series of changes. Specify the announcement to modify using its ID and provide the updates as an array of patch operations.
| Name | Type | Req | Description |
|---|---|---|---|
| announcementId | string | yes | The unique identifier of the announcement to update, provided as a numeric string (e.g., '1234567890'). |
| body | array | yes | An array of patch operations to apply to the announcement. Each operation specifies how to modify the announcement's properties. |
No output schema declared.
No examples provided.
update_application Update Application ~112
Update an application's description and kind fields using JSON Patch format. Specify changes as an array of patch operations following RFC 6902 standard.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | yes | The unique identifier for the application to update. |
| body | array | yes | An array of JSON Patch operations describing the changes to apply. Each operation must include 'op' (the operation type), 'path' (the field to modify), and 'value' (the new value for replace operatio… |
No output schema declared.
No examples provided.
update_application_version Update Application Version ~126
Update an application version using JSON Patch operations. Currently supports updating the `supported` field to enable or disable the version.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | yes | The unique identifier for the application being modified. |
| body | array | yes | A JSON Patch array describing the changes to apply. Each operation must specify an `op` (operation type like 'replace'), `path` (the field to modify), and `value` (the new value). Multiple operations… |
| versionKey | string | yes | The unique identifier for the specific application version to update. |
No output schema declared.
No examples provided.
update_approval_request Update Approval Request ~90
Update an approval request using semantic patch instructions. Supports adding reviewers or updating the request description through a structured instruction format.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the approval request to update. |
| instructions | array | yes | An array of semantic patch instructions to apply. Each instruction specifies an operation (addReviewers or updateDescription) with its required parameters. At least one instruction must be provided. |
No output schema declared.
No examples provided.
update_approval_request_settings_for_project_environment Update Approval Request Settings for Project Environment ~390
Update approval request settings for a specific environment within a project. Configure approval requirements, reviewer permissions, and integration settings for flag change approvals.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | API version identifier. Must be set to 'beta' for this endpoint. |
| autoApplyApprovedChanges | boolean | – | Enable automatic application of changes once all required reviewers have approved them. Only applicable when using third-party approval services. |
| bypassApprovalsForPendingChanges | boolean | – | Skip the approval process for changes that are currently pending review. |
| canApplyDeclinedChanges | boolean | – | Allow applying changes if at least one reviewer has approved, regardless of other reviewers' decisions. |
| canReviewOwnRequest | boolean | – | Permit the person who created an approval request to also approve and apply their own change. |
| environmentKey | string | yes | The environment key that identifies which environment these approval settings apply to. |
| minNumApprovals | string | – | The number of approvals required before a change can be applied. Must be between 1 and 5 inclusive. |
| projectKey | string | yes | The project key that uniquely identifies the project containing the approval settings. |
| required | boolean | – | Whether approval is mandatory for changes in this environment. |
| requiredApprovalTags | array | – | List of flag tags that trigger approval requirements. When specified, only flags with these tags require approval; otherwise all flags require approval. |
| resourceKind | string | yes | The type of resource these approval settings apply to. |
| serviceConfig | object | – | Custom configuration object specific to the approval service being used. |
| serviceKind | string | – | The approval service provider to use for managing approvals (e.g., 'launchdarkly' for native approvals). |
| serviceKindConfigurationId | string | – | Integration configuration ID for a custom approval service. This is an Enterprise-only feature and identifies which custom integration to use. |
No output schema declared.
No examples provided.
update_audit_log_subscription Update Audit Log Subscription ~125
Update an audit log subscription configuration using JSON Patch operations. Specify the changes you want to apply to the subscription settings.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | An array of JSON Patch operations describing the changes to apply. Each operation must include 'op' (the operation type), 'path' (the JSON pointer to the target field), and 'value' (the new value for… |
| id | string | yes | The unique identifier of the audit log subscription to update. |
| integrationKey | string | yes | The unique identifier for the integration containing the audit log subscription. |
No output schema declared.
No examples provided.
update_big_segment_context_targets Update Big Segment Context Targets ~204
Update which contexts are included in or excluded from a big segment. Big segments support larger list-based and synced segments, unlike standard segments which are not supported by this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key that identifies the specific environment within the project. |
| excludedAdd | array | – | Array of context identifiers to add to the segment's excluded list. Order is not significant. |
| excludedRemove | array | – | Array of context identifiers to remove from the segment's excluded list. Order is not significant. |
| includedAdd | array | – | Array of context identifiers to add to the segment's included list. Order is not significant. |
| includedRemove | array | – | Array of context identifiers to remove from the segment's included list. Order is not significant. |
| projectKey | string | yes | The project key that identifies the LaunchDarkly project containing the segment. |
| segmentKey | string | yes | The segment key that uniquely identifies the big segment to update. |
No output schema declared.
No examples provided.
update_big_segment_user_targets Update Big Segment User Targets ~206
Modify user context targets included or excluded in a big segment. Use this operation to add or remove users from list-based or synced segments, which support larger audiences than standard segments.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key that identifies which environment the segment belongs to. |
| excludedAdd | array | – | Array of user context identifiers to add to the segment's excluded targets. Order is not significant. |
| excludedRemove | array | – | Array of user context identifiers to remove from the segment's excluded targets. Order is not significant. |
| includedAdd | array | – | Array of user context identifiers to add to the segment's included targets. Order is not significant. |
| includedRemove | array | – | Array of user context identifiers to remove from the segment's included targets. Order is not significant. |
| projectKey | string | yes | The project key that identifies which project contains the segment. |
| segmentKey | string | yes | The segment key that uniquely identifies the big segment to update. |
No output schema declared.
No examples provided.
update_context_kind Update Context Kind ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Whether the context kind is archived. Archived context kinds cannot be used for targeting. Defaults to false if not specified. |
| key | string | yes | The unique identifier for the context kind to create or update. |
| name | string | yes | The display name for the context kind (e.g., 'organization'). This is the human-readable label used to identify the context kind. |
| projectKey | string | yes | The unique identifier for the project containing the context kind. |
No output schema declared.
No examples provided.
update_custom_role Update Custom Role ~126
Update a custom role using JSON patch or JSON merge patch operations. Supports modifying role policies by specifying the desired changes as a patch document.
| Name | Type | Req | Description |
|---|---|---|---|
| customRoleKey | string | yes | The unique identifier key for the custom role to update. |
| patch | array | yes | An array of JSON patch operations (RFC 6902) or JSON merge patch (RFC 7386) representing the changes to apply. To modify the policy array, use path `/policy` followed by an array index (`/0` for begi… |
No output schema declared.
No examples provided.
update_deployment Update Deployment ~129
Update a deployment's properties using JSON Patch operations. Specify the deployment by ID and provide an array of patch operations to modify its state.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | An array of JSON Patch operations (RFC 6902) describing the changes to apply. Each operation must include `op` (the operation type), `path` (the property to modify), and `value` (the new value for re… |
| deploymentID | string | yes | The unique identifier of the deployment to update. This ID is returned in the `id` field when listing deployments. |
No output schema declared.
No examples provided.
update_destination Update Destination ~138
Update a Data Export destination using JSON patch or JSON merge patch operations. Specify the changes you want to apply to the destination configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | An array of patch operations following RFC 6902 (JSON Patch) or RFC 7386 (JSON Merge Patch) format. Each operation specifies an action (op), target path (path), and new value (value) for the destinat… |
| environmentKey | string | yes | The environment key where the destination is configured. |
| id | string | yes | The unique identifier of the Data Export destination to update. |
| projectKey | string | yes | The project key that contains the destination. |
No output schema declared.
No examples provided.
update_environment Update Environment ~175
Update an environment's configuration using JSON Patch operations. Supports modifying fields including approval settings, comments requirements, and array-based properties.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | A JSON Patch array describing the changes to apply. Each operation specifies an action (op), target path, and value. For array fields, append the index to the path (e.g., `/fieldName/0` to prepend).… |
| environmentKey | string | yes | The environment key that identifies which environment within the project to update. |
| projectKey | string | yes | The project key that identifies which project contains the environment to update. |
No output schema declared.
No examples provided.
update_experiment Update Experiment ~165
Update an experiment using semantic patch instructions. Supports operations like renaming, updating descriptions, managing iterations, and archiving experiments.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the experiment exists. |
| experimentKey | string | yes | The unique identifier for the experiment to update. |
| instructions | array | yes | An array of semantic patch instructions to apply to the experiment. Each instruction is an object with a `kind` field specifying the operation (updateName, updateDescription, startIteration, stopIter… |
| projectKey | string | yes | The unique identifier for the project containing the experiment. |
No output schema declared.
No examples provided.
update_experimentation_settings Update Experimentation Settings ~86
Update the experimentation settings for a project, including the randomization units that are allowed for running experiments.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project whose experimentation settings should be updated. |
| randomizationUnits | array | yes | An array of randomization units that are permitted for experiments in this project. Each unit defines how experiment subjects are randomly assigned to variations. |
No output schema declared.
No examples provided.
update_expiring_context_targets Update Expiring Context Targets ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key where the feature flag targeting applies. A string identifier for the specific environment. |
| featureFlagKey | string | yes | The feature flag key to update expiring targets for. A string identifier for the feature flag. |
| instructions | array | yes | An array of semantic patch instructions to execute. Each instruction must specify a `kind` (addExpiringTarget, updateExpiringTarget, or removeExpiringTarget), the target context via `contextKey` and… |
| projectKey | string | yes | The project key that contains the feature flag. A string identifier for the LaunchDarkly project. |
No output schema declared.
No examples provided.
update_expiring_user_targets_for_segment Update Expiring User Targets for Segment ~187
Update expiration dates for users targeted in a segment using semantic patch instructions. This endpoint manages when LaunchDarkly will automatically remove users from segment targeting.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key where the segment targeting applies. Specifies which environment's user targets should be modified. |
| instructions | array | yes | Array of semantic patch instructions defining the changes to apply. Each instruction must specify a kind (addExpireUserTargetDate, updateExpireUserTargetDate, or removeExpireUserTargetDate), targetTy… |
| projectKey | string | yes | The project key that contains the segment. Used to identify which project's segment to update. |
| segmentKey | string | yes | The segment key identifying which segment's user target expirations to update. |
No output schema declared.
No examples provided.
update_feature_flag Update Feature Flag ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | If true, validates the patch and returns a preview of the flag after changes without persisting them. Useful for testing changes before applying. |
| featureFlagKey | string | yes | The feature flag key used to identify the flag in your application code. |
| ignoreConflicts | boolean | – | If true, applies the patch even if it conflicts with pending scheduled changes or approval requests. Use to override validation checks. |
| patch | array | yes | Array of patch operations describing the changes to apply. Use semantic patch format (with Content-Type header domain-model=launchdarkly.semanticpatch), JSON patch (RFC 6902), or JSON merge patch (RF… |
| projectKey | string | yes | The project key that identifies the LaunchDarkly project containing the feature flag. |
No output schema declared.
No examples provided.
update_flag_defaults_for_project Update Flag Defaults for Project ~340
Set default configuration values for all feature flags created in a project, including naming conventions, targeting behavior, and SDK availability.
| Name | Type | Req | Description |
|---|---|---|---|
| falseDescription | string | yes | A description explaining the purpose or behavior of the false variation, displayed in the LaunchDarkly UI. |
| falseDisplayName | string | yes | The display name shown in the LaunchDarkly UI for the false variation of flags (e.g., 'Off', 'Disabled', 'False'). |
| offVariation | integer | yes | The index (0 or 1) of the variation to serve when flag targeting is disabled. |
| onVariation | integer | yes | The index (0 or 1) of the variation to serve when flag targeting is enabled and no rules match the target. |
| projectKey | string | yes | The unique identifier for the project where flag defaults will be applied. |
| tags | array | yes | A list of default tag labels to automatically assign to each new flag created in this project. Tags help organize and categorize flags. |
| temporary | boolean | yes | Whether newly created flags should be marked as temporary by default, indicating they are intended for short-term use. |
| trueDescription | string | yes | A description explaining the purpose or behavior of the true variation, displayed in the LaunchDarkly UI. |
| trueDisplayName | string | yes | The display name shown in the LaunchDarkly UI for the true variation of flags (e.g., 'On', 'Enabled', 'True'). |
| usingEnvironmentId | boolean | yes | Whether flags should be available to client-side SDKs by default. |
| usingMobileKey | boolean | yes | Whether flags should be available to mobile SDKs by default. |
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 container image (ghcr.io/mcparmory/launchdarkly:1.0.4).
Is the com.mcparmory/launchdarkly MCP server safe to use?
com.mcparmory/launchdarkly scores 49 out of 100 on VerifyMCP. 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.