Deploy

Also for this capability: API · CLI · MCP · SDKs

deploy: 21 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Arguments

op — what each one does:

• get_deploy_account_can_i — Always answers yes, whatever resource, action or subresource the path names.
• list_deploy_applications — Returns the fleet as an argocd ApplicationList: one projected Application per operator App CR, carrying the image tag…
• get_deploy_application — Returns ONE projected argocd Application by name, with status.resources filled in from its reconciled resource tree…
• get_deploy_application_resource_tree — Returns one application's argocd ApplicationTree: the objects the operator reconciled from its App CR, reached by…
• get_deploy_application_revision_metadata — Returns the argocd RevisionMetadata for one revision of one application — what the detail view shows beside a…
• list_deploy_application_syncwindows — Returns one application's argocd ApplicationSyncWindowState — the answer to "is anything blocking a sync of this…
• get_deploy_callback — Completes the redirect from IAM: it validates state against the single-use flow cookie in constant time, redeems the…
• list_deploy_clusters — Returns the argocd ClusterList of the destinations the caller's applications reconcile into: one entry per distinct…
• list_deploy_gitops — Lists every Hanzo CD Application in the cluster: the git source each one polls, the commit it last APPLIED, how its…
• get_deploy_health — Reports the plane's real reachability: 200 only when the Kubernetes API server answers AND the App CRD is served, 503…
• get_deploy_login — Redirects the browser to IAM's authorize endpoint, having minted a nonce and a PKCE verifier into a short-lived…
• 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…
• list_deploy_settings — Returns the argocd AuthSettings object the dashboard SPA awaits before its first render.
• list_deploy_stream_applications — Holds the connection open as text/event-stream and pushes one watch event per application change.
• get_deploy_stream_application_resource_tree — Holds the connection open as text/event-stream and pushes the application's whole resource tree — its live child…
• get_deploy_version — Returns the argocd VersionMessage the dashboard SPA reads at bootstrap.
• rollback_deploy_application — Performs exactly what the sync action performs: it stamps the sync-requested timestamp onto the application's App CR…
• sync_deploy_application — Requests an immediate reconcile of one application by stamping a sync-requested timestamp onto its App CR, which the…
• create_deploy_logout — Clears this console's session cookie and answers the signed-out state with the sign-in URL to start again.
• create_deploy_reconcile — Runs one full GitOps sync through the embedded engine — render the configured repo, ref and path, then three-way…

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.

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": "get_deploy_account_can_i"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> 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 →

The operation behind it

deploy dispatches to 21 operations. 5 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.

The same capability over plain HTTP is in the deploy API reference, on https://api.hanzo.ai.

All 121 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 121 tools captured 2026-08-16.