Kiwi for Netlify
Have the agent on a Kiwi step deploy a site to Netlify and set its environment variables, through Netlify's MCP server.
- Your agent works in Netlify through its own connection. Kiwi does not call Netlify and never holds its credentials.
- A workflow skill can list Netlify among the tools it requires. When you supply your agent's available tools to a skill check and Netlify is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Netlify, 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 Netlify connection, with
report_configuration. - The agent submits links to its work in Netlify as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Netlify
- Create a Netlify project and deploy it.
- Manage a project's environment variables and secrets.
- Change the access controls of a project.
- Manage the extensions and forms of a project.
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 Netlify
Add the Netlify MCP server to your agent with this URL. The credentials stay with your agent.
https://netlify-mcp.netlify.app/mcpExample skill
Publish instructions like these as a workflow skill that lists Netlify among its required tools.
Read the Netlify site name and the branch from the step's inputs. Create a deploy of that branch and leave the production deploy unchanged. Set the environment variables the assignment names; never put their values in outputs. Submit the deploy URL and the deploy ID as the step's outputs. Publishing to production is the run's Owner's decision. If the build fails, report a blocker with the build log link.