4,500+ servers built on MCP Fusion
Vinkius

Netlify MCP. Manage builds and deploys via chat commands.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Netlify MCP on Cursor AI Code Editor MCP Client Netlify MCP on Claude Desktop App MCP Integration Netlify MCP on OpenAI Agents SDK MCP Compatible Netlify MCP on Visual Studio Code MCP Extension Client Netlify MCP on GitHub Copilot AI Agent MCP Integration Netlify MCP on Google Gemini AI MCP Integration Netlify MCP on Lovable AI Development MCP Client Netlify MCP on Mistral AI Agents MCP Compatible Netlify MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Netlify MCP Server manages your entire Netlify deployment lifecycle directly from any AI agent. Use this to list all active sites, trigger new builds instantly, track historical deployments, and monitor form submissions without touching the dashboard.

You can query site metadata, check user profiles, and manage DNS zones—all via conversation.

What your AI agents can do

Get deploy

Retrieves detailed information about one specific deployment version on Netlify.

Get site

Gets core metadata and details for a single Netlify site project.

Get user

Pulls the profile data for an authenticated user account connected to Netlify.

+ 7 more capabilities included
Check Site Status

Get metadata for any Netlify project, including its unique ID and current configuration.

Monitor Deployments

List all historical site deployments or get the full details of a single deploy version.

Start Builds

Trigger a new build process for a specific Netlify site immediately.

Review Form Submissions

List recent submissions from a designated form on a specific site to check user feedback.

Manage Domains

List all custom DNS zones and domains attached to your account.

Verify User Identity

Retrieve the profile information for an authenticated user based on their credentials.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Netlify MCP Server: 10 Tools for Site Management

Use these ten tools to manage every aspect of your Netlify hosting environment, from listing sites to triggering production builds.

get019d75dc

get deploy

Retrieves detailed information about one specific deployment version on Netlify.

get019d75dc

get site

Gets core metadata and details for a single Netlify site project.

get019d75dc

get user

Pulls the profile data for an authenticated user account connected to Netlify.

list019d75dc

list builds

Lists all build records associated with a given netlify site ID.

list019d75dc

list deploys

Retrieves a list of all historical deployment versions for a specific site.

list019d75dc

list domains

Shows every DNS zone and custom domain currently configured on the account.

list019d75dc

list form submissions

Fetches recent messages submitted through a named form on your website.

list019d75dc

list forms

Lists all active contact or data collection forms attached to a site.

list019d75dc

list sites

Returns the names and IDs of every web project hosted on Netlify.

trigger019d75dc

trigger build

Initiates an immediate, fresh build process for a specified Netlify site.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Netlify, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Netlify MCP Server gives you direct control over your Netlify deployments—no more jumping between tabs or running messy CLI commands just to check a status. Your AI agent handles the whole lifecycle; it's like having a dedicated DevOps intern that never sleeps. You'll manage everything right from conversation, giving you full visibility into what’s going on with your sites and builds.

Checking Site Status & Metadata

When you need to know what projects you’re running, start simple. Use list_sites to get the names and unique IDs for every single web project hosted under your account. If you need deep details on one specific site—say, checking its current configuration or metadata—you call get_site. This pulls all the core info you need about that particular Netlify project.

Managing Builds and Deployments

The deployment pipeline is where this thing shines. You can monitor every stage of your app's life cycle without logging into the dashboard. If you want to see a history, list_deploys retrieves a full list of all past site deployments for a specific project. Want to dig into one specific version? Use get_deploy; it hands you all the detailed information about that single deployment instance.

If code changes and you need fresh assets, don't mess with the UI—just use trigger_build. It immediately starts an entire new build process for a designated site. To check the status of those builds or see records of previous attempts, run list_builds against your netlify site ID.

Reviewing Forms and User Feedback

Need to know what people are saying? You don't gotta dig through emails. First, you can use list_forms to get a list of every contact or data collection form attached to a specific site. Once you know which form it is, calling list_form_submissions fetches the most recent messages submitted through that named form on your website.

Handling Domains and Users

Managing domains and user accounts gets straightforward too. To see all the custom DNS zones and external domains attached to your account, use list_domains. If you need to verify who's talking to you or pull profile data for an authenticated person connected to Netlify, get_user pulls that specific profile information.

This server lets you treat deployment management like sending a chat command. You list all active sites via list_sites, check the metadata on any project using get_site, and then monitor deployments by calling list_deploys or getting granular info with get_deploy. If you need to start over, just trigger it with trigger_build.

For user data checks, get_user pulls their profile. You can also review site activity: use list_builds for build records, check submissions using list_form_submissions, and manage your web presence by listing all domains with list_domains.

How Netlify MCP Works

  1. 1 First, subscribe to this server and provide your Netlify Personal Access Token. This gives the agent API access.
  2. 2 Next, you prompt your AI client with a command—like 'List all my sites' or 'Trigger build for site X'.
  3. 3 The agent calls the appropriate tool (e.g., list_sites), gets the raw data, and presents it to you in plain text.

The bottom line is: your AI client handles authentication and API calling so you can manage complex deployments using simple chat prompts.

Who Is Netlify MCP For?

Frontend Developers, DevOps Engineers, and Content Managers. If you spend time switching between the Netlify dashboard, your terminal, and a ticketing system to check site health or deploy changes, this is for you. You're tired of context switching—you want results right where you write code.

Frontend Developer

Uses list_builds and trigger_build to quickly verify if a local change successfully compiled without leaving their IDE.

DevOps Engineer

Manages site health by calling get_deploy or checking list_domains status, ensuring the entire stack is correctly pointing to production endpoints.

Content Manager

Uses list_form_submissions to grab recent user feedback and inquiries directly into a document for review.

What Changes When You Connect

  • Immediate Build Control: Instead of navigating to the build section, you simply prompt for a new deployment. Use trigger_build and get confirmation instantly. This cuts out several clicks and context switches.
  • Full Deployment History: Don't manually check every dashboard tab. Call list_deploys or get_deploy to see the exact status, commit hash, and time of any site version you need to audit.
  • User Feedback Loop: Stop relying on email attachments for feedback. Use list_form_submissions to query recent user comments directly from your agent's chat output.
  • Site Discovery: When you forget which project ID belongs to 'the blog,' just run list_sites. You get a clean, actionable list of all available projects and their IDs.
  • Domain Oversight: Keep track of where your site points. Call list_domains to see every registered zone, ensuring no traffic is lost due to misconfiguration.

Real-World Use Cases

01

Hotfix deployment needed right now.

The production site breaks after a small update. Instead of logging into the Netlify UI and manually triggering a build, you tell your agent: 'Trigger build for site X.' The agent runs trigger_build instantly, giving you confirmation while you wait for the status to populate.

02

Auditing user data before launch.

Before launching a new feature, you need to know what users have submitted. You ask your agent to 'Show me recent form submissions.' The agent executes list_form_submissions, pulling the last 10 messages right into your chat window for quick review.

03

Checking site configuration across multiple projects.

You have ten client sites and need to know if they all point to correct domains. You run list_sites first, then loop through the IDs calling list_domains for each one, getting a consolidated view of your entire infrastructure.

04

Verifying who signed up last week.

You need to confirm if a specific user account (like an admin) is linked to Netlify. You use the get_user tool, providing their ID, and the agent returns their profile details immediately for verification.

The Tradeoffs

Checking status via multiple dashboards

Opening the Netlify dashboard, then opening your terminal CLI, then checking a separate domain registrar's web UI. You lose track of which tool was last updated.

Keep it in one place. Use your agent to run list_sites for an overview, followed by get_deploy on the specific site ID for the single piece of data you need.

Guessing which build is live

Running a deploy and then waiting 20 minutes to check if it actually went through. You're wasting time refreshing pages.

Use list_deploys immediately after the trigger. This gives you the list of all versions and their current status, telling you exactly when (and if) the build finished.

Copy-pasting IDs manually

You have to go into one tab to find a site ID and then copy it into another command line or tool. This is slow and error-prone.

Use list_sites first. The agent provides the clean list of sites, making sure you use the correct site ID when calling other tools like trigger_build.

When It Fits, When It Doesn't

Use this server if your primary bottleneck is context switching between deployment views and command lines. You need to treat Netlify's API as a conversational endpoint.

Don't use this if you simply want to read documentation about the APIs; the tools only execute commands, they don't teach you them. Also, if all you need is basic site information (like just the name), checking the main dashboard might be faster than calling get_site. Only rely on these tools for action (triggering builds) or complex data retrieval (form submissions).

Always start by running list_sites to ensure your agent has the correct scope before attempting any other action like list_deploys or trigger_build.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Netlify. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_deploy get_site get_user list_builds list_deploys list_domains list_form_submissions list_forms list_sites trigger_build

Checking site status shouldn't require five tabs and three clicks.

Right now, figuring out if a deployment worked is a headache. You check the dashboard for build success. Then you open another tab to see the domain status. If you need form data, you jump into the analytics panel. It’s manual, it’s slow, and you're always guessing which piece of information belongs where.

With Netlify MCP Server, you talk to your agent. You ask about deployment history or recent user feedback. The agent runs `list_deploys` or `list_form_submissions` and gives you the answer in a single chat response. It's immediate status updates without leaving your workspace.

Netlify MCP Server: Get site data, build history, and user info.

The process of checking domain zones (`list_domains`), confirming a user's identity (`get_user`), and triggering a fix (`trigger_build`) used to require jumping between the Netlify UI, your terminal, and possibly another service. It was a multi-step manual workflow.

Now, you handle it all through natural language. You ask for the domain zones, and get them. You need a hotfix? Ask the agent to `trigger_build`. The single conversational interface manages complex API calls like these.

Common Questions About Netlify MCP

How do I list all my Netlify sites using the list_sites tool? +

Run list_sites and provide your site scope. It returns a clean list of every project ID, saving you from manually navigating to each one.

What is the difference between get_deploy and list_deploys? +

list_deploys gives you an index—a summary of all historical versions. get_deploy lets you drill down into one specific deployment to see its exact metadata.

Can I trigger a build for a site using the trigger_build tool? +

Yes, providing the correct Netlify Site ID, the trigger_build tool initiates an immediate new build process. You'll need to use list_builds afterward to track its progress.

Where do I find user submissions using list_form_submissions? +

You must know the Site ID and the Form Name. The agent uses both parameters in the list_form_submissions tool call to filter out noise and retrieve only relevant messages.

What credentials are required to use the `get_user` tool? +

You need a Netlify Personal Access Token for authentication. This token grants your agent read-only access to retrieve authenticated user profile data, confirming who owns the site.

Use the `get_site` tool to view core configuration metrics? +

The get_site tool pulls foundational details about a specific project. You can check metadata like the build settings, associated domains, and general health status for any site ID.

How do I track the full lifecycle of a site's deployments using `list_builds`? +

The list_builds tool shows you every compilation attempt. This lets you audit build failures or verify successful pre-deployment steps before checking the final deploy status.

How do I check which DNS zones are managed under my account using `list_domains`? +

The list_domains tool retrieves all managed DNS zones and associated domains. This is crucial for verifying domain ownership and checking active record configurations.

Can I check if my latest deploy was successful using the agent? +

Yes! Use the list_deploys tool with your Site ID. Your agent will fetch the latest deployments and their statuses, such as 'ready', 'error', or 'building'.

How do I trigger a new build for my site? +

Simply ask the agent to trigger_build and provide the Site ID. It will start a new build process in your Netlify account immediately.

Does the integration allow me to see contact form submissions? +

Yes. Use the list_forms tool to find your Form ID, and then use list_form_submissions to retrieve the latest messages from your users.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Netlify. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.