Netlify MCP Server: Streamline DevOps & Centralized Site Control

What is Netlify MCP Server: Streamline DevOps & Centralized Site Control?

This server acts as a middleware bridge between your development environment and Netlify’s API, enabling programmatic control over site lifecycle management. By leveraging the Model Context Protocol (MCP), it abstracts complex API interactions into actionable commands, allowing developers to automate deployments, manage configurations, and track site status without leaving their workflow.

How to use Netlify MCP Server: Streamline DevOps & Centralized Site Control?

1. Clone the repository and install dependencies via npm.
2. Generate a Netlify access token from your account settings.
3. Configure the server by setting environment variables and integrating it with your MCP setup.
4. Execute predefined commands like createSiteFromGitHub to deploy repositories directly from your IDE.

Personal preference tip: I recommend setting up a dedicated VM for testing configurations before deploying to production environments.

Key Features of Netlify MCP Server: Streamline DevOps & Centralized Site Control?

• GitHub Integration: Instantly spin up sites from repositories using specified branches and build commands.
• Granular Visibility: Filter sites by access levels (owner/guest) and retrieve detailed build logs.
• Atomic Operations: Delete sites with confirmation safeguards while maintaining audit trails.
• Environment Isolation: Manage staging/production environments through distinct configuration profiles.

Use cases of Netlify MCP Server: Streamline DevOps & Centralized Site Control?

Optimal scenarios include:

• CI/CD pipelines requiring automated site creation for pull request previews
• Enterprise teams managing hundreds of microsites with centralized policy enforcement
• Infrastructure as Code workflows where site configurations are version-controlled
• Debugging environments that need rapid site deletion/recreation cycles

FAQ from Netlify MCP Server: Streamline DevOps & Centralized Site Control?

Q: How do I troubleshoot authentication errors?
A: Verify the access token has proper scopes and check environment variable escaping in your MCP config. Tokens older than 30 days may need regeneration.

Q: Can I customize build commands dynamically?
A: Yes, the buildCommand parameter supports template variables referencing repository metadata (e.g., {{repo_branch}}).

Q: What happens if I delete a site with active traffic?
A: The site is immediately taken offline and removed from load balancers. Use the filter:owner list option to audit before deletion.

Netlify MCP Server

A Model Context Protocol (MCP) server for managing Netlify sites. This server enables seamless integration with Netlify's API through MCP, allowing you to create, manage, and deploy sites directly from your MCP-enabled environment.

Features

• Create new sites from GitHub repositories
• List existing Netlify sites
• Get detailed site information
• Delete sites

Installation

1. Clone this repository:

git clone https://github.com/MCERQUA/netlify-mcp.git
cd netlify-mcp

2. Install dependencies:

npm install

3. Build the project:

npm run build

Configuration

Getting Your Netlify Access Token

1. Create a Netlify account at https://app.netlify.com/signup
2. Go to User Settings > Applications > Personal access tokens
3. Click "New access token"
4. Give it a name (e.g., "MCP Integration")
5. Copy the generated token

Setting Up MCP

1. Create a .env file in the project root:

NETLIFY_ACCESS_TOKEN=your_token_here

2. Add the server to your MCP settings configuration:

{
  "mcpServers": {
    "netlify": {
      "command": "node",
      "args": ["path/to/netlify-mcp/build/index.js"],
      "env": {
        "NETLIFY_ACCESS_TOKEN": "your_token_here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Available Tools

createSiteFromGitHub

Create a new Netlify site from a GitHub repository.

interface CreateSiteFromGitHubArgs {
  name: string;          // Name for the new site
  repo: string;          // GitHub repository (format: owner/repo)
  branch: string;        // Branch to deploy from
  buildCommand: string;  // Build command to run
  publishDir: string;    // Directory containing the built files
}

listSites

List all Netlify sites you have access to.

interface ListSitesArgs {
  filter?: 'all' | 'owner' | 'guest';  // Optional filter for sites
}

getSite

Get detailed information about a specific site.

interface GetSiteArgs {
  siteId: string;  // ID of the site to retrieve
}

deleteSite

Delete a Netlify site.

interface DeleteSiteArgs {
  siteId: string;  // ID of the site to delete
}

Documentation

For more detailed information, see:

• Setup Guide
• API Documentation
• Usage Examples

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.