Your assistant can read why a deploy failed

The MCP server now lists deployments, reads any step's log with secrets redacted, and says which package logins a site is missing.

When a deploy fails, the first thing anybody asks is which step stopped and what it printed. An assistant connected to Shipways over MCP can now ask the same thing.

  • list-deployments finds deployments started anywhere: from the panel, from a push, from CI or from the assistant itself.
  • deployment-status names the step that stopped and quotes its last lines.
  • deployment-log reads any step's output in full.

Both redact secrets before anything leaves the panel.

A Composer or npm install that fails with 401, 403 or 404 on a private package usually means the machine has no login for that host. list-package-credentials says which hosts have one. Adding a login is still something a person does in the panel.

list-sites now also shows the source control account each site uses. When the organization already has an account for the repository's owner, it suggests that one.

Every change

One machine, free, for as long as you like

No card and no end date. Connect a spare box and watch it provision; everything it builds carries into whichever plan you move to.