---
title: "What your AI tool can do"
description: "The tools the server offers, grouped by what they are for."
canonical: "https://docs.automo.build/mcp/what-it-can-do"
---

# What your AI tool can do

> The tools the server offers, grouped by what they are for.

The tools fall into four groups: handing work to Automo Build's agents, operating the platform, observing what is happening, and reviewing builder work.

## Hand work to Automo Build's agents

Ask a specialist instead of doing the work yourself. Builds run in parallel in the cloud while your tool carries on.

- `automo_ask_cto` — questions across your projects.
- `automo_run_doctor` — triage for deployments, drift and stuck sandboxes.
- `automo_ask_security` — scans, findings, access rules and secrets.
- `automo_run_qa` — drive the app like a user, or run a playbook.
- `automo_design_workflow` — turn "when X happens, do Y" into a standing workflow. Plan-gated.
- `automo_build` — hand a brief to a builder subagent that works in parallel. Returns a builder link.
- `automo_prompt_project` — one turn on the project's main agent, for foundational, sequential work. Queues behind a running turn.
- `automo_continue` — reply to or redirect any session.
- `automo_read_session` — read progress. Can wait up to 60 seconds.

## Operate the platform

- `automo_whoami`, `automo_list_workspaces`, `automo_switch_workspace` — who you are and which workspace you are in.
- `automo_search_projects`, `automo_get_project` — find projects and read their details. Environment variables are shown by name only, never values.
- `automo_create_project`, `automo_wake_sandbox`, `automo_merge_projects` — create and manage projects.
- `automo_list_branches`, `automo_merge_branch`, `automo_read_diff` — branches and changes.
- `automo_propose_deployment`, `automo_get_pending_publish` — prepare a publish.
- `automo_list_playbooks`, `automo_get_playbook`, `automo_run_playbook`, `automo_save_playbook` — playbooks.
- `automo_list_workflows`, `automo_get_workflow_runs` — workflows and their runs.

There are also tools for QA files and folders, and for sharing a preview link or a clone link.

## Observe

- `automo_turn_status` — whether a turn is still running.
- `automo_read_project_chat` — the project's chat.
- `automo_preview_screenshot` — a screenshot of the preview.
- `automo_get_project_status` — the project's current state.
- `automo_about` — about the server.

You can also read deployment history, security findings, playbook run screenshots and workspace activity.

## Review builder work

- `automo_list_reviews`, `automo_get_review` — see reviews and their verdicts.
- `automo_run_reviewer`, `automo_apply_review_fixes` — run a review and apply its fixes.
- `automo_approve_review`, `automo_promote`, `automo_cancel_review` — approve, promote or cancel.

## What stays in the app

Plan approval, deployment approval, design mode, review settings and billing stay in the app. Raw sandbox logs are not exposed; ask the Doctor instead.

> [!tip] There is no "ping" tool. Do not create test projects or send hello prompts to check the connection: they cost credits.