Gleap AI agents can use LaunchDarkly through Composio, for teams that roll out features behind flags and receive bug reports and feedback from customers in Gleap. Kai Code, Kai Support and custom agents can check which variations a customer receives and which flag changes happened around a report, while flag changes stay with your team.
What a Gleap agent can do in LaunchDarkly
- Why only this customer: Evaluate Context Instance shows which flag variations a customer’s context receives, which can explain an “only I see this” report.
- What changed recently: Get Audit Log Entries and Search Audit Log Entries list recent flag changes, so a report that started this morning can be matched to a rollout.
- How a flag is set up: Get Feature Flag returns a flag’s variations and targeting rules for the teammate or engineer looking at the ticket.
- Flags while fixing: with LaunchDarkly in Kai Code’s MCP settings, Kai Code can read a flag’s configuration when a fix touches flagged code.
Example: a new editor for some customers
A customer reports through the Gleap widget that the text editor lost its formatting toolbar, and nobody on the support team can reproduce it. A teammate asks the agent on the ticket to check LaunchDarkly. The agent evaluates the customer’s context, finds that they are in the 10 percent rollout of the new editor, and sees in the audit log that the rollout started yesterday. The product engineer decides whether to pause the rollout or fix the toolbar first.
How to connect LaunchDarkly
- In Gleap, open Kai Code, click Settings and open MCP.
- Click Add MCP server, search for “LaunchDarkly” and select it.
- Click Connect LaunchDarkly and follow the authorization Gleap shows: a LaunchDarkly access token, or the client ID and secret of your own LaunchDarkly OAuth client followed by a sign-in window.
- Open the LaunchDarkly server and switch off the tools Kai Code should not call, such as Patch Feature Flag, Delete Feature Flag, approval actions and member or project changes.
- For a custom agent, add LaunchDarkly under the agent’s Tools with Add tool instead, then publish and test it.
Kai Code is on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. Custom agents are on the Team, Pro and Enterprise plans.
FAQ
Does Gleap integrate with LaunchDarkly?
Yes. Kai Code, Kai Support and custom agents use LaunchDarkly through Composio’s LaunchDarkly toolkit, which supports access tokens and OAuth. They read or change LaunchDarkly only while they run; Gleap does not sync flags.
What can a Gleap AI agent do in LaunchDarkly?
It can read flags, statuses, contexts, segments, audit logs, experiments and releases, evaluate contexts, and create, change, copy or delete flags, segments, projects and approvals. Changing a flag changes what customers see at once, so give the agents a reader token.
Which Gleap plan includes the LaunchDarkly integration?
Kai Code and Kai Support’s investigations can use LaunchDarkly on Team, Pro and Enterprise, and Kai Support can use connected apps as tools in its customer conversations on the same plans. Custom agents that use LaunchDarkly are part of the Team, Pro and Enterprise plans. The token’s role decides which projects and environments the agents can read. AI usage is billed separately; see pricing.
Can the agent turn a flag off during an incident?
The toolkit allows it, but a flag change is a production change. Keep Patch Feature Flag off, let the agent show which flag and rollout are involved, and let the engineer on call flip it in LaunchDarkly.
