Unbind

What an Agent Can Do

The tools an agent gets and how they map to the API.

The MCP server has no logic of its own. Every tool is an operation of the HTTP API, called the same way, with the same validation and the same permissions. If the API reference says an operation does something, the tool with that name does exactly that.

There are about 70 tools, and more than half of them only read.

What is covered

AreaExamples
Teams, projects, environmentslist-teams, create-project, reorder-projects, create-environment
Servicescreate-service, update-service, reorder-services, list-available-databases
GitHublist-github-installations, list-github-repositories, get-github-repository
Deploymentstrigger-deployment, get-deployment, redeploy-deployment, cancel-deployment
Variableslist-variables, update-variables, list-available-references
Volumescreate-volume, update-volume, get-volume-metrics
Templateslist-templates, deploy-template
Service groupscreate-service-group, update-service-group-template-inputs
Logs and metricsquery-logs (needs Read logs), get-metrics, get-system-metrics
Replicaslist-replicas, get-replica-health, restart-replicas
Docker Hubsearch-docker-images, list-docker-tags
Serverslist-servers, get-server
Staged changesapply-staged-changes, with a dry run that shows what would be affected
Webhookslist-webhooks, create-webhook, update-webhook
Youwhoami

What is redacted, and why

Two tools answer with a blank where a secret would be, unless the connection has the matching privilege:

  • Read variable values: without it, list-variables returns names and references, with values_redacted true.
  • Read webhook URLs: without it, the webhook tools return url_redacted true.

query-logs is not offered at all without Read logs, because a log line has no harmless part.

What is left out, and why

  • S3 buckets: creating or editing one means sending credentials, and those should not pass through a model conversation. Agents can list buckets and pick one for backups.
  • Team settings: managed in the UI.
  • Live log streaming: query-logs returns the same data.
  • Anything that needs a browser session: API keys, connected apps, connecting, sharing and removing GitHub apps, system settings, users and the terminal.

How an agent finds its way

The server gives every client a short set of instructions. They are worth knowing, because they describe how Unbind behaves through the API in general:

  • Resources nest as team > project > environment > service, and most tools need the IDs of every level above. Agents find them with list-teams, list-projects, list-environments and list-service.
  • Names are unique among siblings and case sensitive. A taken name answers "conflict", except for create-service, create-service-group, create-volume and deploy-template, which add a short suffix and keep going.
  • Agents call whoami first to learn their role, limits and privileges, and not to retry for values that come back redacted.
  • A service built from GitHub needs an installation, an owner and a repository. list-github-repositories lists the repositories the agent can build in a team, each with its installation. A repository that is not listed has to be added to the installation on GitHub, or its connection shared with the team, by a person first.
  • Creating a service does not deploy it. The agent calls trigger-deployment, polls get-deployment until it finishes, and reads query-logs when a build or a replica fails.
  • Once a service is running, changes to its config or variables roll out on their own, and so do the services that reference a changed variable.
  • A service's variables can reference other values instead of copying them, like API_URL=${{service:<service_id>.UNBIND_URL_PRIVATE}}, so they stay correct when the source changes. list-available-references lists what a service can use.
  • A service holds one volume at most. A service with a volume runs a single replica, and its rollouts stop the running replica before the new one starts. The new image is pulled first, so an image that can't be pulled leaves the running replica in place.

Hints for the client

Each tool tells the client whether it only reads, whether it destroys something, and whether calling it twice is safe. Good clients use these hints to ask you before a destructive call. Every delete is marked destructive.

On this page