---
title: "What the MCP server does"
description: "Let the AI tool you already use operate Automo Build on your behalf."
canonical: "https://docs.automo.build/mcp/overview"
---

# What the MCP server does

> Let the AI tool you already use operate Automo Build on your behalf.

Automo Build runs a remote MCP server. Attach it to the AI tool you already use and that tool can operate Automo Build as you.

## Which tools

Claude Code, Claude.ai, ChatGPT, Codex, Cursor, Copilot, Cline, or your own agent. Any tool that speaks MCP can connect.

## What your tool can do

- Create projects.
- Hand off builds to cloud builders that run in parallel, off your machine.
- Ask the CTO, Doctor, Security and QA agents.
- Run playbooks.
- Prepare publishes.

See [What your AI tool can do](/mcp/what-it-can-do) for the full list.

## The idea

If Automo Build can do it, it happens in Automo Build. Your AI tool only does locally what Automo Build cannot.

## What you need

An Automo Build account. It is free to start: a trial, then a USD 0 Free plan with a monthly credit allowance. There is no anonymous use.

Nothing to install or run. It is a remote server, so you only add its address to your tool. See [Connecting your AI tool](/mcp/connecting-your-ai-tool).

## Listings and the docs server

The server is listed in the [official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=build.automo/automo-build) as `build.automo/automo-build`. Its setup helper is on npm as [automo-build](https://www.npmjs.com/package/automo-build).

These docs are also a public, read-only MCP server at `https://mcp.automo.build/docs`. No sign-in: any AI tool can search and read them.