Integration · Automate and collaborate

LaunchDarkly and Meteor AI agents

Connect LaunchDarkly to an internal Met: check feature flags, their health and history, and turn off a failing flag if the admin allows it.

Book a demo See every integration

How does LaunchDarkly connect to Meteor?

With the LaunchDarkly ready connector, your Met uses LaunchDarkly's official MCP server with the account the admin authorizes. It lists projects and feature flags, opens a flag's configuration in an environment, checks its status across all environments, finds stale flags and queries the change history to see who changed what. Turning a flag on or off, changing its rules or rollout, archiving it and deleting it start turned off until the admin turns them on. If the environment requires approval, the Met creates the request so someone can review it. It lets the owner or the agency turn off, on WhatsApp, a flag that breaks the checkout.

What it automates

What a Meteor Met does with LaunchDarkly

Turn off a flag that breaks the checkout

When someone reports on WhatsApp that payment fails since the last change, the Met finds the flag, checks its status and, if the admin turned on the on/off action, which starts turned off, turns it off in production and tells you how it ended up.

Request approval when the environment requires it

If the environment requires approval, LaunchDarkly does not apply the change and returns the instructions. The Met creates the request with the reviewer you name and then tells you its status.

Find out who changed a flag

The Met queries the account's change history and tells you what changed in the flag, who did it and when.

Clean up stale flags carefully

The Met lists the flags that are candidates for cleanup and runs the removal check on each one. Archiving and deleting start turned off: your team decides with the verdict in hand.

24 tools

Everything your Met can ask LaunchDarkly for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_projects`	Lists the account's LaunchDarkly projects, with search by name or key.
`get_project`	Returns a project with its environments, or confirms it exists.
`list_flags`	Searches and browses a project's feature flags, in a single environment and paginated.
`get_flag`	Returns a flag's full configuration in an environment, with rules, individual targets, prerequisites and variations.
`get_flag_status_across_envs`	Shows the flag's status in each environment (active, inactive, new or launched) and a summary.
`get_flag_health`	Sums up a flag's health, with its state, when it was last requested, its rules, its age and whether it is temporary.
`find_stale_flags`	Finds flags that are candidates for cleanup, stalest first.
`check_removal_readiness`	Checks dependencies, code references, active targeting and per-environment status before removing a flag, and gives a verdict.
`create_flag`	Creates a new feature flag, which starts off in every environment.
`update_flag_settings`	Changes a flag's name, description, tags, maintainer or default variations, without touching its per-environment rules.
`toggle_flag`	Turns a flag on or off in an environment and returns the previous and new state. Starts turned off.
`update_targeting_rules`	Adds, removes or modifies a flag's targeting rules in an environment. Starts turned off.
`update_rollout`	Changes a flag's default rule, with a percentage across variations or a single variation. Starts turned off.
`archive_flag`	Archives a flag reversibly, as the step before deleting it. Starts turned off.
`delete_flag`	Deletes a flag permanently, with no way back. Starts turned off.
`create_approval_request`	Creates an approval request for a flag or segment change in an environment that requires approval, with at least one reviewer.
`list_approval_requests`	Lists a flag's or segment's approval requests, with their status and who requested the change.
`find_members`	Searches LaunchDarkly account members and returns their IDs.
`query_change_history`	Queries the audit log, newest change first, with who made each change and what they did.
`get_sdk_active`	Checks whether any SDK has been active in an environment, to know whether that environment is in use.
`list_alerts`	Lists the project's observability alerts.
`get_alert_firing_history`	Shows when an alert fired and what state it is in now.
`query_error_groups`	Queries the project's error groups.
`query_logs`	Queries the project's logs.

The limits

What the LaunchDarkly integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask you for confirmation in the chat before changing a flag. Turning on or off, changing rules or rollout, archiving and deleting start turned off; if the admin turns them on in Connections, the Met runs them.
It does not skip LaunchDarkly approvals. If the environment requires them, the change stays in a request until a reviewer approves it.
It does not work on LaunchDarkly's European Union instance or in federal environments. The hosted server is not available there.
It does not do more than the connected account's role allows. LaunchDarkly recommends a Writer or Developer role to create, read, update and delete flags.
It does not pay your LaunchDarkly plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect LaunchDarkly

1

A LaunchDarkly account with permissions on the flags

LaunchDarkly recommends a Writer base role, the LaunchDarkly Developer preset role or another role that can create, read, update and delete flags in the projects the Met will use.
2

Connect it in Met

In Met, open Connections → LaunchDarkly → Connect. A LaunchDarkly window opens so you sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about LaunchDarkly and Meteor

Yes, if the admin turns on the flag on/off action, which starts turned off. If the production environment requires approval, the Met creates the request instead of applying the change.

Deleting and archiving start turned off. Even when they are on, LaunchDarkly asks to check first whether the flag is ready to be removed, and archiving is reversible; deleting is not.

It is usually a permissions issue with the account that authorized. Check that it has a role that can manage flags in the project and environment you want to use, and connect again.

You do, with your own LaunchDarkly plan. Meteor does not resell LaunchDarkly: the connector uses your company's account.

Step by step