# Launchdarkly (npm · @pipeworx/mcp-launchdarkly)

LaunchDarkly MCP Pack — wraps the LaunchDarkly REST API v2 (https://app.launchdarkly.com/api/v2).

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-launchdarkly/launchdarkly-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-launchdarkly/launchdarkly-mcp)
- npm · `@pipeworx/mcp-launchdarkly`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-launchdarkly/pipeworx-mcp-launchdarkly.md), [page](https://verifymcp.io/servers/pipeworx-io-launchdarkly/pipeworx-mcp-launchdarkly)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-launchdarkly`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-launchdarkly).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 464 tokens (~116/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Launchdarkly MCP server?

Launchdarkly runs locally as an npm package, launched with npx -y @pipeworx/mcp-launchdarkly. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-launchdarkly -- npx -y @pipeworx/mcp-launchdarkly
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-launchdarkly": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-launchdarkly"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-launchdarkly": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-launchdarkly"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-launchdarkly -- npx -y @pipeworx/mcp-launchdarkly
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-launchdarkly": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-launchdarkly"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-launchdarkly --command npx --arg -y --arg @pipeworx/mcp-launchdarkly
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-launchdarkly:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-launchdarkly"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-launchdarkly": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-launchdarkly"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-launchdarkly -t stdio -c npx -a -y @pipeworx/mcp-launchdarkly
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-launchdarkly": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-launchdarkly"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (4)

### `ld_list_projects` (~92 tokens)

Return bounded LaunchDarkly projects with keys, names, tags, environments, and creation metadata. Answers which applications and deployment environments are managed in LaunchDarkly.

Input parameters:

- `_apiKey` (string, required): LaunchDarkly API access token
- `limit` (number): Maximum records, default 20 and maximum 100
- `offset` (number): Records to skip for pagination
- `query` (string)

### `ld_list_environments` (~95 tokens)

Return bounded LaunchDarkly environments for a project with keys, names, colors, tags, approval settings, and archival state. Answers where feature releases and experiments run.

Input parameters:

- `_apiKey` (string, required): LaunchDarkly API access token
- `limit` (number): Maximum records, default 20 and maximum 100
- `offset` (number): Records to skip for pagination
- `project_key` (string, required)

### `ld_list_flags` (~139 tokens)

Return bounded LaunchDarkly feature flags with keys, variations, tags, maintainers, experiment links, lifecycle state, and optional environment rollout configuration. Answers which features are live, experimental, deprecated, or archived.

Input parameters:

- `_apiKey` (string, required): LaunchDarkly API access token
- `environment_key` (string)
- `filter` (string): LaunchDarkly filter expression such as hasExperiment:true or state:live
- `limit` (number): Maximum records, default 20 and maximum 100
- `offset` (number): Records to skip for pagination
- `project_key` (string, required)
- `query` (string)

### `ld_get_flag` (~84 tokens)

Return one LaunchDarkly feature flag with variations, maintainer, experiment links, and optional environment targeting or rollout configuration. Answers exactly how a feature is configured for release or experimentation.

Input parameters:

- `_apiKey` (string, required): LaunchDarkly API access token
- `environment_key` (string)
- `flag_key` (string, required)
- `project_key` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-launchdarkly/pipeworx-mcp-launchdarkly#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 65
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### What is the Launchdarkly MCP server?

Launchdarkly is an MCP server listed in the public MCP registry as io.github.pipeworx-io/launchdarkly. LaunchDarkly MCP Pack, wraps the LaunchDarkly REST API v2 (https://app.launchdarkly.com/api/v2). This page covers its npm package (@pipeworx/mcp-launchdarkly).

### Is the Launchdarkly MCP server safe to use?

Launchdarkly scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Launchdarkly MCP server expose?

Launchdarkly exposes 4 tools: ld_list_projects, ld_list_environments, ld_list_flags, ld_get_flag. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.

### Is the Launchdarkly MCP server still maintained?

Launchdarkly is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Launchdarkly MCP server under?

Launchdarkly declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-launchdarkly
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-launchdarkly
- Repository: https://github.com/pipeworx-io/mcp-launchdarkly
- Website: https://pipeworx.io/packs/launchdarkly
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-launchdarkly/pipeworx-mcp-launchdarkly.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-launchdarkly/pipeworx-mcp-launchdarkly.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-launchdarkly/pipeworx-mcp-launchdarkly