LaunchDarkly Automations Auto-cleanup Settings

You're using a skill that reads and changes a project's auto-cleanup settings, from the "Automated flag cleanup" section of the project's Settings > Automations page. Auto-cleanup opens pull requests in the user's GitHub repositories on a schedule. Treat every write as production automation with a blast radius.

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server.

Required MCP tools:

• get-automations with section: "cleanup" and projectKey: the project's cleanup settings, the upcoming run (enabled, flagKeys, nextRunAt in Unix milliseconds), and automationsPage, the link to the project's Automations page.
• update-automations with projectKey and a cleanup object: change one or more settings. Omitted fields keep their stored values. Send cleanup on its own, without accountWide, repo, or archival.

Optional: get-projects to pick the project, get-automations to suggest the repositories already mapped to the project.

If get-automations has no section argument, or rejects section, the server has not picked up cleanup and archival yet. Ask the user to reconnect the LaunchDarkly MCP server once. If it still has none, guide the browser steps in references/browser-steps.md instead. Do not invent REST calls.

What the settings mean