Netlify MCP
for LuumenAI

Inspect Netlify projects and deploys, then ship changes as approved steps

Connect Netlify and Luumen can read your projects, deploy history, team environment variables, and installed extensions on request. Ask why the last build failed, which sites a variable is set on, or what changed between deploys. When a fix means deploying a site or editing project settings, Luumen shows the plan first and waits for your approval by default. Access is set up through OAuth with dynamic client registration.

Book a DemoDownload Luumen

The Netlify MCP toolbox

9 tools: 6 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet-netlify-coding-contextALWAYS call when writing code.
  • ReadNetlify-deploy-services-readerSelect and run one of the following Netlify read operations (read-only) get-deploy, get-deploy-for-site
  • ReadNetlify-extension-services-readerSelect and run one of the following Netlify read operations (read-only) get-extensions, get-full-extension-details
  • ReadNetlify-project-services-readerSelect and run one of the following Netlify read operations (read-only) get-project, get-projects, get-forms-for-project
  • ReadNetlify-team-services-readerSelect and run one of the following Netlify read operations (read-only) get-teams, get-team, get-team-env-vars
  • ReadNetlify-user-services-readerSelect and run one of the following Netlify read operations (read-only) get-user
  • WriteNetlify-deploy-services-updaterSelect and run one of the following Netlify write operations deploy-site Approval by default
  • WriteNetlify-extension-services-updaterSelect and run one of the following Netlify write operations change-extension-installation, initialize-database Approval by default
  • WriteNetlify-project-services-updaterSelect and run one of the following Netlify write operations update-visitor-access-controls, update-forms, manage-form-submissions, update-project-name, manage-env-vars, create-new-project Approval by default

One prompt, start to finish

What a governed Netlify MCP run looks like inside Luumen.

Questions

How does LuumenAI connect to Netlify MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Netlify MCP on its own?

Read actions answer immediately. Anything that writes — netlify-deploy-services-updater, netlify-extension-services-updater, netlify-project-services-updater — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Netlify MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
GitHubRepos, actions, and runbook code as context and as actions.GitLabMerge requests and pipelines proposed, triggered, and rolled back.BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.

Put Netlify MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen