24 actions ready for your AI

Connect LaunchDarkly to your AI

Add your LaunchDarkly key once and every AI you use can get projects, post projects and post environments through it.

Needs your API keyWorks today: paste the key from this app and your AI can use it. One-click sign-in is not built yet.

Not verified by us yet. Its actions come from LaunchDarkly's own documented API, and we have not run them here yet.

Use your own LaunchDarkly account. Credentials stay encrypted in ahel.

Tell me when ahel has verified LaunchDarkly

What your AI can do with LaunchDarkly

Choose a task and ask your AI.

Project

  • Get projectsGET

    Returns a list of all projects in the account.

  • Post projectPOST

    Create a new project with the given key and name.

    keyrequired
    namerequired
  • Get projectGET

    Fetch a single project by key.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
  • Patch projectPATCH

    Modify a project by ID.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    body
    The request body.
  • Delete projectDELETE

    Delete a project by key. Caution-- deleting a project will delete all associated environments and feature flags. You cannot delete the last project in an account.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.

Flag

  • Get flag config scheduled changesGET

    Get all scheduled workflows for a feature flag by key.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    featureFlagKeyrequired
    The feature flag's key.
    environmentKeyrequired
    The environment key, used to tie together flag configuration and users under one environment so they can be managed together.
  • Post flag config scheduled changesPOST

    Creates a new scheduled change for a feature flag.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    featureFlagKeyrequired
    The feature flag's key.
    environmentKeyrequired
    The environment key, used to tie together flag configuration and users under one environment so they can be managed together.
    comment
    Used to describe the scheduled changes.
  • Get flag config scheduled changes conflictsPOST

    Lists conflicts between the given instructions and any existing scheduled changes for the feature flag. The actual HTTP verb should be REPORT, not POST.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    featureFlagKeyrequired
    The feature flag's key.
    environmentKeyrequired
    The environment key, used to tie together flag configuration and users under one environment so they can be managed together.
    executionDate
    A unix epoch time in milliseconds specifying the date the scheduled changes will be applied

Environment

  • Post environmentPOST

    Create a new environment in a specified project with a given name, key, and swatch color.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    colorrequired
    A color swatch (as an RGB hex value with no leading '#', e.g.
    keyrequired
    A project-unique key for the new environment.
    namerequired
    The name of the new environment.
  • Get environmentGET

    Get an environment given a project and key.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    environmentKeyrequired
    The environment key, used to tie together flag configuration and users under one environment so they can be managed together.

Feature

  • Get feature flagsGET

    Get a list of all features in the given project.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    env
    By default, each feature will include configurations for each environment.
    summary
    By default in api version >= 1, flags will not include their list of prerequisites, targets or rules.
    archived
    When set to 1, only archived flags will be included in the list of flags returned.
  • Post feature flagPOST

    Creates a new feature flag.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    keyrequired
    A unique key that will be used to reference the flag in your code.
    namerequired
    A human-friendly name for the feature flag.
    variationsrequired
    An array of possible variations for the flag.
Show 10 more groups

Member

  • Get membersGET

    Returns a list of all members in the account.

    limit
    The number of objects to return.
    offset
    Where to start in the list.
    filter
    A comma-separated list of filters.
    sort
    A comma-separated list of fields to sort by.
  • Post membersPOST

    Invite new members.

    body
    The request body.

Reset

  • Reset environment sdkkeyPOST

    Reset an environment's SDK key with an optional expiry time for the old key.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    environmentKeyrequired
    The environment key, used to tie together flag configuration and users under one environment so they can be managed together.
    expiry
    An expiration time for the old environment SDK key, expressed as a Unix epoch time in milliseconds.
  • Reset environment mobile keyPOST

    Reset an environment's mobile key. The optional expiry for the old key is deprecated for this endpoint, so the old key will always expire immediately.

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    environmentKeyrequired
    The environment key, used to tie together flag configuration and users under one environment so they can be managed together.
    expiry
    The expiry parameter is deprecated for this endpoint, so the old mobile key will always expire immediately.

Approval

  • Get approval requestsGET

    Get all approval requests for a feature flag config

    projectKeyrequired
    The project key, used to tie the flags together under one project so they can be managed together.
    featureFlagKeyrequired
    The feature flag's key.
    environmentKeyrequired
    The environment key, used to tie together flag configuration and users under one environment so they can be managed together.

Destination

  • Get destinationsGET

    Returns a list of all data export destinations.

Event

  • Get eventsGET

    Get events usage endpoints.

Integration

  • Get integrationsGET

    Get a list of all configured audit log event integrations associated with this account.

Mau

  • Get mauGET

    Get monthly active user data.

Mauby

  • Get mauby categoryGET

    Get monthly active user data by category.

Stream

  • Get streamsGET

    Returns a list of all streams.

Token

  • Get tokensGET

    Returns a list of tokens in the account.

    showAll
    If set to true, and the authentication access token has the "Admin" role, personal access tokens for all members will be retrieved.

Ask your AI

Try one of these requests with a connected AI.

  • Show me the project in LaunchDarkly
  • Post a project in LaunchDarkly
  • Post an environment in LaunchDarkly
  • Show me the environment in LaunchDarkly
  • Delete a project in LaunchDarkly
  • Show me the event in LaunchDarkly

LaunchDarkly MCP server, hosted by ahel

One hosted endpoint serves LaunchDarkly. There is nothing to install and no local server to run.

Connect LaunchDarkly to Claude, Claude Code, Cursor or Codex

  1. Add your LaunchDarkly key. ahel stores it encrypted.
  2. Paste one link into your AI: https://mcp.ahel.ai (once, for every app).
  3. Ask for the work. Your AI picks the action and ahel runs it with your key.

Documentation

About LaunchDarkly

LaunchDarkly is a developer tools service. Connect your own key and your AI can get projects, post projects and post environments.

LaunchDarkly over MCP: ahel serves LaunchDarkly to Claude, Claude Code, Cursor and Codex as one hosted MCP endpoint. There is no local server to run. Add your LaunchDarkly key once, paste one link into your AI, and the actions above are there.

Developer tools

Questions

Is my LaunchDarkly key safe?

Your LaunchDarkly key is sealed in ahel and added to the request server-side when your AI calls LaunchDarkly. It never crosses the MCP link, no tool can read it back, and you can turn the app off or remove the key at any time.

Which AIs can use LaunchDarkly through ahel?

Any MCP-capable AI: Claude, Claude Code, Codex, Cursor, VS Code and others. Paste one link, https://mcp.ahel.ai, into the AI once and everything in your gateway arrives through it.

What can my AI do with LaunchDarkly?

24 actions today, covering projects, flags and environments. Ask in plain language; your AI picks the action and ahel runs it with your key.

Does connecting LaunchDarkly cost anything?

Connecting apps is free during ahel's early access. Free, Pro and Team all cost nothing today, and the pricing page lists what each one includes. LaunchDarkly may bill you for API use under its own terms.