How to connect LaunchDarkly to OpenClaw
Connect LaunchDarkly to OpenClaw with ClawLink: paste your LaunchDarkly key once and 248 tools work from chat. No MCP server to run, nothing stored on your machine.
LaunchDarklyAPI KEYMCPA feature management platform that helps teams build better software faster using feature flags.. Once connected, OpenClaw can read and act on LaunchDarkly from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to LaunchDarkly access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical LaunchDarkly setup: install one ClawHub skill, connect LaunchDarkly in the browser, and OpenClaw can call real LaunchDarkly actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the LaunchDarkly skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "LaunchDarkly" (hith3sh/launch-darkly-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/launch-darkly-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to LaunchDarkly.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect LaunchDarkly
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with LaunchDarkly?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect LaunchDarkly in the ClawLink dashboard — paste your LaunchDarkly API key once.
Verify the connection by asking OpenClaw:
Use LaunchDarkly to add member to teams and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once LaunchDarkly is connected in the dashboard, that agent calls the same 248 LaunchDarkly tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
LaunchDarkly MCP for OpenClaw
Looking for a LaunchDarkly MCP server for OpenClaw? ClawLink connects LaunchDarkly to OpenClaw and exposes 248 LaunchDarkly tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes LaunchDarkly integration works the same way.
What the OpenClaw LaunchDarkly integration can do
248 LaunchDarkly tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 248.
30 of 248 LaunchDarkly tools for OpenClaw
| Tool | What it does |
|---|---|
Add member to teams launch_darkly_add_member_to_teams | Add a LaunchDarkly member to one or more teams |
Apply approval request launch_darkly_apply_approval_request | Apply an approved approval request in LaunchDarkly |
Apply approval request for flag launch_darkly_apply_approval_request_for_flag | Apply an approved approval request for a feature flag in LaunchDarkly |
Copy feature flag launch_darkly_copy_feature_flag | Copy a feature flag's configuration from one environment to another within the same project |
Create migration safety issues launch_darkly_create_migration_safety_issues | Check migration safety issues for a feature flag patch |
Evaluate context instance launch_darkly_evaluate_context_instance | Evaluate flags for a context instance to determine expected flag variations |
Generate trust policy launch_darkly_generate_trust_policy | Generate an AWS trust policy for Data Export destinations |
Get all holdouts launch_darkly_get_all_holdouts | Retrieve all holdouts for a specific project and environment |
Get all integration configurations launch_darkly_get_all_integration_configurations | Retrieve all integration configurations for a specific integration key |
Get all release pipelines launch_darkly_get_all_release_pipelines | Retrieve all release pipelines for a project |
Get all webhooks launch_darkly_get_all_webhooks | Retrieve all webhooks configured in the LaunchDarkly account |
Get announcements public launch_darkly_get_announcements_public | Retrieve public announcements from LaunchDarkly |
Get application versions launch_darkly_get_application_versions | Retrieve all versions for a specific application in LaunchDarkly |
Get applications launch_darkly_get_applications | Retrieve a list of applications in LaunchDarkly |
Get approval for flag launch_darkly_get_approval_for_flag | Get a single approval request for a feature flag in LaunchDarkly |
Get approval request launch_darkly_get_approval_request | Get a specific approval request by ID from LaunchDarkly |
Get approval request settings launch_darkly_get_approval_request_settings | Retrieve approval request settings for a project |
Get approval requests launch_darkly_get_approval_requests | Retrieve all approval requests from LaunchDarkly |
Get approvals for flag launch_darkly_get_approvals_for_flag | Retrieve all approval requests for a specific feature flag in an environment |
Get audit log entries launch_darkly_get_audit_log_entries | Get a list of all audit log entries |
Get audit log entry launch_darkly_get_audit_log_entry | Retrieve a single audit log entry by ID |
Get big segment export launch_darkly_get_big_segment_export | Retrieve a specific big segment export by its ID |
Get big segment import launch_darkly_get_big_segment_import | Retrieve the status and details of a big segment import by its ID |
Get big segment store integration launch_darkly_get_big_segment_store_integration | Retrieve a specific persistent store integration for big segments by its ID |
Get big segment store integrations launch_darkly_get_big_segment_store_integrations | Retrieve all persistent store integrations for big segments |
Get branch launch_darkly_get_branch | Retrieve branch information from a LaunchDarkly code reference repository |
Get caller identity launch_darkly_get_caller_identity | Retrieve basic information about the identity used to authenticate API calls |
Get context attribute names launch_darkly_get_context_attribute_names | Retrieve context attribute names for a project and environment |
Get context attribute values launch_darkly_get_context_attribute_values | Retrieve unique values for a specific context attribute within a project environment |
Get context instances launch_darkly_get_context_instances | Get context instances for a specific context ID within a project and environment |
Try it: find the LaunchDarkly tool you need
Browse the 30 LaunchDarkly tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use LaunchDarkly to add member to teams and walk me through the result in plain English.
Use LaunchDarkly to apply approval request and walk me through the result in plain English.
Use LaunchDarkly to apply approval request for flag and walk me through the result in plain English.
Use LaunchDarkly to copy feature flag and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want LaunchDarkly working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the LaunchDarkly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected LaunchDarkly account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for LaunchDarkly. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right LaunchDarkly actions to the runtime in a format your agent can reliably use. | 248 tools for LaunchDarkly are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes LaunchDarkly to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect LaunchDarkly in the browser, and the 248 tools above work from chat. There is no SDK and no config file, and the LaunchDarkly key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the LaunchDarkly skill but can't call the tools
The ClawHub skill teaches OpenClaw about LaunchDarkly, but the calls run through the ClawLink plugin and your connected account. Make sure LaunchDarkly is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect LaunchDarkly from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling LaunchDarkly tools
LaunchDarkly tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every LaunchDarkly call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
LaunchDarkly returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for LaunchDarkly has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw LaunchDarkly integration?
Yes. ClawLink is the fastest way to connect OpenClaw to LaunchDarkly: link your LaunchDarkly account once in the browser and OpenClaw can call the LaunchDarkly API through 248 ready-made tools — no custom code or token handling.
How do I add LaunchDarkly to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink LaunchDarkly skill from ClawHub, then you click Connect in the dashboard to authorize LaunchDarkly. OpenClaw calls the tools from the next message — no config files, and the LaunchDarkly key you paste is stored server-side instead of in your environment.
How long does it take to connect LaunchDarkly to OpenClaw?
About two minutes. Sign in, click Connect next to LaunchDarkly in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring LaunchDarkly up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want LaunchDarkly working from chat.
OpenClaw installed the LaunchDarkly skill but can't call the tools
The ClawHub skill teaches OpenClaw about LaunchDarkly, but the calls run through the ClawLink plugin and your connected account. Make sure LaunchDarkly is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.