Build a site or landing page in Manus, and it deploys to your Netlify account and sends you the live URL. Use Manus as your Netlify AI agent to check deploys, sort form submissions and manage environment variables.
Make a site for our weekend pottery classes and put it on Netlify.
Describe the site, or point to code you already have. Manus builds it, creates a Netlify project, runs the deploy and sends you the link that visitors will see.
Ask for the change in plain words. Manus edits the site and deploys it to the same Netlify project. Ask it to name the project and wait for your OK before the update goes live.
Pick the repository. Manus reads the code through the GitHub connector, deploys it to the Netlify project you name and sends you the link.
Paste the deploy link. Manus reads the deploy status and the error Netlify reports, checks the code when needed, and tells you in plain words what went wrong and what to change.
Build script returned non-zero exit code: 2Turn on Netlify Forms for the contact or booking form on your site. Manus reads what people send, puts it in a table, groups it by topic and picks out the ones that need a reply.
Manus turns on form detection for the project, sets up the form on your page for Netlify and deploys again, so new submissions start to arrive.
Get every submission to a form as an Excel or CSV file, with the columns you pick and the newest first.
Deleted submissions can’t be restored, so ask Manus to list the ones it would remove and delete them only after you say OK.
Show a new version to a client or your team on its own link, behind a password. Your live site changes only when you ask Manus to publish. Password protection needs a Netlify Pro plan or above, and team sign-in needs Netlify Enterprise.
Manus puts the new version on a separate preview project, sets a password (on Netlify Pro and above) and sends you the link to share. Your live site stays as it is until you say OK.
Limit a project to people who sign in with your Netlify team, or protect only previews and branch deploys. Both options need a Netlify Enterprise plan.
List, add or change the variables a project uses. Mark API keys as secret, and Netlify keeps their values masked. Changes apply from the next deploy.
Add our email API key and the new booking link. List the changes first.
Manus lists the Netlify extensions your team can install and installs or removes them. After the Supabase extension is installed, you connect your Supabase account in Netlify, and the database keys are added to the project.
Netlify is already in Manus Connectors. Sign in with your Netlify account once, and any task can use the Netlify MCP tools to deploy sites and manage the projects your account can open.
In Manus, open Connectors, choose Netlify and select Connect.
Sign in with your Netlify account and allow access. Manus works with the teams and projects your account already has.
Mention Netlify and the project name. Before a deploy to your live site, a change to environment variables or who can visit, or a deletion, ask Manus to wait for your OK.
Open Connectors in Manus, choose Netlify and select Connect. Sign in with your Netlify account and allow access. Then mention Netlify in any task, for example “Deploy this site to a new Netlify project.”
Yes. The Netlify connector in Manus works through the MCP server that Netlify provides, the same one behind the Netlify Claude connector and the ChatGPT Netlify app. In Manus it’s already in Connectors, so there’s nothing to install or configure.
A deploy to an existing Netlify project goes live on its URL right away, so name the project you want. To check first, ask Manus to tell you the project and wait for your OK, or to use a separate preview project. Netlify keeps earlier deploys, and you can publish an older one again from the project’s Deploys page.
Yes. If your project uses the Netlify GitHub integration, Netlify builds a Deploy Preview for every pull request, and Manus can open that pull request through the GitHub connector. For a site without a repository, ask Manus to deploy the new version to a separate preview project and send you the link.
Paste the deploy link from Netlify. Manus reads the deploy status and the error Netlify reports, checks the code when needed, tells you in plain words what went wrong and what to change, and can fix the code and deploy again after you say OK.
Yes. Ask Manus for a spreadsheet of a form’s submissions, as an Excel or CSV file with the columns you choose. On Netlify, each form also has Download as CSV. Deleted submissions can’t be restored, so ask Manus to list them before it deletes anything.
No, not after they’re saved. Netlify keeps variables marked as secret write-only and returns masked values, except values set for local development. Manus can still add or replace them. Values that aren’t marked secret can be read, so ask Manus to show names only.
Yes. Manus can install the Supabase extension for your Netlify team. You then connect your Supabase account and project in Netlify, and Netlify adds the database keys to the project as environment variables. An extension is installed for the whole team, so ask Manus to wait for your OK.
Netlify AI tools such as Agent Runners change and ship code from your Netlify dashboard. Manus can also host what it builds: publish a web app on Manus with your own domain. If your team already runs its sites on Netlify, connect it and Manus deploys to your own Netlify account.
It’s Netlify’s own feature that lets the code on your site call AI models without managing API keys. It’s separate from this connector. Manus builds your site, deploys it to Netlify and handles the work after launch, such as forms, environment variables and who can visit.
Only what your Netlify account can. Manus uses your own sign-in, so it sees the teams and projects you belong to. Password protection needs a Netlify Pro plan or above, team sign-in needs Netlify Enterprise, and usage counts toward your Netlify account.
Yes. Open Connectors in Manus and disconnect Netlify at any time. Tasks can’t use your Netlify account after that.