SousChef
SousChef: Multi-Plattform-zu-Ansible-Migration + Ansible-Upgrade-Planung
Transformieren Sie Chef-, SaltStack-, Puppet-, PowerShell- und Bash-Automatisierungen zu Ansible und planen Sie Ansible-Versions-Upgrades. Funktioniert mit jedem KI-Assistenten via MCP (Model Context Protocol) – Claude, GPT-4, GitHub Copilot, Red Hat AI, lokale Modelle und mehr.
Kurzfakten: MIT-Lizenz | Python 3.10+ | 95 MCP-Tools | 91% Testabdeckung
Warnung Ich habe nicht 100.000 Zeilen Code in zwei Tagen von Hand geschrieben, während ich meinen eigentlichen Vollzeitjob ausübte (der übrigens nicht dieser hier ist). Vieles davon ist KI-generiert. Architektonisch geplant, manuell bearbeitet und persönlich verflucht – ja, aber die starke Hand der KI ist in diesem Repository überall zu spüren.
Ich habe es so weit vorangetrieben, dass es eine Menge Tests enthält, und ich teste es gründlich, bevor ich Änderungen pushe, aber manche Dinge könnten kaputtgehen oder waren schon immer kaputt. Wenn Sie etwas finden, melden Sie es, und ich werde es beheben.
Ein guter Teil davon basiert auf gemockten Chef/AWX/AAP-APIs, da ich – überraschenderweise – nicht über eine Flotte von Unternehmensinstallationen mit Unternehmensdaten verfüge, um dagegen zu testen. Käufer aufgepasst (doppelt so sehr, da Sie eigentlich nichts gekauft haben).
Was es tut
Chef-zu-Ansible-Migration — Konvertieren Sie Cookbooks, Rezepte, benutzerdefinierte Ressourcen, Data Bags und Habitat-Pläne in Ansible-Playbooks, -Rollen und -Container. Unterstützt Infrastruktur, Anwendungen und Day-2-Operationen.
SaltStack-zu-Ansible-Migration — Konvertieren Sie Salt-States, Pillars und top.sls-Targeting in Ansible-Rollen, Variablendateien, Ansible Vault und INI-Inventare. Bewerten Sie die Komplexität, erstellen Sie phasenweise Migrationspläne und generieren Sie Management-Berichte.
Puppet-zu-Ansible-Migration — Konvertieren Sie Puppet-Manifeste und Modulverzeichnisse in Ansible-Playbooks unter Verwendung idiomatischer ansible.builtin-Module. Erkennt 14 Puppet-Ressourcentypen; bildet 10 auf Ansible-Module ab, mit KI-gestützter Konvertierung für komplexe Konstrukte.
PowerShell-zu-Ansible-Migration — Konvertieren Sie Windows PowerShell-Bereitstellungsskripte in idiomatische ansible.windows-Playbooks, -Rollen, WinRM-Inventare und AWX/AAP-Job-Templates.
Bash-Skript-Migration — Konvertieren Sie bereitstellende Bash-Skripte in Ansible-Playbooks und -Rollen mit Qualitätsbewertung, Erkennung sensibler Daten und Hinweisen zur AAP-Bereitschaft.
Ansible-Upgrade-Planung — Bewerten Sie die Kompatibilität, planen Sie Versions-Upgrades, validieren Sie Collections, identifizieren Sie Breaking Changes und generieren Sie Teststrategien.
Related MCP server: AAP MCP Server
Installation & Einrichtung
# Install from PyPI
pip install mcp-souschef
# Configure your MCP client (Claude Desktop example)
cp config/claude-desktop.json ~/Library/Application\ Support/Claude/claude_desktop_config.json
# Restart your AI assistant and start using
# Ask: "What migration tools are available?"Andere MCP-Clients: Siehe config/CONFIGURATION.md für VS Code Copilot, benutzerdefinierte Setups und Docker-Bereitstellung.
Hauptmerkmale
95 MCP-Tools für Chef-Migration, SaltStack-Migration, Puppet-Migration, PowerShell-Migration, Bash-Skript-Migration und Ansible-Upgrades
Web-UI mit interaktivem Migrationsplaner und Visualisierung (einschließlich Salt-, Puppet-, PowerShell- und Bash-Tabs)
CLI für Automatisierung und CI/CD-Integration
Produktionsbereit mit 91% Testabdeckung und umfassender Validierung
Modell-agnostisch — funktioniert mit jedem KI-Assistenten, der MCP unterstützt
Chef-Server-Ingestion mit Abhängigkeitsabschluss und Offline-Bundle-Export
Häufige Anwendungsfälle
Chef-Migration:
Konvertieren Sie Cookbooks in Ansible-Playbooks und -Rollen
Migrieren Sie Chef Habitat-Apps zu Docker-Containern
Transformieren Sie Data Bags zu Ansible Vault
Generieren Sie AWX/AAP-Job-Templates und Workflows
Konvertieren Sie InSpec-Tests in Ansible-Validierungsaufgaben
Rufen Sie Cookbooks vom Chef-Server mit
run_listoder Policy-Auswahl ab
SaltStack-Migration:
Parsen Sie SLS-State-Dateien und extrahieren Sie States, Pillars und Grain-Referenzen
Konvertieren Sie Salt-States in Ansible-Playbooks und Rollen-Task-Dateien
Migrieren Sie Pillar-Daten zu Ansible
group_vars/und Ansible VaultGenerieren Sie Ansible-Inventare aus
top.sls-Targeting-RegelnBatch-Konvertierung eines vollständigen Salt-State-Trees in eine Ansible-Rollenstruktur
Bewerten Sie die Migrationskomplexität und erstellen Sie phasenweise Migrationspläne
Puppet-Migration:
Konvertieren Sie Puppet-Manifeste (
.pp) und Modulverzeichnisse in Ansible-PlaybooksErkennen Sie 14 Puppet-Ressourcentypen; bilden Sie 10 auf idiomatische
ansible.builtin-Module ab (package,service,file,user,group,exec,cron,host,mount,ssh_authorized_key)Warnen Sie vor nicht unterstützten Konstrukten (Hiera-Lookups, exportierte Ressourcen,
create_resources) mit Anleitungen zur manuellen ÜberprüfungKI-gestützte Konvertierung für komplexe Puppet-DSL, die nicht automatisch abgebildet werden kann
Konvertieren Sie einzelne Puppet-Ressourcendeklarationen in eigenständige Ansible-Tasks
PowerShell-Migration:
Konvertieren Sie Windows PowerShell-Bereitstellungsskripte in idiomatische Ansible-Playbooks
Generieren Sie vollständige Ansible-Rollen mit WinRM-Inventar und
group_varsBilden Sie über 28 PowerShell-Muster auf
ansible.windows.*,community.windows.*,chocolatey.chocolatey.*abGenerieren Sie AWX/AAP-Windows-Job-Templates mit WinRM-Anmeldeinformationen
Analysieren Sie die Migrationstreue (0–100 %) mit umsetzbaren Empfehlungen
Erstellen Sie vollständige
requirements.ymlfür erforderliche Windows-Collections
Bash-Skript-Migration:
Konvertieren Sie bereitstellende Bash-Skripte in idiomatische Ansible-Playbooks
Generieren Sie vollständige Ansible-Rollen aus Bash-Skripten (Tasks, Handler, Defaults, Meta)
Erkennen und markieren Sie hartcodierte Secrets mit
ansible-vault-AnleitungIdentifizieren Sie CM-Escape-Aufrufe (Salt, Puppet, Chef), die in Bash eingebettet sind
Erhalten Sie AAP-fertige Job-Template-Hinweise mit Empfehlungen für Execution Environments
Bewerten Sie die Migrationsqualität (A–F) mit gerankten Verbesserungsvorschlägen
Ansible-Upgrades:
Bewerten Sie die Python- und Ansible-Versionskompatibilität
Planen Sie Upgrades mit Analyse von Breaking Changes
Validieren Sie die Collection-Kompatibilität
Generieren Sie Teststrategien
Verfolgen Sie End-of-Life-Daten
Sowohl Infrastruktur als auch Anwendungen:
Infrastrukturbereitstellung und -konfiguration
Automatisierung der Anwendungsbereitstellung
Day-2-Operationen (Backups, Skalierung, Updates)
CI/CD-Pipeline-Migration
Multi-Cloud-Automatisierung
Befehlszeilenbeispiele
# Chef migration
souschef-cli recipe /path/to/recipe.rb
souschef-cli template /path/to/template.erb
souschef-cli convert package nginx --action install
# SaltStack migration
souschef-cli salt assess /srv/salt/states/
souschef-cli salt convert /srv/salt/states/webserver/init.sls
souschef-cli salt inventory /srv/salt/top.sls
souschef-cli salt batch-convert /srv/salt/states/ --output-dir ./ansible-roles/
# PowerShell migration
souschef-cli powershell-parse scripts/setup.ps1
souschef-cli powershell-convert scripts/setup.ps1 --output playbook.yml
souschef-cli powershell-role scripts/setup.ps1 --output-dir ./ansible-role
# Puppet migration
souschef-cli puppet parse manifests/site.pp
souschef-cli puppet convert manifests/site.pp --output playbook.yml
souschef-cli puppet convert-module modules/myapp --output-dir ./ansible-role
# Bash script migration
souschef bash parse scripts/bootstrap.sh
souschef bash convert scripts/deploy.sh --output playbook.yml
souschef bash role scripts/setup.sh --role-name myapp --output-dir ./roles
# Ansible upgrades
souschef ansible assess --environment-path /path/to/ansible
souschef ansible plan --current 2.9 --target 2.17
souschef ansible validate-collections --requirements-file requirements.yml
# Web UI
souschef ui # Launch interactive dashboardDokumentation
Hier starten
Quick Start Guide — In 5 Minuten einsatzbereit
Produktionssicherheit — Validieren Sie Migrationen vor der Bereitstellung ⚠️
Benutzerhandbuch — Alle 95 Tools mit Beispielen erklärt
Chef-Migrationsleitfaden — Schritt-für-Schritt-Prozess der Chef-zu-Ansible-Migration
Salt-Migrationsleitfaden — Schritt-für-Schritt-Prozess der SaltStack-zu-Ansible-Migration
Bash-Migrationsleitfaden — Schritt-für-Schritt-Prozess der Bash-Bereitstellungsskript-Migration
Puppet-Migrationsleitfaden — Puppet-zu-Ansible-Konvertierung
PowerShell-Migrationsleitfaden — PowerShell-zu-Windows-Ansible-Konvertierung
Ansible-Upgrades — Workflows zur Planung von Versions-Upgrades
Referenz
API-Dokumentation — Vollständige technische Referenz
Architekturleitfaden — Codestruktur und Designentscheidungen
Beitragsleitfaden — Entwicklungsstandards und Workflow
Sicherheitsrichtlinie — Schwachstellenmeldung und Sicherheitsfunktionen
Changelog — Vollständige Release-Historie
Aktuelle Updates
v7.0.0 — Erstklassige Multi-Plattform-Migrationsdokumentation für SaltStack, Bash, PowerShell und Puppet
v6.0.0 — v2-Kernfundament mit erweiterten Migrationsfähigkeiten
v5.1.4 — Modulare Architektur, 91% Testabdeckung, vollständige Typsicherheit, produktionsbereit
v5.0.0 — Vollständige Ansible-Upgrade-Planung mit Versionsmatrizen und EOL-Tracking
Mitwirken
# Development setup
git clone https://github.com/kpeacocke/souschef.git && cd souschef
poetry install
poetry run pytest # Run tests
poetry run ruff check . # Lint
poetry run mypy souschef # Type check
# If you change terraform-provider/
cd terraform-provider
go test ./... # Run Go testsStandards: Null-Warnungen-Richtlinie, Typ-Hinweise erforderlich, 90%+ Testabdeckung, australische englische Rechtschreibung.
Siehe CONTRIBUTING.md für vollständige Richtlinien.
Support
Issues: GitHub Issues
Diskussionen: GitHub Discussions
Sicherheit: Siehe SECURITY.md
Lizenz
MIT-Lizenz — siehe LICENSE für Details.
Available Tools
34 toolsanalyze_chef_application_patternsC
Analyze Chef cookbook for application deployment patterns and provide migration recommendations.
Args: cookbook_path: Path to Chef application cookbook application_type: Type of application (web_application, microservice, database, etc.)
Returns: Analysis of deployment patterns with Ansible migration recommendations
Inputs: cookbook_path (required), application_type. Returns: result
analyze_chef_databag_usageA
Analyze Chef cookbook for data bag usage and provide migration recommendations.
Args: cookbook_path: Path to Chef cookbook databags_path: Optional path to data_bags directory for cross-reference
Returns: Analysis of data bag usage and migration recommendations
Inputs: cookbook_path (required), databags_path. Returns: result
analyze_chef_environment_usageC
Analyze Chef cookbook for environment usage and provide migration recommendations.
Args: cookbook_path: Path to Chef cookbook environments_path: Optional path to environments directory for cross-reference
Returns: Analysis of environment usage and migration recommendations
Inputs: cookbook_path (required), environments_path. Returns: result
analyze_chef_search_patternsC
Analyze Chef recipes/cookbooks to extract search patterns for inventory planning.
Args: recipe_or_cookbook_path: Path to Chef recipe file or cookbook directory.
Returns: JSON string with discovered search patterns and recommended inventory structure.
Inputs: recipe_or_cookbook_path (required). Returns: result
analyze_cookbook_dependenciesC
Analyze cookbook dependencies and identify migration order requirements.
Args: cookbook_path: Path to Chef cookbook or cookbooks directory dependency_depth: Analysis depth (direct, transitive, full)
Returns: Dependency analysis with migration order recommendations
Inputs: cookbook_path (required), dependency_depth. Returns: result
assess_chef_migration_complexityC
Assess the complexity of migrating Chef cookbooks to Ansible with detailed analysis.
Args: cookbook_paths: Comma-separated paths to Chef cookbooks or cookbook directory migration_scope: Scope of migration (full, recipes_only, infrastructure_only) target_platform: Target platform (ansible_awx, ansible_core, ansible_tower)
Returns: Comprehensive migration complexity assessment with recommendations
Inputs: cookbook_paths (required), migration_scope, target_platform. Returns: result
convert_chef_databag_to_varsB
Convert Chef data bag to Ansible variables format.
Args: databag_content: JSON content of the Chef data bag databag_name: Name of the data bag item_name: Name of the data bag item (default: "default") is_encrypted: Whether the data bag is encrypted target_scope: Variable scope ("group_vars", "host_vars", or "playbook")
Returns: Ansible variables YAML content or vault file structure
Inputs: databag_content (required), databag_name (required), item_name, is_encrypted, +1 more. Returns: result
convert_chef_deployment_to_ansible_strategyA
Convert Chef application deployment recipe to Ansible deployment strategy.
Args: deployment_recipe_path: Path to Chef deployment recipe deployment_pattern: Chef deployment pattern (blue_green, rolling, canary, auto_detect) target_strategy: Target Ansible strategy (rolling_update, blue_green, canary)
Returns: Ansible playbook with deployment strategy implementation
Inputs: deployment_recipe_path (required), deployment_pattern, target_strategy. Returns: result
convert_chef_environment_to_inventory_groupA
Convert Chef environment to Ansible inventory group with variables.
Args: environment_content: Ruby content of the Chef environment file environment_name: Name of the Chef environment include_constraints: Whether to include cookbook version constraints
Returns: Ansible inventory group configuration with variables
Inputs: environment_content (required), environment_name (required), include_constraints. Returns: result
convert_chef_search_to_inventoryA
Convert a Chef search query to Ansible inventory patterns and groups.
Args: search_query: Chef search query (e.g., "role:web AND environment:production").
Returns: JSON string with Ansible inventory patterns and group definitions.
Inputs: search_query (required). Returns: result
convert_inspec_to_testC
Convert InSpec controls to Ansible test format.
Args: inspec_path: Path to InSpec profile or control file. output_format: Output format ('testinfra' or 'ansible_assert').
Returns: Converted test code or error message.
Inputs: inspec_path (required), output_format. Returns: result
convert_resource_to_taskB
Convert a Chef resource to an Ansible task.
Args: resource_type: The Chef resource type (e.g., 'package', 'service'). resource_name: The name of the resource. action: The Chef action (e.g., 'install', 'start', 'create'). Defaults to 'create'. properties: Additional resource properties as a string representation.
Returns: YAML representation of the equivalent Ansible task.
Inputs: resource_type (required), resource_name (required), action, properties. Returns: result
generate_ansible_vault_from_databagsB
Generate Ansible Vault files from Chef data bags directory.
Args: databags_directory: Path to Chef data_bags directory output_directory: Target directory for Ansible variables (group_vars/host_vars) encryption_key_hint: Hint for identifying encrypted data bags
Returns: Summary of converted data bags and instructions
Inputs: databags_directory (required), output_directory, encryption_key_hint. Returns: result
generate_awx_inventory_source_from_chefB
Generate AWX/AAP inventory source from Chef server configuration.
Args: chef_server_url: Chef server URL for inventory sync organization: AWX organization name sync_schedule: Inventory sync schedule (hourly, daily, weekly)
Returns: AWX/AAP inventory source configuration for Chef server integration
Inputs: chef_server_url (required), organization, sync_schedule. Returns: result
generate_awx_job_template_from_cookbookB
Generate AWX/AAP job template configuration from Chef cookbook.
Args: cookbook_path: Path to Chef cookbook directory cookbook_name: Name of the cookbook for job template target_environment: Target environment for the job template include_survey: Whether to include survey spec for cookbook attributes
Returns: AWX/AAP job template JSON configuration
Inputs: cookbook_path (required), cookbook_name (required), target_environment, include_survey. Returns: result
generate_awx_project_from_cookbooksA
Generate AWX/AAP project configuration from Chef cookbooks directory.
Args: cookbooks_directory: Path to Chef cookbooks directory project_name: Name for the AWX project scm_type: SCM type (git, svn, etc.) scm_url: SCM repository URL
Returns: AWX/AAP project configuration with converted playbooks structure
Inputs: cookbooks_directory (required), project_name (required), scm_type, scm_url. Returns: result
generate_awx_workflow_from_chef_runlistC
Generate AWX/AAP workflow template from Chef runlist.
Args: runlist_content: Chef runlist content (JSON or comma-separated) workflow_name: Name for the workflow template environment: Target environment for workflow execution
Returns: AWX/AAP workflow template configuration with job dependencies
Inputs: runlist_content (required), workflow_name (required), environment. Returns: result
generate_blue_green_deployment_playbookB
Generate Ansible blue/green deployment playbook from application configuration.
Args: app_name: Name of the application to deploy service_config: JSON configuration for service setup health_check_url: URL endpoint for health checks
Returns: Complete blue/green deployment playbook with rollback capabilities
Inputs: app_name (required), service_config, health_check_url. Returns: result
generate_canary_deployment_strategyC
Generate Ansible canary deployment strategy with gradual rollout.
Args: app_name: Name of the application for canary deployment canary_percentage: Initial canary traffic percentage rollout_steps: Comma-separated rollout percentages
Returns: Canary deployment strategy with monitoring and automated rollback
Inputs: app_name (required), canary_percentage, rollout_steps. Returns: result
generate_dynamic_inventory_scriptA
Generate a Python dynamic inventory script from Chef search queries.
Args: search_queries: JSON string containing Chef search queries and group names.
Returns: Complete Python script for Ansible dynamic inventory.
Inputs: search_queries (required). Returns: result
generate_inspec_from_recipeA
Generate InSpec controls from a Chef recipe.
Args: recipe_path: Path to Chef recipe file.
Returns: InSpec control code or error message.
Inputs: recipe_path (required). Returns: result
generate_inventory_from_chef_environmentsB
Generate complete Ansible inventory from Chef environments directory.
Args: environments_directory: Path to Chef environments directory output_format: Output format ("yaml", "ini", or "both")
Returns: Complete Ansible inventory structure with environment-based groups
Inputs: environments_directory (required), output_format. Returns: result
generate_migration_planA
Generate a detailed migration plan from Chef to Ansible with timeline and milestones.
Args: cookbook_paths: Comma-separated paths to Chef cookbooks migration_strategy: Migration approach (big_bang, phased, parallel) timeline_weeks: Target timeline in weeks
Returns: Detailed migration plan with phases, milestones, and deliverables
Inputs: cookbook_paths (required), migration_strategy, timeline_weeks. Returns: result
generate_migration_reportC
Generate comprehensive migration report from assessment results.
Args: assessment_results: JSON string or summary of assessment results report_format: Report format (executive, technical, combined) include_technical_details: Include detailed technical analysis (yes/no)
Returns: Formatted migration report for stakeholders
Inputs: assessment_results (required), report_format, include_technical_details. Returns: result
generate_playbook_from_recipeA
Generate a complete Ansible playbook from a Chef recipe.
Args: recipe_path: Path to the Chef recipe (.rb) file.
Returns: Complete Ansible playbook in YAML format with tasks, handlers, and variables.
Inputs: recipe_path (required). Returns: result
list_cookbook_structureC
List the structure of a Chef cookbook directory.
Args: path: Path to the cookbook root directory.
Returns: Formatted string showing the cookbook structure.
Inputs: path (required). Returns: result
list_directoryC
List the contents of a directory.
Args: path: The path to the directory to list.
Returns: A list of filenames in the directory, or an error message.
Inputs: path (required). Returns: result
parse_attributesC
Parse a Chef attributes file and extract attribute definitions.
Args: path: Path to the attributes (.rb) file.
Returns: Formatted string with extracted attributes.
Inputs: path (required). Returns: result
parse_custom_resourceA
Parse a Chef custom resource or LWRP file.
Args: path: Path to the custom resource (.rb) file.
Returns: JSON string with extracted properties, actions, and metadata.
Inputs: path (required). Returns: result
parse_inspec_profileB
Parse an InSpec profile and extract controls.
Args: path: Path to InSpec profile directory or control file (.rb).
Returns: JSON string with parsed controls, or error message.
Inputs: path (required). Returns: result
parse_recipeB
Parse a Chef recipe file and extract resources.
Args: path: Path to the recipe (.rb) file.
Returns: Formatted string with extracted Chef resources and their properties.
Inputs: path (required). Returns: result
parse_templateA
Parse a Chef ERB template file and convert to Jinja2.
Args: path: Path to the ERB template file.
Returns: JSON string with extracted variables and Jinja2-converted template.
Inputs: path (required). Returns: result
read_cookbook_metadataC
Parse Chef cookbook metadata.rb file.
Args: path: Path to the metadata.rb file.
Returns: Formatted string with extracted metadata.
Inputs: path (required). Returns: result
read_fileC
Read the contents of a file.
Args: path: The path to the file to read.
Returns: The contents of the file, or an error message.
Inputs: path (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 34 tools
The tools have clear purposes focused on Chef-to-Ansible migration, but significant overlap exists between analysis tools (e.g., analyze_chef_application_patterns, analyze_chef_databag_usage, analyze_chef_environment_usage) and conversion tools (e.g., convert_chef_databag_to_vars, convert_chef_environment_to_inventory_group). While descriptions help differentiate, an agent might struggle to choose between similar analysis or conversion tools for specific migration tasks, leading to potential misselection.
Most tools follow a consistent verb_noun pattern (e.g., analyze_chef_application_patterns, convert_chef_databag_to_vars, generate_ansible_vault_from_databags), which aids predictability. However, there are minor deviations like list_directory and read_file, which use simpler verbs without the domain prefix, slightly breaking the pattern but remaining readable overall.
With 34 tools, the count is excessive for the Chef-to-Ansible migration domain. Many tools could be consolidated (e.g., multiple analysis and conversion tools overlap in functionality), making the set feel heavy and overwhelming. A more streamlined set of 10-20 tools would better serve the purpose without sacrificing coverage.
The tool set provides comprehensive coverage for Chef-to-Ansible migration, including analysis, conversion, generation of Ansible components (playbooks, inventory, vaults), integration with AWX/AAP, deployment strategies, and reporting. It supports full CRUD/lifecycle operations for the domain, with no obvious gaps that would cause agent failures in migration workflows.
Maintenance
Related MCP Connectors
DORA OS Conductor — 16-tool meta-orchestrator for DORA compliance workflow automation.
30+ deterministic dev and delivery tools: linting, metrics, diagrams, model advice, AI-text checks.
Evidence-first architecture workbench: 48 deterministic tools, 10 architect personas, any cloud
Detects database migration table locks, terraform cost leaks, and OWASP API flaws.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables comprehensive Ansible automation management through natural language, including playbook creation and execution, inventory management, role scaffolding, and project workflows. Supports both local inventories and full project lifecycle management with syntax validation and idempotency testing.30-
- FlicenseCqualityDmaintenanceEnables comprehensive management of Ansible Automation Platform Controller and Gateway through 17 specialized tools covering job execution, inventory management, workflows, credentials, user administration, and system monitoring.18-
- AlicenseNot gradedqualityDmaintenance36 enterprise MCP tools for AWS security, infrastructure generation, AI workflows, and agent governance. IAM validation, MFA compliance, CloudFormation/SAM generation, DynamoDB design, OAuth validation, vector embeddings, error analysis, data lake readiness, 12 ACI governance tools for AI agent safety, and 4 local interview tools.58 npmMIT
- AlicenseCqualityFmaintenanceEnables AI assistants to manage infrastructure using Ansible and Terraform with 58 tools for playbooks, provisioning, security scanning, and more.877MIT