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 →
delete_application_version Delete Application Version ~66
Permanently delete a specific version of an application. This operation removes the version and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | yes | The unique identifier for the application containing the version to delete. |
| versionKey | string | yes | The unique identifier for the specific application version to delete. |
No output schema declared.
No examples provided.
delete_approval_request Delete Approval Request ~42
Permanently delete an approval request by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the approval request to delete. |
No output schema declared.
No examples provided.
delete_approval_request_for_flag Delete Approval Request for Flag ~116
Delete a pending approval request for a feature flag in a specific environment. This removes the approval workflow, preventing further review or approval actions on the request.
| 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 associated with the approval request. |
| id | string | yes | The unique identifier of the approval request to delete. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
delete_audit_log_subscription Delete Audit Log Subscription ~73
Remove an audit log subscription from an integration. This permanently deletes the subscription and stops audit log collection for the specified integration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the audit log subscription to delete. |
| integrationKey | string | yes | The unique identifier for the integration from which the subscription will be deleted. |
No output schema declared.
No examples provided.
delete_branches Delete Branches ~79
Asynchronously delete multiple branches from a repository. Returns a task that processes the branch deletions in the background.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | An array of branch names to delete. Each item should be a string representing a branch name. Order is not significant. |
| repo | string | yes | The name of the repository from which branches will be deleted. |
No output schema declared.
No examples provided.
delete_context_instance Delete Context Instance ~93
Delete a specific context instance by its ID within a project environment. This operation permanently removes the context instance and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project where the context instance is located. |
| id | string | yes | The unique identifier of the context instance to delete. |
| projectKey | string | yes | The unique identifier for the project containing the context instance to delete. |
No output schema declared.
No examples provided.
delete_custom_role Delete Custom Role ~65
Permanently delete a custom role by its unique key. This action removes the role and any associated permissions from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| customRoleKey | string | yes | The unique identifier for the custom role to delete. This is a string value that uniquely identifies the role within the system. |
No output schema declared.
No examples provided.
delete_destination Delete Destination ~85
Permanently delete a Data Export destination from a specific project and environment. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project where the destination exists. |
| id | string | yes | The unique identifier of the Data Export destination to delete. |
| projectKey | string | yes | The unique identifier for the project containing the destination to delete. |
No output schema declared.
No examples provided.
delete_environment Delete Environment ~61
Permanently delete an environment from a project by its key. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment to delete. |
| projectKey | string | yes | The unique identifier for the project containing the environment to delete. |
No output schema declared.
No examples provided.
delete_feature_flag Delete Feature Flag ~92
Permanently delete a feature flag across all environments. This operation cannot be undone, so only use it for flags your application no longer references in code.
| Name | Type | Req | Description |
|---|---|---|---|
| featureFlagKey | string | yes | The unique key that identifies the feature flag in your codebase. This is the identifier you reference when evaluating the flag in your application. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
delete_insight_group Delete Insight Group ~65
Permanently delete an insight group by its unique key. This operation removes the insight group and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| insightGroupKey | string | yes | The unique identifier for the insight group to delete. This is a string value that uniquely identifies the insight group within the system. |
No output schema declared.
No examples provided.
delete_member Delete Member ~45
Remove an account member by their ID. This operation will fail if SCIM provisioning is enabled for the account.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the member to delete |
No output schema declared.
No examples provided.
delete_metric Delete Metric ~65
Permanently delete a metric from a project by its key. This operation removes the metric and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| metricKey | string | yes | The unique identifier for the metric to delete. |
| projectKey | string | yes | The unique identifier for the project containing the metric to delete. |
No output schema declared.
No examples provided.
delete_metric_group Delete Metric Group ~66
Permanently delete a metric group from a project by its key. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| metricGroupKey | string | yes | The unique identifier for the metric group to delete. |
| projectKey | string | yes | The unique identifier for the project containing the metric group to delete. |
No output schema declared.
No examples provided.
delete_model_config Delete Model Config ~84
Permanently delete an AI model configuration from a project. This operation removes the specified model config and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| modelConfigKey | string | yes | The unique identifier of the AI model configuration to delete. |
| projectKey | string | yes | The unique identifier of the project containing the model config. Use 'default' for the default project or specify a custom project key. |
No output schema declared.
No examples provided.
delete_oauth_client Delete OAuth Client ~62
Permanently delete an OAuth 2.0 client application by its unique identifier. This action cannot be undone and will invalidate all tokens issued to this client.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | The unique identifier of the OAuth 2.0 client to delete. |
No output schema declared.
No examples provided.
delete_project Delete Project ~71
Permanently delete a project and all its associated environments and feature flags. This operation cannot be undone and will fail if the project is the last one in the account.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project to delete. This is a string value that uniquely identifies the project within your account. |
No output schema declared.
No examples provided.
delete_prompt_snippet Delete Prompt Snippet ~71
Delete an existing prompt snippet from a project's AI configuration. This operation permanently removes the specified prompt snippet and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier of the project containing the prompt snippet to delete. |
| snippetKey | string | yes | The unique identifier of the prompt snippet to delete. |
No output schema declared.
No examples provided.
delete_relay_auto_config Delete Relay Auto Config ~67
Delete a Relay Proxy auto-configuration by its unique identifier. This operation permanently removes the specified relay auto config from your account.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the relay auto config to delete. This is a string value that uniquely identifies the configuration within your account. |
No output schema declared.
No examples provided.
delete_release_for_flag Delete Release for Flag ~95
Removes a release associated with a feature flag. This operation permanently deletes the release record from the specified flag within a project.
| Name | Type | Req | Description |
|---|---|---|---|
| flagKey | string | yes | The unique identifier for the feature flag from which the release will be deleted. Must correspond to an existing flag within the specified project. |
| projectKey | string | yes | The unique identifier for the project containing the flag. Used to scope the operation to the correct project context. |
No output schema declared.
No examples provided.
delete_release_pipeline Delete Release Pipeline ~79
Deletes a release pipeline from a project. Note that the default release pipeline cannot be deleted; if you need to remove it, first create and set a different pipeline as default.
| Name | Type | Req | Description |
|---|---|---|---|
| pipelineKey | string | yes | The unique identifier for the release pipeline to delete. |
| projectKey | string | yes | The unique identifier for the project containing the release pipeline. |
No output schema declared.
No examples provided.
delete_release_policy Delete Release Policy ~106
Permanently delete a release policy from a project. This action cannot be undone and will remove all associated policy configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this operation. Must be set to 'beta'. |
| policyKey | string | yes | The human-readable identifier for the release policy to delete (e.g., 'production-release'). |
| projectKey | string | yes | The unique identifier for the project containing the release policy (e.g., 'default'). |
No output schema declared.
No examples provided.
delete_repository Delete Repository ~46
Permanently delete a repository and all associated code references. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | The name of the repository to delete. Must be a valid string identifier. |
No output schema declared.
No examples provided.
delete_scheduled_flag_changes Delete Scheduled Flag Changes ~127
Delete a scheduled changes workflow for a feature flag in a specific environment. This removes the pending scheduled changes and cancels any automation associated with the workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key specifying which environment's scheduled changes workflow should be removed. |
| featureFlagKey | string | yes | The feature flag key identifying which flag's scheduled changes should be deleted. |
| id | string | yes | The unique identifier of the scheduled changes workflow to delete. |
| projectKey | string | yes | The project key that contains the feature flag. Used to scope the operation to a specific project. |
No output schema declared.
No examples provided.
delete_segment Delete Segment ~82
Permanently delete a segment from a specific project and environment. This action cannot be undone.
| 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 project containing the segment to delete. |
| segmentKey | string | yes | The unique identifier for the segment to delete. |
No output schema declared.
No examples provided.
delete_team Delete Team ~67
Permanently delete a team by its key. This action cannot be undone and will remove the team from your LaunchDarkly account.
| Name | Type | Req | Description |
|---|---|---|---|
| teamKey | string | yes | The unique identifier for the team to delete. This is a string value that uniquely identifies the team within your LaunchDarkly organization. |
No output schema declared.
No examples provided.
delete_token Delete Token ~63
Permanently delete an access token by its ID. This operation removes the token immediately, invalidating any authentication attempts using it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the access token to delete. This is a string value that uniquely identifies the token in the system. |
No output schema declared.
No examples provided.
delete_trigger_for_flag Delete Trigger for Flag ~109
Delete a specific flag trigger by its ID. This removes the trigger configuration that automates flag state changes based on defined conditions.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the flag trigger is configured. |
| featureFlagKey | string | yes | The unique identifier for the feature flag associated with this trigger. |
| id | string | yes | The unique identifier of the flag trigger to delete. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
delete_view Delete View ~131
Permanently delete a specific view from a project by its key. This operation removes the view and 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' for this endpoint. |
| projectKey | string | yes | The unique identifier of the project containing the view. Use the project key (e.g., 'default') to specify which project to access. |
| viewKey | string | yes | The unique identifier of the view to delete. Specify the view key (e.g., 'my-view') to target the exact view for deletion. |
No output schema declared.
No examples provided.
delete_view_resource_links Delete View Resource Links ~171
Remove one or multiple linked resources (feature flags or segments) from a view. Specify the resource type and provide the identifiers to unlink.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | API version identifier. Must be set to 'beta' for this endpoint. |
| body | – | yes | Request body containing the resource identifiers to unlink. For flags, provide flag keys; for segments, provide segment IDs. |
| projectKey | string | yes | The project key that contains the view. Use the project identifier (e.g., 'default'). |
| resourceType | string | yes | The type of resource to unlink: either 'flags' for feature flags or 'segments' for audience segments. |
| viewKey | string | yes | The view key from which to unlink resources. Use the view identifier (e.g., 'my-view'). |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~68
Permanently delete a webhook by its ID. This action cannot be undone and will stop all event notifications from being sent to the webhook's configured endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the webhook to delete. This is a string value that uniquely identifies the webhook in the system. |
No output schema declared.
No examples provided.
delete_workflow Delete Workflow ~106
Remove a workflow from a feature flag in a specific environment. This permanently deletes the workflow and its associated configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the workflow is configured. |
| featureFlagKey | string | yes | The unique identifier for the feature flag that contains the workflow to delete. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
| workflowId | string | yes | The unique identifier for the workflow to delete. |
No output schema declared.
No examples provided.
evaluate_context_instance_segment_memberships Evaluate Context Instance Segment Memberships ~169
Evaluate which segments a context instance belongs to based on its attributes. Provide a context instance with its key, kind, and custom attributes to retrieve membership status across all segments in the environment.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | The context instance to evaluate. Must include a unique key identifier, a kind (e.g., 'user', 'organization'), and any custom attributes relevant to segment rules (e.g., name, jobFunction, address).… |
| environmentKey | string | yes | The environment key that identifies the specific environment within the project. This determines which segment definitions and rules are evaluated. |
| projectKey | string | yes | The project key that identifies the LaunchDarkly project. This is a string identifier used to scope the operation within your workspace. |
No output schema declared.
No examples provided.
generate_warehouse_destination_key_pair Generate Warehouse Destination Key Pair ~82
Generate a public-private key pair for authenticating Data Export operations to a Snowflake warehouse destination. This enables secure credential-based access without storing passwords.
| Name | Type | Req | Description |
|---|---|---|---|
| envKey | string | yes | The unique identifier for the environment within the project where the warehouse destination is configured. |
| projKey | string | yes | The unique identifier for the project containing the destination configuration. |
No output schema declared.
No examples provided.
get_agent_graph Get Agent Graph ~87
Retrieve a specific agent graph by its key, including all its edges and configuration details.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Currently only the beta version is supported. |
| graphKey | string | yes | The unique identifier for the agent graph to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the agent graph. |
No output schema declared.
No examples provided.
get_agent_optimization Get Agent Optimization ~73
Retrieve a specific agent optimization configuration by its unique key within a project. Use this to inspect the details and settings of an existing optimization.
| Name | Type | Req | Description |
|---|---|---|---|
| optimizationKey | string | yes | The unique identifier for the specific agent optimization to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the agent optimization. |
No output schema declared.
No examples provided.
get_ai_config Get AI Config ~74
Retrieve a specific AI configuration by its project and configuration keys. Use this to fetch detailed settings and properties for a particular AI config within a project.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the specific AI configuration to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the AI configuration. |
No output schema declared.
No examples provided.
get_ai_config_metrics Get AI Config Metrics ~179
Retrieve usage and performance metrics for a specific AI Config within a defined time range and environment. Metrics are aggregated for the specified period to help monitor AI Config performance and usage patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config whose metrics should be retrieved. |
| env | string | yes | The environment key to filter metrics by. Only metrics collected in this specific environment will be included in the results. |
| from | integer | yes | The start of the metrics time range as milliseconds since epoch (inclusive). Use this to define the beginning of your analysis period. |
| projectKey | string | yes | The unique identifier for the project containing the AI Config. |
| to | integer | yes | The end of the metrics time range as milliseconds since epoch (exclusive). The time range between `from` and `to` cannot exceed 100 days. |
No output schema declared.
No examples provided.
get_ai_config_metrics_by_variation Get AI Config Metrics by Variation ~159
Retrieve usage and performance metrics for an AI Config segmented by variation. Results are filtered to a specific time range and environment.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config whose metrics you want to retrieve. |
| env | string | yes | The environment key to filter metrics. Only metrics from this specific environment will be included in the results. |
| from | integer | yes | The start of the time range for metrics, specified as milliseconds since epoch (inclusive). |
| projectKey | string | yes | The unique identifier for the project containing the AI Config. |
| to | integer | yes | The end of the time range for metrics, specified as milliseconds since epoch (exclusive). The time range cannot span more than 100 days. |
No output schema declared.
No examples provided.
get_ai_config_quick_stats Get AI Config Quick Stats ~99
Retrieve aggregate quick statistics for AI Configs within a specific project and environment. Returns metrics summarizing AI Config usage and performance for the specified environment.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | yes | The environment key that filters which metrics are included in the results. Only statistics from this specific environment will be returned. |
| projectKey | string | yes | The unique identifier for the project containing the AI Configs. This key determines which project's statistics will be retrieved. |
No output schema declared.
No examples provided.
get_ai_config_targeting Get AI Config Targeting ~78
Retrieve the targeting configuration for a specific AI Config. Returns the targeting rules and criteria that determine which users or contexts this AI Config applies to.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config whose targeting configuration should be retrieved. |
| projectKey | string | yes | The unique identifier for the project containing the AI Config. |
No output schema declared.
No examples provided.
get_ai_config_variation Get AI Config Variation ~111
Retrieve a specific AI Config variation by its key, including all versions associated with that variation.
| Name | Type | Req | Description |
|---|---|---|---|
| configKey | string | yes | The unique identifier for the AI Config within the project. Use 'default' for the default configuration. |
| projectKey | string | yes | The unique identifier for the project containing the AI Config. Use 'default' for the default project. |
| variationKey | string | yes | The unique identifier for the specific variation within the AI Config. Use 'default' for the default variation. |
No output schema declared.
No examples provided.
get_ai_tool Get AI Tool ~72
Retrieve a specific AI tool by its project and tool identifiers. Use this operation to fetch detailed information about a configured AI tool within a project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project containing the AI tool. |
| toolKey | string | yes | The unique identifier for the AI tool to retrieve. |
No output schema declared.
No examples provided.
get_application Get Application ~65
Retrieve a LaunchDarkly application by its unique application key. Optionally expand the response to include evaluated flags and other application details.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | yes | The unique identifier for the application. This is a string value that uniquely identifies the application within your LaunchDarkly workspace. |
No output schema declared.
No examples provided.
get_approval_request Get Approval Request ~56
Retrieve a specific approval request by its ID. Optionally expand the response to include related resources such as environments, flags, projects, or resource details.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the approval request to retrieve. |
No output schema declared.
No examples provided.
get_approval_request_for_flag Get Approval Request for Flag ~117
Retrieve a specific approval request for a feature flag in a given environment. Use this to check the status and details of a pending or completed approval workflow.
| 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 associated with this approval request. |
| id | string | yes | The unique identifier for the specific approval request to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
get_audit_log_entry Get Audit Log Entry ~64
Retrieve a detailed audit log entry with full change history. Returns comprehensive metadata including the previous and current versions of the modified entity, plus the JSON patch or semantic patch that was applied.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the audit log entry to retrieve. |
No output schema declared.
No examples provided.
get_audit_log_subscription Get Audit Log Subscription ~78
Retrieve a specific audit log subscription by its ID within a given integration. Use this to fetch details about an existing subscription configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the audit log subscription to retrieve. |
| integrationKey | string | yes | The unique identifier for the integration. This key determines which integration context the subscription belongs to. |
No output schema declared.
No examples provided.
get_big_segment_export Get Big Segment Export ~115
Retrieve the status and details of a big segment export process for a synced or list-based segment containing more than 15,000 entries.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project where the segment is defined. |
| exportID | string | yes | The unique identifier for the specific export process to retrieve information about. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the segment. |
| segmentKey | string | yes | The unique identifier for the segment being exported. |
No output schema declared.
No examples provided.
get_big_segment_import Get Big Segment Import ~124
Retrieve detailed information about an in-progress or completed big segment import process. Big segments support list-based imports with more than 15,000 entries.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key that identifies which environment contains the segment being imported. |
| importID | string | yes | The import ID that uniquely identifies the specific import process to retrieve status and details for. |
| projectKey | string | yes | The project key that identifies which project contains the segment being imported. |
| segmentKey | string | yes | The segment key that identifies the specific big segment associated with this import. |
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.