launchdarkly | Type: Application (parent with child servers) | PCID required: Yes
launchdarkly is exposed as multiple MCP server IDs (one per area below). Each child server has its own server path and tool names.
Child servers
| Child server | Server path | Tools | Description |
|---|---|---|---|
| launchdarkly-account | /launchdarkly-account | 32 | LaunchDarkly Account — members, teams, roles, tokens, and users |
| launchdarkly-ai-configs | /launchdarkly-ai-configs | 46 | LaunchDarkly AI Configs — manage AI configurations, variations, and tools |
| launchdarkly-experiments | /launchdarkly-experiments | 22 | LaunchDarkly Experiments — manage experiments, holdouts, and metrics |
| launchdarkly-flags | /launchdarkly-flags | 35 | LaunchDarkly Flags — create, manage, and target feature flags, triggers, and schedules |
| launchdarkly-insights | /launchdarkly-insights | 38 | LaunchDarkly Insights — code references, insights scores, charts, and deployments |
| launchdarkly-integrations | /launchdarkly-integrations | 48 | LaunchDarkly Integrations — webhooks, data export, relay proxy, and flag imports |
| launchdarkly-projects | /launchdarkly-projects | 47 | LaunchDarkly Projects — manage projects, environments, contexts, segments, and layers |
| launchdarkly-usage | /launchdarkly-usage | 46 | LaunchDarkly Usage — account usage, views, audit log, applications, and announcements |
| launchdarkly-workflows | /launchdarkly-workflows | 41 | LaunchDarkly Workflows — approvals, workflows, releases, and pipelines |