# Deploy URL: https://docs.hanzo.ai/docs/mcp-tools/deploy > deploy: 11 operations. Also for this capability: [API](https://docs.hanzo.ai/docs/openapi/deploy) · [CLI](https://docs.hanzo.ai/docs/cli/deploy) · **MCP** · [SDKs](https://docs.hanzo.ai/docs/sdks) deploy: 11 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema. | | | | ------------- | ----------------------------------------------------------- | | **Tool** | `deploy` | | **Address** | `https://api.hanzo.ai/v1/mcp` | | **Method** | `tools/call` (JSON-RPC 2.0) | | **Arguments** | 2, 1 required | | **Operation** | `GET /v1/deploy/health` · `GET /v1/deploy/session/userinfo` | | **Product** | [deploy](https://docs.hanzo.ai/docs/openapi/deploy) | ## Arguments | Field | Type | Required | Default | Values | Description | | ------- | -------- | -------- | ------- | ------ | --------------------------- | | `input` | `object` | — | — | — | arguments for the chosen op | | `op` | `string` | **yes** | — | — | one of the operations below | **`op`** — what each one does: - `list_deploy_applications` — Returns the fleet as an argocd ApplicationList: one projected Application per operator App CR, carrying the image tag the CR DECLARES, the tag actually RUNNING in the cluster's Deployment, the reconciled health, and the sync verdict those two produce (declared == running ⇒ Synced, both known and different ⇒ OutOfSync, either unknown ⇒ Unknown). - `get_deploy_application` — Returns ONE projected argocd Application by name, with status.resources filled in from its reconciled resource tree — which is what makes it the detail view rather than a row of the list. - `get_deploy_application_resource_tree` — Returns one application's argocd ApplicationTree: the objects the operator reconciled from its App CR, reached by ownerRef — the Deployment and, under it, the ReplicaSet and Pods, plus the Service, Ingress, HorizontalPodAutoscaler, PodDisruptionBudget and ConfigMaps it owns — each node carrying its parent edges and its health. - `get_deploy_application_revision_metadata` — Returns the argocd RevisionMetadata for one revision of one application — what the detail view shows beside a revision. - `list_deploy_application_syncwindows` — Returns one application's argocd ApplicationSyncWindowState — the answer to "is anything blocking a sync of this application right now?". - `list_deploy_clusters` — Returns the argocd ClusterList of the destinations the caller's applications reconcile into: one entry per distinct destination server, carrying the count of applications reconciling into it. - `get_deploy_health` — Reports whether this deployment can observe the delivery plane. - `list_deploy_projects` — Returns the argocd AppProjectList this console groups and filters applications by. - `get_deploy_session_userinfo` — Answers "is this browser signed in, and if not where does it sign in?" — the dashboard SPA's bootstrap question, and the only route on this plane that answers for an anonymous caller. - `rollback_deploy_application` — Serves the console's rollback control, and today it requests a reconcile and nothing more. - `create_deploy_logout` — Ends the console session on this host. `tools/list` declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside `input`, field by field, on the operation you name — ask `describe` for that. A `—` means MCP does not constrain the field. ## Call it A `tools/call` carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run. ```bash curl -X POST https://api.hanzo.ai/v1/mcp \ -H "Authorization: Bearer $HANZO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "deploy", "arguments": { "op": "list_deploy_applications" } } }' ``` Values are the operation's own defaults and enumerated values where it declares them, and a `` where neither source declares one. `tools/list` needs no credential; `tools/call` does — called without one MCP answers HTTP 200 with a JSON-RPC result whose `isError` is set and whose text says what was missing. [How to get a key →](https://docs.hanzo.ai/docs/mcp-tools#credentials) ## The operation behind it `deploy` dispatches to 11 operations. 2 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which `describe` resolves. | Operation | Route | Product | Summary | | ----------------------------- | --------------------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `get_deploy_health` | `GET /v1/deploy/health` | [deploy](https://docs.hanzo.ai/docs/openapi/deploy) | Reports whether this deployment can observe the delivery plane. | | `get_deploy_session_userinfo` | `GET /v1/deploy/session/userinfo` | [deploy](https://docs.hanzo.ai/docs/openapi/deploy) | Answers "is this browser signed in, and if not where does it sign in?" — the dashboard SPA's bootstrap question, and the only route on this plane that answers for an anonymous caller. | The same capability over plain HTTP is in the [deploy API reference](https://docs.hanzo.ai/docs/openapi/deploy), on `https://api.hanzo.ai`. --- [All 120 tools](https://docs.hanzo.ai/docs/mcp-tools/all-tools) · [MCP](https://docs.hanzo.ai/docs/mcp-tools) · [API reference](https://docs.hanzo.ai/docs/openapi) Generated from `tools/list` on `https://api.hanzo.ai/v1/mcp` — 120 tools captured 2026-09-30.