com.mcparmory/launchdarkly
PYPI · MCPARMORY-LAUNCHDARKLY · 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 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 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 Management90
- Stability observed for 27 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 21 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 →
get_branch Get Branch ~89
Retrieve detailed information about a specific branch within a repository, optionally filtered to a particular project.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | The name of the branch to retrieve, URL-encoded to handle special characters in branch names. |
| projKey | string | – | Optional project key to scope the branch lookup to a specific project within the repository. |
| repo | string | yes | The name of the repository containing the branch. |
No output schema declared.
No examples provided.
get_caller_identity Get Caller Identity ~40
Retrieve information about the identity used to authenticate the current API request, including details about the session cookie, API token, SDK keys, or other credentials.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_code_references_statistics Get Code References Statistics ~76
Retrieve code reference statistics for flags in a project, showing the number of references to flag keys across repositories in the default branch. Optionally filter results to a single flag using the flagKey query parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. Used to scope the statistics query to a specific project. |
No output schema declared.
No examples provided.
get_context Get Context ~139
Retrieve a specific context by its kind and key within a project environment. Contexts are used to segment user data and targeting rules.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project. |
| includeTotalCount | boolean | – | Whether to include the total count of matching contexts in the response. Defaults to true if not specified. |
| key | string | yes | The unique identifier for the specific context instance within its kind. |
| kind | string | yes | The category or type of context (e.g., 'user', 'organization', 'device'). |
| projectKey | string | yes | The unique identifier for the project containing the context. |
No output schema declared.
No examples provided.
get_context_attribute_values Get Context Attribute Values ~103
Retrieve all values associated with a specific context attribute within a project environment. Use this to discover what values have been recorded or are available for a given attribute name.
| Name | Type | Req | Description |
|---|---|---|---|
| attributeName | string | yes | The name of the context attribute for which to retrieve values. |
| environmentKey | string | yes | The unique identifier for the environment within the project where the context attribute values are stored. |
| projectKey | string | yes | The unique identifier for the project containing the context attribute. |
No output schema declared.
No examples provided.
get_context_instance Get Context Instance ~112
Retrieve a specific context instance by its ID within a project and environment. Returns detailed information about the context instance configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project. |
| id | string | yes | The unique identifier of the context instance to retrieve. |
| includeTotalCount | boolean | – | Whether to include the total count of matching context instances in the response. Defaults to true if not specified. |
| projectKey | string | yes | The unique identifier for the project containing the context instance. |
No output schema declared.
No examples provided.
get_custom_role Get Custom Role ~63
Retrieve a single custom role by its unique key or ID. Use this to fetch detailed information about a specific custom role in your organization.
| Name | Type | Req | Description |
|---|---|---|---|
| customRoleKey | string | yes | The unique identifier for the custom role, specified as either the custom role key or its ID. |
No output schema declared.
No examples provided.
get_custom_workflow Get Custom Workflow ~113
Retrieve a specific custom workflow by its ID within a feature flag's environment. Use this to inspect workflow configuration, status, and details.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which the workflow operates. |
| featureFlagKey | string | yes | The unique identifier for the feature flag that contains the workflow. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag and workflow. |
| workflowId | string | yes | The unique identifier of the specific workflow to retrieve. |
No output schema declared.
No examples provided.
get_deployment Get Deployment ~61
Retrieve a specific deployment by its ID. Optionally expand the response to include associated pull requests and flag references.
| Name | Type | Req | Description |
|---|---|---|---|
| deploymentID | string | yes | The unique identifier of the deployment to retrieve. This ID is provided in the `id` field when listing deployments. |
No output schema declared.
No examples provided.
get_deployment_frequency_chart Get Deployment Frequency Chart ~273
Retrieve deployment frequency chart data for engineering insights, showing how often deployments occur across your infrastructure. Optionally expand the response to include detailed metrics related to deployment frequency.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Comma-separated list of application keys to filter deployment frequency data across multiple applications. |
| bucketMs | string | – | Duration of intervals for the x-axis in milliseconds. Defaults to one day (86400000 milliseconds). Adjust to control granularity of the chart data. |
| bucketType | string | – | Type of time bucket for aggregating data: `rolling` (continuous window), `hour` (hourly intervals), or `day` (daily intervals). Defaults to `rolling`. |
| environmentKey | string | – | The environment key to filter deployment frequency data for a specific environment. |
| from | string | – | Start of the time range as a Unix timestamp in milliseconds. Defaults to 7 days ago if not specified. |
| groupBy | string | – | Dimension to group deployment frequency data by: `application` (per application) or `kind` (by deployment type). |
| projectKey | string | – | The project key to filter deployment frequency data for a specific project. |
| to | string | – | End of the time range as a Unix timestamp in milliseconds. Defaults to the current time if not specified. |
No output schema declared.
No examples provided.
get_destination Get Destination ~80
Retrieve a single Data Export destination by its ID within a specific project and environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key that identifies which environment within the project contains the destination. |
| id | string | yes | The unique identifier of the Data Export destination to retrieve. |
| projectKey | string | yes | The project key that identifies which project contains the destination. |
No output schema declared.
No examples provided.
get_environment Get Environment ~62
Retrieve a specific environment within a project. Returns environment configuration including approval settings when the approvals feature is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the environment. |
No output schema declared.
No examples provided.
get_events_usage_by_type Get Events Usage by Type ~168
Retrieve time-series data showing how many times a flag was evaluated and which variation resulted from each evaluation. Data granularity automatically adjusts based on age: minutely for the past 2 hours, hourly for the past 2 days, and daily for older data.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO 8601 timestamp marking the start of the requested data range. If not provided, defaults to 24 hours before the 'to' timestamp. |
| to | string | – | ISO 8601 timestamp marking the end of the requested data range. If not provided, defaults to the current time. |
| type | string | yes | The event category to retrieve usage data for. Must be either 'received' (events received by the system) or 'published' (events published by the system). |
No output schema declared.
No examples provided.
get_experiment Get Experiment ~128
Retrieve detailed information about a specific experiment in a LaunchDarkly project environment. Optionally expand the response to include iterations, metrics, treatments, and analysis configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the experiment is running. |
| experimentKey | string | yes | The unique identifier for the experiment to retrieve. Use the optional `expand` query parameter to include additional fields such as previousIterations, draftIteration, secondaryMetrics, treatments,… |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the experiment. |
No output schema declared.
No examples provided.
get_experimentation_settings Get Experimentation Settings ~52
Retrieve the current experimentation settings configured for a specific project. This includes all active experimentation policies and configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project whose experimentation settings you want to retrieve. |
No output schema declared.
No examples provided.
get_feature_flag Get Feature Flag ~113
Retrieve a single feature flag by its key, with configurations for all environments by default. Use the `env` parameter to filter results to specific environments for faster responses and smaller payloads.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | Optional environment filter to restrict returned configurations to a specific environment (e.g., 'production'). Omit to retrieve all environments. |
| featureFlagKey | string | yes | The unique identifier for the feature flag to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
get_feature_flag_status Get Feature Flag Status ~103
Retrieve the current status of a specific feature flag within a given project and environment. This includes whether the flag is enabled or disabled and any associated targeting rules.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which to check the feature flag status. |
| featureFlagKey | string | yes | The unique identifier for the feature flag whose status you want to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
get_feature_flag_status_across_environments Get Feature Flag Status Across Environments ~155
Retrieve the current status and configuration of a feature flag across all environments or a specific environment. Use this to check whether a flag is enabled, its targeting rules, and rollout percentages in your deployment pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | Optional filter to retrieve flag status for a specific environment only. If omitted, the response includes status across all environments in the project. |
| featureFlagKey | string | yes | The unique identifier for the specific feature flag whose status you want to retrieve. This is a required string key that identifies the flag within the project. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. This is a required string key that identifies which project's flags to query. |
No output schema declared.
No examples provided.
get_flag_defaults_for_project Get Flag Defaults for Project ~64
Retrieve the default flag settings configured for a specific project. These defaults apply to feature flags within the project unless overridden at a more granular level.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. Used to scope the flag defaults to a specific project. |
No output schema declared.
No examples provided.
get_flag_status_chart Get Flag Status Chart ~104
Retrieve flag status chart data for a specific project and environment, optionally filtered by applications. This provides observability into flag health and status distribution across your infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Optional comma-separated list of application keys to filter the flag status data to specific applications. |
| environmentKey | string | yes | The environment key that specifies which environment's flag statuses to chart. |
| projectKey | string | yes | The project key that identifies which project's flag data to retrieve. |
No output schema declared.
No examples provided.
get_insight_group Get Insight Group ~53
Retrieve a specific insight group by its key, with optional expansion to include scoring details and environment associations used in engineering insights metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| insightGroupKey | string | yes | The unique identifier for the insight group to retrieve. |
No output schema declared.
No examples provided.
get_insights_scores Get Insights Scores ~126
Retrieve engineering insights scores for a specified project and environment, optionally filtered by one or more applications. This data powers engineering insights metrics dashboards and performance analysis views.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Optional comma-separated list of application identifiers to filter insights scores to specific applications. When omitted, scores for all applications in the environment are returned. |
| environmentKey | string | yes | The unique identifier for the environment within the project. Required to retrieve environment-specific insight metrics. |
| projectKey | string | yes | The unique identifier for the project. Required to scope the insights scores to a specific project. |
No output schema declared.
No examples provided.
get_lead_time_chart Get Lead Time Chart ~287
Retrieve lead time chart data for engineering insights, showing deployment frequency metrics across specified time periods and grouping dimensions.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Optional comma-separated list of application keys to filter the chart data to specific applications. |
| bucketMs | string | – | Optional duration in milliseconds for each interval on the x-axis. Defaults to one day (86400000 milliseconds). Only applies when bucketType is `hour` or `day`. |
| bucketType | string | – | Optional bucket type for aggregating data points. Choose from: `rolling` (continuous window), `hour` (hourly intervals), or `day` (daily intervals). Defaults to `rolling`. |
| environmentKey | string | – | Optional environment key to filter lead time data to a specific environment within the project. |
| from | string | – | Optional Unix timestamp in milliseconds marking the start of the time range. Defaults to 7 days before the end time if not specified. |
| groupBy | string | – | Optional dimension for grouping chart data. Choose from: `application` (group by application) or `stage` (group by deployment stage). Defaults to `stage`. |
| projectKey | string | yes | The project key that identifies which project's lead time data to retrieve. |
| to | string | – | Optional Unix timestamp in milliseconds marking the end of the time range. Defaults to the current time if not specified. |
No output schema declared.
No examples provided.
get_member Get Member ~81
Retrieve a single account member by ID. Use the reserved value `me` to get the caller's own member information. Optionally expand the response to include custom role details and role attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The member ID as a string. Use the reserved value `me` to retrieve the caller's own member information instead of specifying a numeric ID. |
No output schema declared.
No examples provided.
get_metric Get Metric ~123
Retrieve detailed information about a specific metric in a LaunchDarkly project. Optionally expand the response to include related experiments and metric groups.
| Name | Type | Req | Description |
|---|---|---|---|
| metricKey | string | yes | The unique identifier for the metric to retrieve. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the metric. |
| versionId | string | – | The specific version ID of the metric to retrieve. If omitted, returns the current version. Use comma-separated values in the expand query parameter to include experiments, experimentCount, metricGro… |
No output schema declared.
No examples provided.
get_metric_group Get Metric Group ~70
Retrieve detailed information about a specific metric group within a project. Optionally expand the response to include associated experiments or experiment counts.
| Name | Type | Req | Description |
|---|---|---|---|
| metricGroupKey | string | yes | The unique identifier for the metric group to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the metric group. |
No output schema declared.
No examples provided.
get_migration_safety_issues Get Migration Safety Issues ~143
Analyzes a feature flag patch and returns any migration safety issues that would result from applying those changes. Use this to validate flag modifications before deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which the flag changes would be applied. |
| flagKey | string | yes | The unique identifier for the feature flag being evaluated for migration safety. |
| instructions | array | yes | An array of semantic patch instructions that describe the flag modifications to evaluate. Use the same instruction format as standard flag update operations. Order matters—instructions are applied se… |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
get_model_config Get Model Config ~92
Retrieve a specific AI model configuration by its unique key within a project. Use this to fetch detailed settings and parameters for a configured AI model.
| Name | Type | Req | Description |
|---|---|---|---|
| modelConfigKey | string | yes | The unique identifier for the AI model configuration to retrieve. Typically 'default' for the standard model configuration. |
| projectKey | string | yes | The unique identifier for the project containing the model configuration. Typically 'default' for standard projects. |
No output schema declared.
No examples provided.
get_oauth_client_by_id Get OAuth Client by ID ~63
Retrieve a registered OAuth 2.0 client by its unique client ID. Use this to fetch detailed configuration and metadata for a specific OAuth client application.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | The unique identifier of the OAuth 2.0 client to retrieve. |
No output schema declared.
No examples provided.
get_project Get Project ~51
Retrieve a single project by its key. Optionally expand the response to include related resources such as environments.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. Used to specify which project to retrieve. |
No output schema declared.
No examples provided.
get_prompt_snippet Get Prompt Snippet ~76
Retrieve a specific prompt snippet by its unique key within a project. Use this to fetch the full details of a saved prompt snippet for use in AI configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project containing the prompt snippet. |
| snippetKey | string | yes | The unique identifier for the prompt snippet to retrieve. |
No output schema declared.
No examples provided.
get_relay_proxy_config Get Relay Proxy Config ~53
Retrieve a single Relay Proxy auto configuration by its unique identifier. Use this to fetch detailed settings for a specific relay proxy configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the relay auto config to retrieve. |
No output schema declared.
No examples provided.
get_release_by_flag_key Get Release by Flag Key ~70
Retrieve the currently active release associated with a specific feature flag. Returns release metadata if an active release exists for the flag.
| Name | Type | Req | Description |
|---|---|---|---|
| flagKey | string | yes | The unique identifier for the feature flag within the project. |
| projectKey | string | yes | The unique identifier for the project containing the flag. |
No output schema declared.
No examples provided.
get_release_frequency_chart Get Release Frequency Chart ~354
Retrieve release frequency chart data for a project and environment, with optional filtering by application, experiment association, and time range. Results can be grouped by impact and bucketed into time intervals for visualization.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Comma-separated list of application keys to filter results to specific applications. Omit to include all applications. |
| bucketMs | string | – | Duration of each time interval bucket in milliseconds. Defaults to one day (86400000 milliseconds). Only applies when bucketType is not 'rolling'. |
| bucketType | string | – | Time interval bucketing strategy: 'rolling' for continuous aggregation, 'hour' for hourly buckets, or 'day' for daily buckets. Defaults to 'rolling'. |
| environmentKey | string | yes | The environment key that identifies which environment's release data to retrieve. |
| from | string | – | Start of the time range as a Unix timestamp in milliseconds. Defaults to 7 days before the 'to' timestamp if not specified. |
| global | string | – | Filter to include or exclude global events. Use 'include' to show global events or 'exclude' to hide them. Defaults to 'include'. |
| groupBy | string | – | Group results by a property such as 'impact' to organize the chart data. Omit for ungrouped results. |
| hasExperiments | boolean | – | Filter results to releases associated with experiments (true) or releases without experiments (false). Omit to include all releases regardless of experiment association. |
| projectKey | string | yes | The project key that identifies which project's release data to retrieve. |
| to | string | – | End of the time range as a Unix timestamp in milliseconds. Defaults to the current time if not specified. |
No output schema declared.
No examples provided.
get_release_pipeline_by_key Get Release Pipeline by Key ~70
Retrieve a specific release pipeline within a project using its unique key identifier. This operation returns the complete pipeline configuration and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| pipelineKey | string | yes | The unique identifier for the release pipeline to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the release pipeline. |
No output schema declared.
No examples provided.
get_release_policy Get Release Policy ~128
Retrieve a specific release policy by its key within a project. Use this to fetch detailed configuration and settings for a named release policy.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Must be set to 'beta' to access this endpoint. |
| policyKey | string | yes | The unique identifier for the release policy within the project (e.g., 'production-release'). This specifies which policy to retrieve. |
| projectKey | string | yes | The unique identifier for the project (e.g., 'default'). This scopes the release policy lookup to a specific project. |
No output schema declared.
No examples provided.
get_repository Get Repository ~60
Retrieve a single repository by its name. Use this to fetch detailed information about a specific code repository tracked in the system.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | The name of the repository to retrieve. This is a string identifier that uniquely identifies the repository within the system. |
No output schema declared.
No examples provided.
get_scheduled_change_for_feature_flag Get Scheduled Change for Feature Flag ~122
Retrieve a specific scheduled change that will be applied to a feature flag in a given environment. Use this to inspect the details of a pending flag modification by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the scheduled change will be applied. |
| featureFlagKey | string | yes | The unique identifier for the feature flag associated with the scheduled change. |
| id | string | yes | The unique identifier for the scheduled change to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
get_segment Get Segment ~93
Retrieve a single segment by its key. Segments can be rule-based, list-based, or synced; big segments include larger list-based and synced segments with additional metadata fields.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project. |
| projectKey | string | yes | The unique identifier for the project containing the segment. |
| segmentKey | string | yes | The unique identifier for the segment to retrieve. |
No output schema declared.
No examples provided.
get_segment_membership_for_context Get Segment Membership for Context ~122
Check whether a specific context is included or excluded from a big segment. Big segments support larger list-based and synced segments, but not standard segments.
| Name | Type | Req | Description |
|---|---|---|---|
| contextKey | string | yes | The context key that identifies the specific context whose membership status you want to retrieve. |
| environmentKey | string | yes | The environment key that identifies which environment to query for segment membership. |
| projectKey | string | yes | The project key that identifies which project contains the segment. |
| segmentKey | string | yes | The segment key that identifies the big segment to check membership against. |
No output schema declared.
No examples provided.
get_stale_flags_chart Get Stale Flags Chart ~146
Retrieve stale flags chart data for engineering insights, showing flag health metrics across a project and environment. Optionally expand the response to include detailed metrics and group results by maintainer.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Optional comma-separated list of application keys to filter stale flags data to specific applications. |
| environmentKey | string | yes | The environment key that identifies which environment within the project to retrieve stale flags data for. |
| groupBy | string | – | Optional property to group the stale flags results by. Currently supports grouping by maintainer to organize flags by their responsible team members. |
| projectKey | string | yes | The project key that identifies which project to retrieve stale flags data for. |
No output schema declared.
No examples provided.
get_team Get Team ~60
Retrieve a team by its unique key. Optionally expand the response to include members, roles, role attributes, projects, or maintainers.
| Name | Type | Req | Description |
|---|---|---|---|
| teamKey | string | yes | The unique identifier for the team. Use this key to fetch the specific team's details. |
No output schema declared.
No examples provided.
get_token Get Token ~49
Retrieve a single access token by its unique identifier. Use this to fetch details about a specific token for inspection or validation purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the access token to retrieve. |
No output schema declared.
No examples provided.
get_trigger_workflow_by_id Get Trigger Workflow by ID ~121
Retrieve a specific flag trigger by its ID within a feature flag, project, and environment context. Use this to fetch detailed configuration and status of an individual trigger workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which the trigger operates. |
| featureFlagKey | string | yes | The unique identifier for the feature flag that contains the trigger. |
| id | string | yes | The unique identifier of the specific flag trigger to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag and trigger. |
No output schema declared.
No examples provided.
get_user_segment_membership Get User Segment Membership ~102
Check whether a user is included or excluded from a big segment. This operation only works with big segments, not standard segments.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key where the segment membership is evaluated. |
| projectKey | string | yes | The project key that contains the segment. |
| segmentKey | string | yes | The big segment key to check membership for. |
| userKey | string | yes | The user key to check for membership in the segment. |
No output schema declared.
No examples provided.
get_view Get View ~101
Retrieve a specific view by its project and view keys. Returns the view configuration and metadata for the specified view.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Must be set to 'beta'. |
| projectKey | string | yes | The unique identifier for the project containing the view (e.g., 'default'). |
| viewKey | string | yes | The unique identifier for the view to retrieve (e.g., 'my-view'). |
No output schema declared.
No examples provided.
get_webhook Get Webhook ~45
Retrieve a single webhook by its unique identifier. Use this to fetch detailed information about a specific webhook configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the webhook to retrieve. |
No output schema declared.
No examples provided.
invite_members Invite Members ~176
Invite one or more new members to join an account via email. Each member receives an invitation and must have a valid email address with either a base role (reader, writer, admin, owner/admin, no_access) or a custom role key. Up to 50 members can be invited per request; the entire request fails if any member's data is invalid or conflicts with existing members.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | Array of member objects to invite. Each object must include an email field and either a role field (base role name) or customRoles field (custom or preset role key). Some roles may require roleAttrib… |
No output schema declared.
No examples provided.
link_resources_to_view Link Resources to View ~200
Link one or multiple resources (flags or segments) to a view using resource keys, filters, or both. When both keys and filters are provided, resources matching either condition are linked.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version for this endpoint. Must be 'beta'. |
| body | – | yes | Request body containing resource keys and/or filters to link. For flags, you can filter by maintainerId, maintainerTeamKey, tags, state, or query. For segments, you can filter by tags, query, or unbo… |
| 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 link. Must be either 'flags' or 'segments'. |
| viewKey | string | yes | The view key where resources will be linked. Use the view identifier (e.g., 'my-view'). |
No output schema declared.
No examples provided.
list_agent_graphs List Agent Graphs ~76
Retrieve all agent graphs in a project with their metadata. Returns graph information without edge data for efficient listing.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Must be set to 'beta'. |
| projectKey | string | yes | The unique identifier for the project containing the agent graphs to list. |
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 21 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.