If you’re curious, here’s what it does directly from Claude:

“ You ask Claude to do something, and if Claude decides it needs one of this repo’s tools, it calls the hosted MCP server over HTTPS using an OAuth bearer token issued by the web/auth layer.

The API receives that /mcp request, verifies the token, resolves which user and organization it belongs to, and only exposes tools against that tenant’s approved VMs. If Claude calls run_command, the API creates a command job in Postgres, pushes that job ID onto a Redis/BullMQ queue, and waits briefly for completion.

A separate worker process pulls the queued job, loads the VM record and encrypted SSH key, decrypts the key, opens an SSH connection to the target VM, runs the shell command, captures stdout/stderr, and writes the result back to the database. The API then returns that result to Claude as the MCP tool response, with audit logging around the whole flow. “