---
id: w2/m2/t002
title: Expose deploy as an MCP verb
worker: worker2
status: done
estimate: 20m
depends_on: [w2/m2/t001, w2/m1/t001]
---

## Objective

Make "deploy this" a single agent action by registering `deploy` as an MCP tool over `Core.Deploy`.

## Context

- The MCP adapter and its `Core` wiring exist from w2/m1/t001; `Core.Deploy` exists from t001.
- Pillar 4: "one API call takes a repo + `bex.yml` to a live URL, so 'deploy this' is a single agent action."

## Steps

1. Register an MCP `deploy` tool with inputs `{repo, bex.yml}` delegating to `Core.Deploy`.
2. Return the service object (`id`, `phase`, `url`) so the agent can poll to Ready.

## Files

- `operator/cmd/mcp/main.go`

## Acceptance criteria

- [ ] An MCP client calls `deploy` with a repo + `bex.yml` and receives a service object it can poll until `status.url` is live.

## Out of scope

- Redeploy-on-push (t003).
