Can I use LaunchDarkly as a CLI?

Yes. KosmoKrator exposes a LaunchDarkly CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose LaunchDarkly through MCP?

Yes. The KosmoKrator MCP gateway can expose selected LaunchDarkly tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are LaunchDarkly credentials stored?

LaunchDarkly credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for LaunchDarkly MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

devtools

LaunchDarkly CLI for Headless Automation

Use the LaunchDarkly CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit LaunchDarkly feedback View package source

LaunchDarkly CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The LaunchDarkly CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# LaunchDarkly CLI for Headless Automation
kosmokrator integrations:configure launchdarkly --set access_token="$LAUNCHDARKLY_ACCESS_TOKEN" --set project_key="$LAUNCHDARKLY_PROJECT_KEY" --enable --read allow --write ask --json
kosmo integrations:call launchdarkly.launchdarkly_list_flags '{"project_key":"example_project_key","limit":1,"offset":1,"env":"example_env"}' --json

Discovery Before Execution

Agents and scripts can inspect LaunchDarkly docs and schemas before choosing a function.

kosmo integrations:docs launchdarkly --json
kosmo integrations:docs launchdarkly.launchdarkly_list_flags --json
kosmo integrations:schema launchdarkly.launchdarkly_list_flags --json
kosmo integrations:search "LaunchDarkly" --json
kosmo integrations:list --json

Useful LaunchDarkly CLI Functions

Function	Type	Parameters	Description
`launchdarkly.launchdarkly_list_flags`	Read	project_key, limit, offset, env	List feature flags in a LaunchDarkly project. Returns flag keys, names, descriptions, and their on/off state per environment.
`launchdarkly.launchdarkly_get_flag`	Read	feature_flag_key, project_key, env	Get detailed information about a specific LaunchDarkly feature flag, including targeting rules, variations, and per-environment state.
`launchdarkly.launchdarkly_toggle_flag`	Write	feature_flag_key, enabled, environment_key, project_key	Turn a LaunchDarkly feature flag on or off in a specific environment. Use this to enable or disable a feature flag.
`launchdarkly.launchdarkly_list_environments`	Read	project_key	List all environments for a LaunchDarkly project. Returns environment keys, names, and their SDK keys for reference.
`launchdarkly.launchdarkly_list_projects`	Read	none	List all LaunchDarkly projects. Returns project keys, names, and the number of environments in each project.
`launchdarkly.launchdarkly_get_project`	Read	project_key	Get detailed information about a specific LaunchDarkly project, including its environments and settings.
`launchdarkly.launchdarkly_get_current_user`	Read	none	Get information about the currently authenticated LaunchDarkly user. Useful for verifying API credentials.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related LaunchDarkly CLI Pages

CI LaunchDarkly CLI for CI. Cron Jobs LaunchDarkly CLI for cron jobs. Shell Scripts LaunchDarkly CLI for shell scripts. Coding Agents LaunchDarkly CLI for coding agents.