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_agent_optimizations List Agent Optimizations ~58
Retrieve all agent optimizations configured for a specific project. Returns a list of optimization settings and configurations applied to agents within the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier of the project containing the agent optimizations to retrieve. |
No output schema declared.
No examples provided.
list_ai_configs List AI Configs ~72
Retrieve all AI Configs available in a specified project. Returns a list of AI configuration objects that define AI behavior and settings for the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier of the project. Use the project key (e.g., 'default') to specify which project's AI Configs to retrieve. |
No output schema declared.
No examples provided.
list_ai_tool_versions List AI Tool Versions ~71
Retrieve all versions of a specific AI tool within a project. Returns a list of version records for the identified tool.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier of the project containing the AI tool. |
| toolKey | string | yes | The unique identifier of the AI tool for which to retrieve versions. |
No output schema declared.
No examples provided.
list_ai_tools List AI Tools ~55
Retrieve all AI tools available in a specific project. Returns a complete list of configured AI tools that can be used within the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier of the project containing the AI tools to retrieve. |
No output schema declared.
No examples provided.
list_announcements List Announcements ~69
Retrieve a list of announcements filtered by their publication status. Use this to fetch active, inactive, or scheduled announcements for display or management purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter announcements by their current status: active (published and visible), inactive (unpublished), or scheduled (queued for future publication). |
No output schema declared.
No examples provided.
list_application_versions List Application Versions ~68
Retrieve all versions for a specific application identified by its application key. Returns a list of version records associated with the application in the account.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | yes | The unique identifier for the application. This string key is used to look up and retrieve all versions belonging to that specific application. |
No output schema declared.
No examples provided.
list_applications List Applications ~33
Retrieve a list of all applications. Optionally expand the response to include additional details such as flags evaluated by each application.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_approval_requests List Approval Requests ~49
Retrieve all approval requests with support for filtering by assignee, requestor, resource, status, and review status. Optionally expand the response to include related flag, project, and environment details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_approval_requests_for_flag List Approval Requests for Flag ~98
Retrieve all pending approval requests for a feature flag in a specific environment. Use this to review changes awaiting approval before they can be deployed.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which to list approval requests. |
| featureFlagKey | string | yes | The unique identifier for the feature flag to retrieve approval requests for. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
list_audit_log_entries List Audit Log Entries ~104
Retrieve audit log entries with optional filtering by date ranges, resource specifiers, or full-text search. Use resource specifier syntax to target specific resources or collections.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | Full or partial resource name to search for in audit logs. Supports text-based matching across resource identifiers. |
| spec | string | – | Resource specifier to filter results by specific resources or resource collections. Use LaunchDarkly resource specifier syntax to target particular resource types or instances. |
No output schema declared.
No examples provided.
list_audit_subscriptions_by_integration List Audit Subscriptions by Integration ~62
Retrieve all audit log subscriptions associated with a specific integration. Use this to view which audit events are being monitored for a given integration.
| Name | Type | Req | Description |
|---|---|---|---|
| integrationKey | string | yes | The unique identifier for the integration whose audit log subscriptions you want to retrieve. |
No output schema declared.
No examples provided.
list_branches List Branches ~62
Retrieve a list of all branches in the specified repository. Use this to discover available branches for code references and analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | The name of the repository to list branches from. This is a required identifier that specifies which repository's branches to retrieve. |
No output schema declared.
No examples provided.
list_code_reference_statistics List Code Reference Statistics ~26
Retrieve code reference statistics and repository links for all projects that have code references configured.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_context_attribute_names List Context Attribute Names ~77
Retrieve all available context attribute names for a specific environment within a project. This returns the list of attributes that can be used to define user context in feature flag evaluations.
| 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 environment. |
No output schema declared.
No examples provided.
list_context_kinds_by_project List Context Kinds by Project ~74
Retrieve all context kinds configured for a specific project. Context kinds define the types of contextual information that can be associated with feature flags and experiments in the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. This is a string-based key that distinguishes the project within your LaunchDarkly workspace. |
No output schema declared.
No examples provided.
list_custom_roles List Custom Roles ~47
Retrieve all custom roles available in your LaunchDarkly organization, including project-specific roles, organization-wide roles, and LaunchDarkly-provided preset roles. Base roles are excluded from this list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_deployments List Deployments ~229
Retrieve a list of deployments for a specific project and environment, with optional filtering by application, time range, kind, and status. Supports expansion to include associated pull requests and flag references.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Comma-separated list of application keys to filter deployments by specific applications. Omit to include all applications. |
| environmentKey | string | yes | The environment key that identifies which environment to query deployments for. |
| from | string | – | Unix timestamp in milliseconds marking the start of the time range. Defaults to 7 days before the current time if not specified. |
| kind | string | – | Filter deployments by deployment kind (e.g., 'blue-green', 'canary'). Omit to include all kinds. |
| projectKey | string | yes | The project key that identifies which project to query deployments for. |
| status | string | – | Filter deployments by deployment status (e.g., 'active', 'completed'). Omit to include all statuses. |
| to | string | – | 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.
list_destinations List Destinations ~34
Retrieve all Data Export destinations configured across your projects and environments. This provides a comprehensive view of where your data is being exported.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_environments_by_project List Environments by Project ~70
Retrieve a paginated list of environments for a specified project, with support for filtering by name/key and tags, and sorting by creation date, criticality, or name.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. Used to scope the environment list to a specific project. |
No output schema declared.
No examples provided.
list_experiments List Experiments ~133
Retrieve all experiments in an environment with optional filtering by flag, metric, or iteration status, and optional expansion of related data such as iterations, metrics, treatments, and analysis configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key that identifies the specific environment within the project where experiments are located. |
| lifecycleState | string | – | A comma-separated list specifying which experiment states to include in results. Valid values are `archived`, `active`, or both. Defaults to returning only active experiments if not specified. |
| projectKey | string | yes | The project key that identifies the LaunchDarkly project containing the experiments. |
No output schema declared.
No examples provided.
list_experiments_project List Experiments in Project ~97
Retrieve a list of experiments across all environments in a project, optionally filtered by lifecycle state (active, archived, or both).
| Name | Type | Req | Description |
|---|---|---|---|
| lifecycleState | string | – | Filter experiments by lifecycle state using a comma-separated list. Valid values are `active`, `archived`, or both. Defaults to `active` experiments only if not specified. |
| projectKey | string | yes | The unique identifier for the project from which to retrieve experiments. |
No output schema declared.
No examples provided.
list_expiring_context_targets List Expiring Context Targets ~102
Retrieve a list of context targets scheduled for removal from a feature flag. This helps identify and manage temporary targeting rules that are approaching their expiration date.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the feature flag is configured. |
| featureFlagKey | string | yes | The unique identifier for the feature flag whose expiring context targets should be retrieved. |
| projectKey | string | yes | The unique identifier for the project containing the feature flag. |
No output schema declared.
No examples provided.
list_expiring_targets_for_segment List Expiring Targets for Segment ~103
Retrieve a list of context targets within a segment that are scheduled for removal. This helps identify which targets will be automatically deleted from the segment.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the segment's expiring targets are managed. |
| projectKey | string | yes | The unique identifier for the project containing the segment. |
| segmentKey | string | yes | The unique identifier for the segment whose expiring context targets you want to retrieve. |
No output schema declared.
No examples provided.
list_expiring_user_targets_for_feature_flag List Expiring User Targets for Feature Flag ~125
Retrieve a list of user targets scheduled for removal from a feature flag in a specific environment. Note: This endpoint is deprecated; use list_expiring_context_targets_for_feature_flag instead after upgrading to context-based SDKs.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The environment key that specifies which environment's feature flag targeting data to retrieve. |
| featureFlagKey | string | yes | The feature flag key that identifies which flag's expiring user targets to list. |
| projectKey | string | yes | The project key that identifies the LaunchDarkly project containing the feature flag. |
No output schema declared.
No examples provided.
list_expiring_user_targets_for_segment List Expiring User Targets for Segment ~114
Retrieve a list of user targets scheduled for removal from a specific segment. Note: This endpoint is deprecated; use list_expiring_targets_for_segment instead after upgrading to context-based SDKs.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project where the segment is defined. |
| projectKey | string | yes | The unique identifier for the LaunchDarkly project containing the segment. |
| segmentKey | string | yes | The unique identifier for the segment whose expiring user targets should be retrieved. |
No output schema declared.
No examples provided.
list_extinctions List Extinctions ~199
Retrieve a list of all extinction events, which are created when all code references to a flag are removed. Filter results by repository, branch, project, or commit time window to find specific extinctions.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | Filter results to extinctions in a specific branch. If not specified, only the default branch is queried. |
| from | string | – | Filter results to extinctions after a specific point in time, expressed as a Unix epoch timestamp in milliseconds. Must be used together with the `to` parameter. |
| projKey | string | – | Filter results to extinctions in a specific project by project key. |
| repoName | string | – | Filter results to extinctions in a specific repository by name. |
| to | string | – | Filter results to extinctions before a specific point in time, expressed as a Unix epoch timestamp in milliseconds. Must be used together with the `from` parameter. |
No output schema declared.
No examples provided.
list_feature_flag_statuses List Feature Flag Statuses ~79
Retrieve the status of all feature flags in a specific project and environment, including their current state (new, active, inactive, or launched) and last request timestamp.
| 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 feature flags. |
No output schema declared.
No examples provided.
list_feature_flags List Feature Flags ~142
Retrieve all feature flags in a project with optional filtering by environment, tags, and other criteria. Supports pagination, sorting, and field expansion to optimize response payload and performance.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | Filter flag configurations to a specific environment (e.g., 'production', 'staging'). Required when using environment-specific filters like `evaluated` or `targetingModifiedDate` sorting. |
| projectKey | string | yes | The unique identifier for the project containing the feature flags. |
| summary | boolean | – | Set to `0` to include detailed flag configuration including prerequisites, targets, and rules for each environment. By default, these details are excluded for performance. |
No output schema declared.
No examples provided.
list_flag_events List Flag Events ~295
Retrieve a list of flag events for a specific project and environment, with optional filtering by application, flag key, impact size, and experiment association. Supports expanding the response to include experiment details.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Comma-separated list of application keys to filter events by specific applications. |
| environmentKey | string | yes | The environment key that identifies which environment within the project to query for flag events. |
| from | string | – | Unix timestamp in milliseconds marking the start of the time range. Defaults to 7 days ago if not specified. |
| global | string | – | Include or exclude global events from results. Defaults to `include`. Valid options are `include` or `exclude`. |
| hasExperiments | boolean | – | Filter to show only events associated with experiments (`true`) or events without experiments (`false`). |
| impactSize | string | – | Filter events by the magnitude of user impact: `none` (no change), `small` (less than 20% change), `medium` (20-80% change), or `large` (more than 80% change). |
| projectKey | string | yes | The project key that identifies which project to query for flag events. |
| query | string | – | Filter events by flag key using a search query string. |
| to | string | – | 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.
list_flag_followers List Flag Followers ~100
Retrieve a list of team members who are following a specific feature flag within a project and environment. This helps identify who is monitoring changes to the flag.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment in which to retrieve flag followers. |
| featureFlagKey | string | yes | The unique identifier for the feature flag whose followers 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_flag_followers_by_project_environment List Flag Followers by Project Environment ~84
Retrieve all followers across feature flags within a specific project and environment. This returns the list of users or teams monitoring flag changes in that environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment within the project where you want to retrieve flag followers. |
| projectKey | string | yes | The unique identifier for the project containing the flags and environment. |
No output schema declared.
No examples provided.
list_flag_triggers List Flag Triggers ~94
Retrieve all triggers configured for a feature flag in a specific environment. Triggers define automated workflows that respond to flag changes.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentKey | string | yes | The unique identifier for the environment where the flag triggers are configured. |
| featureFlagKey | string | yes | The unique identifier for the feature flag whose triggers 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_insight_groups List Insight Groups ~70
Retrieve a list of insight groups for which you are collecting engineering insights. Optionally filter by group name and expand the response to include scores, environment details, or metadata indicators.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Filter the insight groups list by group name. Supports partial string matching to find groups by name. |
No output schema declared.
No examples provided.
list_layers List Layers ~57
Retrieve all layers for a specified project. Returns a collection of layer resources associated with the given project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. This string value is used to scope the layer collection to a specific project. |
No output schema declared.
No examples provided.
list_linked_resources_for_view List Linked Resources for View ~201
Retrieve all linked resources of a specified type (flags or segments) associated with a given view within a project. Optionally filter results using a case-insensitive search query.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version for this endpoint. Must be set to 'beta' to access this operation. |
| projectKey | string | yes | The project key that identifies the project containing the view. Use the project's unique identifier (e.g., 'default'). |
| query | string | – | Optional case-insensitive search filter that matches against the resource key and resource name. Leave empty to retrieve all linked resources without filtering. |
| resourceType | string | yes | The type of linked resource to retrieve. Must be either 'flags' for feature flags or 'segments' for user segments. |
| viewKey | string | yes | The view key that identifies the specific view within the project. Use the view's unique identifier (e.g., 'my-view'). |
No output schema declared.
No examples provided.
list_linked_views_for_resource List Linked Views for Resource ~174
Retrieve all views linked to a specific resource (flag or segment). Use the resource key for flags and segment ID for segments to identify the target resource.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this request. Currently supports 'beta' version. |
| environmentId | string | – | The environment ID where the resource exists. Required when resourceType is 'segments'; optional for flags. |
| projectKey | string | yes | The project key that contains the resource. Typically 'default' for standard projects. |
| resourceKey | string | yes | The unique identifier for the resource. For flags, use the flag key. For segments, use the segment ID. |
| resourceType | string | yes | The type of resource to retrieve linked views for. Must be either 'flags' or 'segments'. |
No output schema declared.
No examples provided.
list_members List Members ~49
Retrieve a paginated list of account members with support for filtering by query, role, ID, email, team membership, and activity status. Optionally expand the response to include custom roles and role attributes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_metric_groups List Metric Groups ~73
Retrieve all metric groups for a project. Supports filtering by experiment status, connections, kind, maintainers, and fuzzy search; results can be sorted by name, creation date, or connection count.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. Used to scope the metric groups to a specific project. |
No output schema declared.
No examples provided.
list_metrics List Metrics ~67
Retrieve all metrics for a specified project with support for filtering by various criteria (data sources, event types, tags, usage context) and optional expansion of related experiment counts.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project. Used to scope the metrics query to a specific project. |
No output schema declared.
No examples provided.
list_model_configs List Model Configs ~87
Retrieve all AI model configurations for a specified project. Optionally filter to show only restricted models.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project (e.g., 'default'). This determines which project's model configurations are returned. |
| restricted | boolean | – | When set to true, returns only model configurations that are restricted. Omit or set to false to return all configurations. |
No output schema declared.
No examples provided.
list_oauth_clients List OAuth Clients ~33
Retrieve all OAuth 2.0 clients registered with your account. Use this to view and manage your application integrations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects List Projects ~56
Retrieve a paginated list of projects with support for filtering by name, tags, or keys, and sorting by name or creation date. Results are limited to 20 projects per page by default; use pagination links to navigate through additional pages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_prompt_snippet_references List Prompt Snippet References ~77
Retrieve all AI Config variations that currently reference a specific prompt snippet, helping you understand where a snippet is being used across your project.
| 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 whose references you want to list. |
No output schema declared.
No examples provided.
list_prompt_snippets List Prompt Snippets ~54
Retrieve all prompt snippets available in a specific project. Prompt snippets are reusable text templates used to configure AI behavior and responses.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The unique identifier for the project containing the prompt snippets to retrieve. |
No output schema declared.
No examples provided.
list_pull_requests List Pull Requests ~224
Retrieve a list of pull requests for a project with optional filtering by status, application, date range, and search terms. Supports expanding the response to include deployment details, flag references, and lead time metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationKey | string | – | Filter results to pull requests deployed to specific applications. Provide as a comma-separated list of application keys. |
| environmentKey | string | – | The environment key, required only when sorting results by lead time metrics. |
| from | string | – | Start of the date range as a Unix timestamp in milliseconds. Defaults to 7 days before the end date if not specified. |
| projectKey | string | yes | The project key that identifies which project's pull requests to retrieve. |
| query | string | – | Search pull requests by title or author name. Performs a text match against these fields. |
| status | string | – | Filter results by pull request status. Valid options are: open, merged, closed, or deployed. |
| to | string | – | End of the date range as a Unix timestamp in milliseconds. Defaults to the current time if not specified. |
No output schema declared.
No examples provided.
list_relay_proxy_configs List Relay Proxy Configurations ~33
Retrieve all Relay Proxy configurations currently configured in your account. Use this to view existing proxy setups and their settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_release_pipelines List Release Pipelines ~52
Retrieve all release pipelines for a project. Supports filtering by pipeline attributes (key, name, description) and environment.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | The project key that identifies which project's release pipelines to retrieve. |
No output schema declared.
No examples provided.
list_release_policies List Release Policies ~111
Retrieve a list of release policies for a specified project with optional filtering to exclude the default policy.
| Name | Type | Req | Description |
|---|---|---|---|
| LD-API-Version | string | yes | The API version to use for this endpoint; must be set to 'beta'. |
| excludeDefault | boolean | – | Set to true to exclude the default release policy from the results; when false or omitted, the default policy is included if an environment filter is present. |
| projectKey | string | yes | The unique identifier for the project (e.g., 'default'). |
No output schema declared.
No examples provided.
list_release_progressions_for_pipeline List Release Progressions for Pipeline ~84
Retrieve the progression status of all releases across all feature flags within a specified release pipeline. This provides a comprehensive view of how releases are advancing through the pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| pipelineKey | string | yes | The unique identifier for the release pipeline whose release progressions you want to retrieve. |
| projectKey | string | yes | The unique identifier for the project containing the release pipeline. |
No output schema declared.
No examples provided.
list_repositories List Repositories ~121
Retrieve a list of connected repositories with optional branch metadata and code references. Filter results by project key to scope code references to a specific LaunchDarkly project.
| Name | Type | Req | Description |
|---|---|---|---|
| projKey | string | – | Filter code reference results to a specific LaunchDarkly project by providing its project key. |
| withBranches | string | – | Include branch metadata in the response. Set to any value to enable this option. |
| withReferencesForDefaultBranch | string | – | Include branch metadata and code references for the default git branch in the response. Set to any value to enable this option. |
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.