formae-mcp

Use when the user wants to add support for a new resource type to an existing formae plugin

Use when the user wants to check for infrastructure drift, see what changed out-of-band, or absorb/overwrite out-of-band changes into their IaC codebase

Use when the user wants to bring unmanaged/discovered resources under formae management, import resources into their IaC codebase, or absorb cloud resources into existing forma files

Use when the user wants to rename a managed resource, relabel a resource, change a resource's label, or give a discovery-named resource a readable name — a rename on its own never destroys or recreates the cloud object

Use when the user wants to deploy infrastructure, apply a forma file, reconcile a stack, update a stack, or make planned infrastructure changes

Use when the user wants to start authoring formae infrastructure or deploy something NEW with formae — e.g. 'I want to deploy X with formae', 'build a k8s app with formae', 'set up infrastructure for Y', 'create a new forma file for my service', 'write formae IaC for Z'. The front door that triages where the work happens, sets up plugin schema deps, and dispatches to focused authoring skills. NOT for applying an existing forma file (use formae-apply) or operating existing infra.

Use when the user wants to add or remove a plugin schema dependency in an existing formae project's PklProject — e.g. 'add the grafana plugin', 'I need cloudflare DNS', 'drop the azure dependency'.

Use when the user wants to find unmanaged resources in their cloud accounts, see what's not managed by formae, or run a discovery scan

Use when the user needs to make an urgent targeted infrastructure change, hotfix, incident response fix, or patch without a full reconcile

Use when the user wants to set, remove, or inspect a TTL or auto-reconcile policy on a stack — e.g. 'expire X in 20 minutes', 'reject out-of-band changes on Y', 'auto-reconcile production every 5 minutes', 'remove the TTL on dev', 'what policies are on lifeline?'

Use when the user wants to create a new formae resource plugin, build a provider integration, or extend formae with support for a new cloud service

Use when the user wants to start a brand-new formae project from scratch (no existing IaC codebase) — scaffolds a project with `formae project init`, infers the plugin schema dependencies from the user's intent, and sets up the file structure.

Use when the user is deciding how to group resources into stacks, where to draw stack boundaries, or how stacks/targets/policies relate — stack design and reconciliation-boundary guidance.

Use when the user wants to switch, list, save, edit, delete, or compare formae configuration profiles in ~/.config/formae/

Use when the user wants to destroy, delete, or tear down infrastructure resources, stacks, or environments

Use when the user asks about deployed infrastructure, what resources exist, resource counts, or wants to find specific resources by type, stack, label, or management status

Use when the user asks about their infrastructure stacks, how infrastructure is organized, or needs a stack overview with resource counts

Use when the user asks about running commands, deployment progress, recent operations, command history, or what failed

Use when the user asks about their cloud targets, configured regions, provider accounts, or which cloud accounts are set up