Kiwi for DigitalOcean
Have the agent on a Kiwi step update a DigitalOcean App Platform app and follow its deployment, through DigitalOcean's MCP server.
- Your agent works in DigitalOcean through its own connection. Kiwi does not call DigitalOcean and never holds its credentials.
- A workflow skill can list DigitalOcean among the tools it requires. When you supply your agent's available tools to a skill check and DigitalOcean is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to DigitalOcean, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its DigitalOcean connection, with
report_configuration. - The agent submits links to its work in DigitalOcean as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in DigitalOcean
- Create an App Platform app from an app spec, or update the spec of an existing app.
- Check the status of an app's deployment.
- List apps and read an app's details and usage.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to DigitalOcean
Add the DigitalOcean MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.digitalocean.com/mcpExample skill
Publish instructions like these as a workflow skill that lists DigitalOcean among its required tools.
Read the App Platform app name and the new image tag from the inputs. In DigitalOcean, set that tag in the staging app's spec. Check the deployment status at most 10 times, then stop and report a blocker. Submit the deployment ID and the app's live URL as the step's outputs. Changes to the production app wait for the run's Owner.