LaunchDarkly Automations Auto-archival Settings

You're using a skill that reads and changes a project's auto-archival settings, from the "Automatic archival" section of the project's Settings > Automations page. Auto-archival archives flags without a person in the loop unless approvals are required. 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: "archival" and projectKey: the project's archival settings and automationsPage, the link to the project's Automations page.
• update-automations with projectKey and an archival object: change one or more settings, or turn archival off. Omitted fields keep their stored values. Send archival on its own, without accountWide, repo, or cleanup. It cannot turn archival on (see Turn it on).

Optional: get-projects to pick the project, search-members to resolve notification member IDs (team keys come from the user), get-approval-requests for pending archival approvals.

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.

If a call fails with "automatic archival is not available for this account yet", the account does not have the feature. Tell the user and stop; do not retry or try other tools.

What the settings mean