Formae MCP Server
platform-engineering-labs/formae-mcp
Infraestrutura como código com IA integrada no Claude Code
Ver no GitHubServidor MCP e skills de IA para a plataforma Infrastructure-as-Code formae. Fornece 15 ferramentas MCP para consultar e gerenciar infraestrutura em nuvem, além de 13 skills que ensinam ao assistente de codificação IA como executar workflows comuns de infraestrutura através da formae.
Instalação
npx convez-ai platform-engineering-labs/formae-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerenciar stacks de infraestrutura e recursos em nuvem via IA
- Descobrir e importar recursos não gerenciados em contas cloud
- Aplicar patches direcionados e reconciliações de infraestrutura
- Detectar e resolver drift de código com políticas TTL e auto-reconciliação
- Scaffolding e desenvolvimento de plugins de recursos formae
Veredito

Ferramenta enterprise-grade para DevOps que integra gerenciamento de infraestrutura com capacidades de IA do Claude. Exige conhecimento profundo em IaC e arquitetura cloud, ideal para equipes de platform engineering.
README
A tradução para o português deste README ainda está na fila.
formae-mcp
MCP server and AI coding skills for the Infrastructure-as-code (IaC) platform formae. Provides 15 MCP tools for querying and managing cloud infrastructure, plus 13 skills that teach your AI coding assistant how to perform common infrastructure workflows through formae.
Prerequisites
- Go 1.25+
- A running formae agent (
formae agent start)
Installation
Claude Code (via Plugin Marketplace)
Register the marketplace:
/plugin marketplace add platform-engineering-labs/formae-marketplace
Install the plugin:
/plugin install formae-mcp@formae-marketplace
Run /reload-plugins (Claude Code v2.1.116+) to apply the install without restarting your session. On older versions, restart Claude Code instead. The MCP server binary is built automatically on first use.
Verify by asking Claude to run /formae-status.
Claude Code (manual)
If you prefer not to use the marketplace:
-
Clone the repo:
git clone https://github.com/platform-engineering-labs/formae-mcp.git ~/.claude/plugins/formae-mcp -
Start Claude Code with the plugin directory:
claude --plugin-dir ~/.claude/plugins/formae-mcp
The MCP server binary is built automatically on first use.
Codex
See .codex/INSTALL.md for Codex-specific installation instructions.
OpenCode
See .opencode/INSTALL.md for OpenCode-specific installation instructions.
Available Skills
| Skill | Description |
|---|---|
formae-status | Check running commands, deployment progress, recent operations, and failures |
formae-stacks | View infrastructure stacks, organization, and resource counts |
formae-resources | Query deployed resources by type, stack, label, or management status |
formae-targets | List cloud targets, configured regions, and provider accounts |
formae-plugins | List installed plugins, supported providers, and resource types |
formae-apply | Deploy infrastructure by applying a forma file or reconciling a stack |
formae-patch | Make targeted infrastructure changes without a full reconcile |
formae-destroy | Tear down infrastructure resources, stacks, or environments |
formae-fix-code-drift | Check for out-of-band changes and decide whether to absorb or overwrite |
formae-policy | Set, remove, or inspect TTL and auto-reconcile policies on a stack |
formae-discover | Find unmanaged resources in cloud accounts |
formae-import | Bring unmanaged/discovered resources under formae management |
formae-plugin-new | Scaffold a new formae resource plugin |
formae-plugin-add-resource | Add a new resource type to an existing plugin |
formae-config | Manage named formae configuration profiles in ~/.config/formae/ via the fcfg CLI |
Available MCP Tools
Read-Only
| Tool | Description |
|---|---|
list_resources | Query resources with optional filters |
list_stacks | Retrieve all stacks |
list_targets | Query configured cloud targets |
get_command_status | Get status of a specific command |
list_commands | List commands with optional query and filters |
get_agent_stats | Retrieve agent statistics |
check_health | Health check for the formae agent |
list_plugins | List active plugins |
list_changes_since_last_reconcile | List infrastructure changes since last reconcile |
extract_resources | Extract resources as PKL code |
list_policies | List standalone (reusable) policies and the stacks they're attached to |
Mutation
| Tool | Description |
|---|---|
apply_forma | Deploy or update infrastructure (reconcile or patch mode) |
destroy_forma | Remove infrastructure by file or query |
cancel_commands | Cancel running commands |
force_sync | Trigger immediate resource synchronization |
force_discover | Trigger immediate resource discovery |
force_check_ttl | Trigger an immediate TTL expiry sweep across all stacks |
force_reconcile_stack | Force a one-shot reconcile on a stack (requires auto-reconcile policy attached) |
create_inline_policy | Plan a TTL or auto-reconcile policy edit on a stack (returns snippet + insertion anchor; caller applies via Edit) |
Configuration
By default, formae-mcp connects to the formae agent at http://localhost:49684. To override this:
Environment variables (highest precedence):
export FORMAE_AGENT_URL=http://my-agent-host
export FORMAE_AGENT_PORT=8080
Config file (~/.config/formae/formae.conf.pkl):
amends "formae:/Config.pkl"
cli {
api {
url = "http://my-agent-host"
port = 8080
}
}
Precedence: environment variables > config file > defaults.