---
title: "LaunchDarkly hosted MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/launchdarkly-hosted/
description: "Manage feature flags and AgentControl configurations, and inspect observability data through LaunchDarkly’s hosted OAuth service."
---

# LaunchDarkly hosted MCP: review, setup & limitations · Undominated.ai

> Manage feature flags and AgentControl configurations, and inspect observability data through LaunchDarkly’s hosted OAuth service.

[← Explore all mcp servers](/mcp-servers/)

FEATURE FLAGS AND RELEASES / LaunchDarkly

# LaunchDarkly hosted MCP

Manage feature flags and AgentControl configurations, and inspect observability data through LaunchDarkly’s hosted OAuth service.

 [See setup guidance ↓](#setup)[Original source ↗](https://launchdarkly.com/docs/home/getting-started/mcp-hosted)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher LaunchDarkly
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“LaunchDarkly hosted MCP server”

 [LaunchDarkly · upstream description ↗](https://launchdarkly.com/docs/home/getting-started/mcp-hosted) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Uses the publisher’s preferred hosted connection for supported environments.
- Links feature-flag operations and observability context while retaining project and environment role checks.
- The page publishes a concrete endpoint (https://mcp.launchdarkly.com/mcp/launchdarkly) rather than only a product name.
- The hosted endpoint uses OAuth; legacy local-server API-key configuration is a separate setup path.

### A good fit for

 - Reviewing a flag’s environment-specific setup before preparing a rollout change.
- Investigating observability evidence alongside flag and AgentControl configuration, with write actions reviewed separately.
- Connect a client to the endpoint on this page and inspect the live tool list before relying on a tool name.
- Match the credentials and transport on this page, and do not treat unstated tools as available.

### Weigh up before choosing

 - The service is write-capable: role permissions can allow creating, updating and deleting flags and AgentControl configurations.
- The maintained local server is still the documented path for EU and Federal environments; do not assume the hosted endpoint serves those accounts.
- A successful OAuth flow can still be followed by 403 responses when project/environment permissions are insufficient.
- Individual tool names were not on the fetched page, so this review does not invent them.
- This review did not start the server or call its tools.
- Local server environment examples do not configure the hosted service, and OAuth success alone does not authorize flag or AgentControl mutations.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - LaunchDarkly hosted MCP setup, migration and permissions
- Pinned local-server scope and hosted-service recommendation
- Documentation mcp-hosted
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The official hosted guide documents OAuth, migration from API-key startup and permission-related 403 errors.
- The pinned local repository explicitly limits its recommended use to EU/Federal environments; its MIT licence is not applied to the hosted service.
- The page documents the remote endpoint https://mcp.launchdarkly.com/mcp/launchdarkly.
- That endpoint is documented with Streamable HTTP, not only as a local process.
- The page describes an OAuth sign-in for the hosted server.
- Hosted MCP uses OAuth instead of the legacy --api-key/LD_ACCESS_TOKEN local configuration; a post-login 403 commonly reflects project/environment permissions.

### Not established by this review

 - Installation, authentication and live tool execution were not tested.
- Service availability, security isolation and package/container parity with source were not tested.
- The server was not installed or initialised.
- No tools/list or tool call was made.
- A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://launchdarkly.com/docs/home/getting-started/mcp-hosted)

DOCUMENTED COMMAND

 claude mcp add --transport http launchdarkly https://mcp.launchdarkly.com/mcp/launchdarkly Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Add the hosted endpoint using the client-specific guide or the shown Cursor configuration.
- Complete OAuth with an account restricted to the intended projects and environments. Review client write approvals before invoking mutations.
- When migrating from the local package, remove the old server entry and hardcoded API-token arguments, then reconnect OAuth.
- For a 403, check project/environment role access before repeatedly reconnecting. Consult the separate local-server guide for EU or Federal accounts.
- Reconnect the hosted OAuth integration and inspect the authorized account's role and project/environment grants before troubleshooting token syntax.

### Before you start

 - A supported MCP client and a LaunchDarkly account in an environment supporting hosted MCP.
- Role permissions appropriate to the selected projects, environments and operations.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "launchdarkly": {
 "url": "https://mcp.launchdarkly.com/mcp/launchdarkly"
 }
 }
} Copy configuration ↗

### Compatibility

Claude Code · Cursor · Windsurf · GitHub Copilot

### Transports

Streamable HTTP

### Hosted service

 - Reads observability and configuration data under the authorised account.
- Can create, update and delete flags and AgentControl configurations when the account role allows.
- An OAuth sign-in for the account that owns the data, as the page describes

### Cost model

LaunchDarkly account and product entitlements apply. No hosted-service code licence or usage rate was established.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [LaunchDarkly hosted MCP setup, migration and permissions ↗](https://launchdarkly.com/docs/home/getting-started/mcp-hosted) Checked 2026-10-14 https://launchdarkly.com/docs/home/getting-started/mcp-hosted Supports: install, configExample, access, limitations, review
- [Pinned local-server scope and hosted-service recommendation ↗](https://github.com/launchdarkly/mcp-server/blob/c3d39cfb085859d389bda11a321064f22dee316a/README.md) Checked 2026-10-14 https://github.com/launchdarkly/mcp-server/blob/c3d39cfb085859d389bda11a321064f22dee316a/README.md Supports: limitations, review

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
