MCP tools
ShipSquares ships a first-class MCP server (Model Context Protocol) so AI agents — and the built-in assistant — can operate the platform. It runs over streamable HTTP with API-key authentication, is RBAC-bound (every tool call re-enters the API as the caller, with the caller’s permissions), and audits every mutation.
Because the MCP tools call the same REST surface as the dashboard, an agent can do anything a user can — and nothing they can’t.
Available tools
Section titled “Available tools”| Tool | Does |
|---|---|
list_apps | List the apps in the active organization. |
get_status | Report an app’s current status and latest deployment. |
deploy_app | Trigger a deployment (from GitHub, an image, or the catalog). |
rollback | Roll an app back to a previous image. |
tail_logs | Stream build/runtime logs. |
set_env | Set environment variables and secrets (write-only). |
add_domain | Attach a custom domain (certificate issued automatically). |
Managed Email and other first-class surfaces expose their own tools as those features are enabled on your control plane.
Connecting
Section titled “Connecting”Point an MCP-capable client at your control plane’s /mcp endpoint and authenticate with
a scoped API key (ss_live_…). The agent then operates strictly within that key’s role —
see Security for the permission model.