Available tools
Every MCP tool, what it does, and the permission it requires.
An assistant can only call a tool when both conditions hold:
- The tool is enabled under Settings → MCP → Exposed tools (a server-wide ceiling), and
- The API key holds the listed permission.
If either fails, the call is refused and the refusal is written to your activity log.
Projects
| Tool | What it does | Requires |
|---|---|---|
list_projects | Lists all projects with their status | projects: read |
get_project | Configuration and metadata for one project | projects: read |
get_project_status | Live running state of a project and its containers | projects: read |
get_logs | Recent log output for a project service | projects: read |
start_project | Starts a stopped project | projects: write |
stop_project | Stops a running project | projects: write |
restart_project | Restarts a project | projects: write |
create_project | Creates a new project | projects: write |
Backups
| Tool | What it does | Requires |
|---|---|---|
list_backups | Lists backups, optionally filtered by project | backups: read |
get_backup_status | Status of a single backup | backups: read |
create_backup | Starts a new backup for a project | backups: write |
Tasks
| Tool | What it does | Requires |
|---|---|---|
list_tasks | Lists scheduled tasks | tasks: read |
get_task | One scheduled task and its run history | tasks: read |
System
| Tool | What it does | Requires |
|---|---|---|
get_system_info | Host OS, versions, disk layout | system: read |
get_resources | Current CPU, memory and disk usage | system: read |
check_updates | Whether a Supascale update is available | system: read |
Not available
The following are not implemented as tools at all, so no setting can enable them:
- Deleting a project
- Restoring a backup
- Reading or writing cloud storage credentials
- Anything under project security scanning
Deletion and restore are irreversible. An assistant deciding to call one is a bad enough outcome that the right control is absence, not a checkbox someone might tick without thinking. If you need these, use the dashboard or the REST API.
Notes on specific tools
create_backup and create_project
Both can run for several minutes. Some MCP clients give up on a tool call after 60 seconds. If your assistant reports a timeout, the operation is usually still running — ask for the status separately rather than retrying, which would start a second one.
get_logs
Returns at most 1000 lines, and defaults to 100. Ask for a specific service (db, auth, storage, …) to narrow the output.
list_backups
Returns at most 100 entries and reports the total alongside them, so an assistant can tell the difference between "there are three backups" and "here are the three most recent of ninety".
Choosing permissions
A useful starting point:
| You want the assistant to… | Give it |
|---|---|
| Answer questions and diagnose | projects: read, backups: read, system: read |
| Also start/stop/restart | projects: write |
| Also take backups | backups: write |
Grant write only where you want the assistant acting on its own judgement. The permissions on the key are what actually decide this — the exposed-tool list can narrow it further but never widen it.