01 · Records and state owned
Projects and environments, feature flags and targeting rules, AgentControl configurations, and observability data including logs, traces, errors and dashboards.
LaunchDarkly
LaunchDarkly
A leading feature-management platform with robust APIs, webhooks, SDKs, approvals, environments, audit history, and experimentation—an important example of governed actions beyond marketing applications.
Analytics, SEO & experimentationSystem of intelligenceExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve and evaluate flag/configuration state and query supported observability data for authorized projects and environments.
03 · Actions and write paths
Create, update and delete flags and AgentControl configurations when authorized. Production targeting, rollout and deletion changes should require review and rollback planning.
04 · Authentication and permissions
The hosted server uses OAuth; the local server uses a scoped API token. LaunchDarkly roles, projects, environments and token permissions define effective access.
05 · Monitoring, approval, and recovery
Treat production flag changes as runtime-control changes: require environment selection, change review, progressive rollout, auditability and a tested rollback path.
06 · Gaps and implementation limits
Hosted MCP is unavailable in LaunchDarkly federal and EU environments; local deployment, token scope and environment targeting differ and must be configured carefully.
Agent access
MCP and adjacent posture
Verified first-party provider MCPLaunchDarkly-hosted OAuth MCP plus local server optionsCurrent documented service
Role: provider
Read scope: Feature flags and targeting configuration, AgentControl configurations, and observability data such as logs, traces, errors and dashboards for authorized projects and environments.
Write scope: Create, evaluate, modify and delete feature flags and AgentControl configurations when the token or OAuth grant permits it; observability tools are query-oriented.
Authentication: OAuth for the hosted MCP server; scoped LaunchDarkly API token for the local server.
Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that LaunchDarkly ships these experiences.
Single-platform patterns
- Experiment and release decision workbench
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- LaunchDarkly + warehouse or semantic layer: executive insight brief
- LaunchDarkly + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
6 recorded sources
Platform core validationRepresentative source
https://launchdarkly.com/docs/home/getting-started/mcp ↗Projects and environments, feature flags and targeting rules, AgentControl configurations, and observability data including logs, traces, errors and dashboards. Create, update and delete flags and AgentControl…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP and platform-access review
HomepageSource inventory
https://launchdarkly.com/ ↗Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
DocumentationSource inventory
https://launchdarkly.com/docs ↗First-party platform documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
APISource inventory
https://launchdarkly.com/docs/api ↗First-party REST API reference.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
WebhooksSource inventory
https://launchdarkly.com/docs/integrations/webhooks ↗First-party event guidance.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP / agent-role validationTargeted review
https://launchdarkly.com/docs/home/getting-started/mcp-hosted ↗Official documentation confirms feature-flag, AgentControl, and observability tools; local deployment supports additional environments.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role claim review; exact live reachability was not independently retested for every URL.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.