{"id":"gitrgoliveira-vagrant-mcp-server","name":"vagrant-mcp-server","af_score":45.2,"security_score":15.5,"reliability_score":17.5,"what_it_does":"Vagrant MCP Server (Go) provides an MCP server interface (stdio by default, SSE optional) that lets an AI agent create/manage Vagrant development VMs and run commands inside them, including host/VM file synchronization workflows and environment/tool setup. It is intended to run on the same host where Vagrant and a virtualization provider are installed so it can access the Vagrant CLI and virtualization drivers.","best_when":"You have trusted local workflows (e.g., VS Code with MCP), Vagrant and a provider installed on the same machine as the server, and you want agent-driven VM lifecycle + synchronized command execution for development.","avoid_when":"You need multi-tenant, remote, internet-exposed access, or you cannot guarantee trust boundaries; also avoid if you require a mature, stable, fully documented API surface (the README explicitly calls it a work in progress).","last_evaluated":"2026-04-04T19:45:29.534417+00:00","has_mcp":true,"has_api":false,"auth_methods":["None (server provides no authentication itself; relies on client/host integration trust model)"],"has_free_tier":false,"known_gotchas":["Requires direct host access to Vagrant CLI and virtualization providers; will not work inside Docker as stated.","No authentication: an agent/user compromise could trigger VM creation/destruction and command execution.","SSE transport should not be exposed publicly; risk increases if network boundaries are not controlled.","Tool behavior for conflicts/resolutions and sync timing is only described generally; agents may need to re-check sync status after operations."],"error_quality":0.0}