LaunchDarkly MCP integration for AI agents.
Connect AI agents to LaunchDarkly through 40 structured actions, including get caller identity, add member to teams, delete environment, and patch environmen…
- ACTION CONTRACTS
- 40
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the LaunchDarkly integration exposes
The LaunchDarkly Agent App exposes 40 provider-backed actions for developer tools work. Its current contract lets an authorized agent get the launchdarkly caller identity for the current access token, add one or more launchdarkly members to one or more teams with a semantic patch update, and delete a launchdarkly environment by project key and environment key. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected LaunchDarkly account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real LaunchDarkly capabilities.
Showing 12 of 40 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_caller_identityREADGet the LaunchDarkly caller identity for the current access token.
add_member_to_teamsWRITEAdd one or more LaunchDarkly members to one or more teams with a semantic patch update.
INPUTS: memberIds / teamKeys / comment
delete_environmentHIGH IMPACTDelete a LaunchDarkly environment by project key and environment key.
INPUTS: projectKey / environmentKey
patch_environmentREVIEWPatch a LaunchDarkly environment with standard JSON Patch operations.
INPUTS: projectKey / environmentKey / patch
create_environmentWRITECreate a LaunchDarkly environment using either common fields or a full official request body.
INPUTS: projectKey / key / name / color / defaultTtl
create_feature_flagWRITECreate a LaunchDarkly feature flag using either common fields or a full official request body.
INPUTS: projectKey / key / name / kind / description
create_projectWRITECreate a LaunchDarkly project using either common fields or a full official request body.
INPUTS: key / name / description / includeInSnippetByDefault / tags
create_segmentWRITECreate a LaunchDarkly segment using either common fields or a full official request body.
INPUTS: projectKey / environmentKey / key / name / description
create_teamWRITECreate a LaunchDarkly team using either common fields or a full official request body.
INPUTS: key / name / description / customRoleKeys / memberIds
create_tokenWRITECreate a LaunchDarkly access token using either common fields or a full official request body.
INPUTS: name / description / role / customRoleIds / inlineRole
delete_feature_flagHIGH IMPACTDelete a LaunchDarkly feature flag by project key and feature flag key.
INPUTS: projectKey / featureFlagKey
delete_projectHIGH IMPACTDelete a LaunchDarkly project by project key.
INPUTS: projectKey
INPUT CONTRACTS
Know what the action needs before it runs.
add_member_to_teams
memberIdsREQUIRED- The LaunchDarkly member identifiers to add to teams.
teamKeysREQUIRED- The LaunchDarkly team keys that should receive the members.
commentOPTIONAL- The comment to attach to the update.
delete_environment
projectKeyREQUIRED- The LaunchDarkly project key.
environmentKeyREQUIRED- The LaunchDarkly environment key.
patch_environment
projectKeyREQUIRED- The LaunchDarkly project key.
environmentKeyREQUIRED- The LaunchDarkly environment key.
patchREQUIRED- JSON Patch operations to apply.
create_environment
projectKeyREQUIRED- The LaunchDarkly project key.
keyOPTIONAL- The environment key to create.
nameOPTIONAL- The environment name to create.
colorOPTIONAL- The display color for the environment.
defaultTtlOPTIONAL- The default time-to-live value for temporary targeting, in minutes.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Caller Identity
Get the LaunchDarkly caller identity for the current access token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_caller_identityControl Add Member To Teams
Add one or more LaunchDarkly members to one or more teams with a semantic patch update. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_member_to_teamsVerify with Add Member To Teams
Add one or more LaunchDarkly members to one or more teams with a semantic patch update. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_member_to_teamsSAFETY BOUNDARY
Operate LaunchDarkly with explicit limits
- Authorize LaunchDarkly with API key and grant only the provider access required by the selected actions.
- 13 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_environment`, `delete_feature_flag`, and `delete_project` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in LaunchDarkly rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the LaunchDarkly task completed successfully.
CONNECTION MODEL
API key
LaunchDarkly personal or service access token sent with the Authorization request header. Create it from LaunchDarkly account authorization settings.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 20
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 6
- REVIEW SIGNALS
- 7
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by LaunchDarkly.