Netlify MCP Server for Claude

Content

Streamline your web deployment and site management by connecting Claude to Netlify. Deploy sites automatically, manage environment variables, configure domains and SSL, handle form submissions, deploy serverless and edge functions, monitor builds, and automate workflows—all through natural language commands. Leverage Netlify's powerful platform with rate limit monitoring and comprehensive deployment controls.

Features

• Create and deploy sites automatically (Git-based or manual deployments)
• Manage environment secrets and variables (site, branch, and deploy context scoping)
• Configure access controls and permissions (team and site-level settings)
• Handle form submissions and data (form processing and storage)
• Control site settings and domains (custom domains, SSL certificates, redirects)
• Manage serverless and edge functions (deploy and configure functions)
• Monitor deployments and build status (real-time build logs and deployment history)
• Configure build settings and frameworks (build commands, environment, plugins)
• Advanced Netlify site and deployment management with build automation, edge functions configuration, and analytics integration
• Batch operations support for efficient bulk site operations, deployment management, and build automation with automatic rate limit handling and retry logic
• Real-time deployment synchronization capabilities with webhook integration support for monitoring Netlify events and triggering automated workflows

Use Cases

• Deploy static sites with zero configuration (automatic builds from Git)
• Manage environment variables securely across different deployment contexts
• Configure custom domains and SSL certificates automatically
• Process form submissions automatically with serverless functions
• Set up redirects and rewrites for SEO and routing
• Deploy serverless and edge functions for dynamic functionality
• Monitor and manage build performance and deployment status
• Automate deployment workflows with build hooks and API integration
• Build automated deployment workflows that sync external systems with Netlify for real-time site management and build automation

Deployment-platform MCP servers compared

Several hosting platforms ship MCP servers that let Claude manage deployments. They differ by platform and primitives:

Use the Netlify MCP server when your sites and functions run on Netlify; the equivalent Vercel or Cloudflare servers cover those platforms' own primitives.

Installation

Claude Code

1. Get your Personal Access Token from Netlify (Applications > Personal access tokens)
2. claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp
3. Authenticate with your PAT when prompted (or configure in environment)
4. Verify installation: claude mcp list
5. Test connection: claude mcp status netlify
6. Verify access: Ask Claude to list your sites

Claude Desktop

1. Get your Personal Access Token from Netlify (Applications > Personal access tokens)
2. Open Claude Desktop configuration file (see configPath below)
3. Add the Netlify server configuration with HTTP transport pointing to https://netlify-mcp.netlify.app/mcp
4. Add PAT to environment variables or configuration
5. Restart Claude Desktop
6. Authenticate with your Netlify account when prompted
7. Verify access: Ask Claude to list your sites

Requirements

• Netlify account (free, Personal, or Pro plan)
• Personal Access Token (PAT) or OAuth2 credentials (generate from Applications > Personal access tokens)
• HTTP transport support (remote MCP server at https://netlify-mcp.netlify.app/mcp)
• Internet connection (remote Netlify API access required)
• Understanding of Netlify API rate limits (500 requests/minute general, 3 deployments/minute, 100 deployments/day)
• Understanding of build capacity limits (concurrent builds: Free=1, Personal=1+, Pro=3+)
• Understanding of Netlify workspace permissions and site access settings
• Claude Desktop 0.7.0+ or Claude Code with MCP support
• Understanding of web deployment concepts (static sites, serverless functions, edge functions, build processes)
• Optional: Git repository connected for continuous deployment (manual deploys also supported)

Configuration

{
  "netlify": {
    "url": "https://netlify-mcp.netlify.app/mcp",
    "transport": "http"
  }
}

Examples

Deploy my site to production

Common usage pattern for this MCP server

Ask Claude: "Deploy my site to production"

Update the API_KEY environment variable

Common usage pattern for this MCP server

Ask Claude: "Update the API_KEY environment variable"

Show recent form submissions

Common usage pattern for this MCP server

Ask Claude: "Show recent form submissions"

Configure domain redirect

Common usage pattern for this MCP server

Ask Claude: "Configure domain redirect"

Deploy Site

Deploy a site to Netlify with files and configuration

// Deploy site to Netlify
const deployment = await netlify.deploys.create({
  site_id: "site-id",
  files: {
    "index.html": "<html>...</html>",
    "style.css": "body { ... }",
  },
  draft: false,
});

Security

• Personal Access Token (PAT) or OAuth2 authentication for secure access
• Secure secret management system (environment variables encrypted at rest)
• Access control configuration options (site-level and team-level permissions)
• Build hook security measures (unique URLs for triggering builds)
• Monitor rate limit headers (X-RateLimit-*) to avoid service disruption
• Netlify API tokens and access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
• Netlify OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
• Netlify site IDs and deployment identifiers may expose infrastructure architecture and deployment patterns - ensure Netlify resource identifiers are kept private and not shared in public configurations
• Rate limiting and API quota management are critical for Netlify MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
• Netlify webhook configurations and payloads may contain sensitive deployment data and site information - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

Build minutes quota exceeded - site paused

Legacy plans: Check build minutes usage at app.netlify.com under team settings. Free plan: 300 build minutes/month. Upgrade plan for more minutes or switch to Credit-based pricing. Site auto-resumes next billing cycle or upgrade immediately. Credit-based plans use credits instead of build minutes. Monitor usage in Usage & billing dashboard.

API rate limit exceeded - 429 error code returned

Netlify API limit: 500 requests/minute for general operations, 3 deployments/minute, 100 deployments/day. Check X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers in responses. Monitor rate limit headers to avoid exceeding limits. Implement exponential backoff. Contact Netlify support for higher limits if needed.

OAuth authentication fails or permissions denied

Re-authenticate at https://netlify-mcp.netlify.app/mcp. Verify Personal Access Token is correctly configured (Authorization: Bearer ). Generate new PAT from Applications > Personal access tokens if expired. Verify account has team member role with deploy permissions. Check site access settings allow API operations. For OAuth2, ensure client key and secret are valid.

Environment variable not available during build

Add variables in site settings under Build & deploy > Environment. Use exact key names (case-sensitive). Redeploy site after adding variables. Check build logs for variable loading confirmation. Variables are scoped to site, branch, or deploy context. Verify variable is set for correct context (production, deploy-preview, branch-deploy).

Netlify MCP server authentication errors with API tokens

Verify API token is valid and not expired. Check token permissions match required operations. Ensure token format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

Netlify rate limit errors when processing multiple deployment requests

Implement exponential backoff retry logic with jitter. Use Netlify API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed site data. Netlify allows 1,000 requests per hour per API token.

Netlify site or deployment access denied errors

Verify API token has access to the site. Check site permissions and account membership. Ensure API token has required permissions for target operations.

Netlify MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Netlify API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

• Source repositorygithub.com 2026-07-13T15:19:32-07:00
• Documentationdocs.netlify.com
• Package (SHA-256 pinned)/downloads/mcp/netlify-mcp-server.mcpb