Skip to main content

​
Overview

Connect Netlify to Continue Mission Control to give your agents access to Netlify’s API and CLI. Create projects, deploy applications, configure domains, and manage infrastructure with natural language. When Netlify is enabled, Continue can analyze bundle sizes, audit performance, and prevent performance regressions.

What You Can Do with Netlify Integration

  • Run Lighthouse audits on PR previews and production
  • Compare bundle sizes and analyze performance regressions
  • Automatically detect configuration issues (minification, caching, tree-shaking)
  • Block PRs that introduce critical performance problems
  • Generate detailed performance reports with actionable fixes
  • Create projects and manage domains with natural language
  • Configure build settings and environment variables

​
Setup

1

Navigate to Integrations

Go to your Integrations Settings.
2

Connect Netlify

Click “Connect” next to Netlify. You’ll need:
  • Personal Access Token: Generate from Netlify account settings
3

Generate Netlify Access Token

To create a personal access token:
  1. Log into your Netlify account
  2. Go to User Settings → Applications → Personal access tokens
  3. Click “New access token”
  4. Give it a descriptive name (e.g., “Continue Mission Control”)
  5. Copy the token immediately
4

Add Token to Mission Control

Paste your access token into the integration form and click “Create Connection”
Token Scope: Personal access tokens have full access to your Netlify account. Create a token specifically for Continue to maintain security and easy revocation if needed.

​
Workflows

​
Optimize Website Performance

Trigger: On PR merge
Description: Run Lighthouse audits on PR preview and production to compare performance When a pull request is merged, this performance-focused workflow automatically:
  1. Retrieves Deployment Information - Uses Netlify MCP to get:
    • Production deploy URL and metadata
    • Deploy preview URL for the PR branch
    • Build artifacts and configuration
  2. Analyzes Bundle Sizes - Compares JavaScript and CSS bundles:
    • Downloads and measures all asset files
    • Calculates total bundle size for both deploys
    • Identifies largest individual files
    • Detects unminified or bloated assets
  3. Reviews Build Configuration - Examines:
    • vite.config.ts or webpack.config.js for minification settings
    • netlify.toml for cache headers and build commands
    • package.json for redundant or oversized dependencies
  4. Identifies Performance Issues - Classifies problems by severity:
    • 🔴 Critical: Minification disabled, bundle size >50% increase, no caching
    • ⚠️ Warning: No code splitting, large chunks >500KB, 20-50% bundle increase
    • ℹ️ Info: Suboptimal configurations, bundle size less than 20% increase
  5. Generates Actionable Report - Posts to PR with:
    • Bundle size comparison table
    • Root cause analysis with file references and line numbers
    • Code fixes that can be copy-pasted
    • Merge recommendation (Approved/Review Needed/Blocked)
    • Expected improvements from each fix

Why This Matters

Performance regressions often slip through code review because:
  • Bundle size increases aren’t visible in diffs
  • Configuration errors (disabled minification) go unnoticed
  • Redundant dependencies accumulate over time
This workflow catches these issues automatically before they reach production.
Smart Analysis: The agent doesn’t just report bundle sizes—it analyzes build configurations, identifies root causes, and provides specific code fixes with line numbers.

​
Performance Issue Classification

The agent categorizes issues by severity:
Issues that must be fixed before merging:
  • Minification disabled (minify: false)
  • Tree-shaking disabled (treeshake: false)
  • No caching headers (Cache-Control: no-cache)
  • Production source maps enabled
  • Bundle size increase >50%
  • Redundant dependencies (lodash + underscore, moment + date-fns + dayjs)
Action: Agent recommends blocking the merge
Issues that need attention:
  • No code splitting (single large bundle)
  • Suboptimal cache headers (max-age too low)
  • Large individual chunks (>500KB)
  • Unoptimized images
  • Bundle size increase 20-50%
Action: Agent recommends careful review before merging
Non-blocking improvements:
  • Could use better code splitting
  • Modern browser features could replace polyfills
  • CSS not extracted/split
  • Bundle size increase less than 20%
Action: Agent approves merge but suggests optimizations

​
Use Cases

​
Infrastructure as Code

Manage Netlify infrastructure with natural language:

Infrastructure Manager

Task Example: “Create a new Netlify site for the marketing-site repo with custom domain marketing.company.com”What the Agent Does:
  • Creates new Netlify project via API
  • Connects to specified Git repository
  • Configures build settings and commands
  • Sets up custom domain and SSL
  • Configures environment variables
Run in Mission Control: Run manually when creating new projects

​
Build Configuration Optimization

Automatically optimize build settings:

Build Optimizer

Task Example: “Audit all Netlify sites for missing cache headers and suboptimal build configs”What the Agent Does:
  • Reviews netlify.toml and build settings
  • Checks cache header configurations
  • Identifies missing optimizations
  • Generates recommended configuration changes
  • Can apply fixes automatically
Run in Mission Control: Run monthly or after adding new sites

​
Performance Auditing

Prevent performance regressions before deployment:

Performance Auditor

Task Example: “Analyze bundle sizes and configurations, block PRs with critical performance issues”What the Agent Does:
  • Compares preview and production bundle sizes
  • Detects disabled minification or tree-shaking
  • Identifies redundant dependencies (lodash + underscore, multiple date libraries)
  • Checks cache configuration
  • Posts detailed report with fixes to PR
  • Recommends approval, review, or blocking merge
Run in Mission Control: Triggered automatically on PR merge

​
Dependency Analysis

Identify and fix problematic dependencies:

Dependency Auditor

Task Example: “Find redundant or oversized dependencies across all projects”What the Agent Does:
  • Scans package.json files in all Netlify sites
  • Identifies duplicate functionality (multiple date/utility libraries)
  • Finds oversized packages (>100KB)
  • Suggests lightweight alternatives
  • Calculates potential bundle size savings
Run in Mission Control: Run quarterly for dependency cleanup

​
Continuous Performance Monitoring

Track performance trends over time:

Performance Tracker

Task Example: “Generate a performance trend report for the last 30 deploys”What the Agent Does:
  • Queries deploy history via Netlify MCP
  • Tracks bundle size over time
  • Identifies gradual performance degradation
  • Highlights deploysthat introduced regressions
  • Generates visualization of trends
Run in Mission Control: Schedule weekly for ongoing monitoring

​
Domain and SSL Management

Manage domains using natural language:

Domain Manager

Task Example: “Add www.example.com to my site and configure SSL”What the Agent Does:
  • Configures custom domains via Netlify API
  • Sets up SSL certificates automatically
  • Configures DNS records and redirects
  • Verifies domain setup and SSL status
Run in Mission Control: Run manually when adding domains

​
Running Netlify Agents in Mission Control

You can run Netlify-connected agents in two ways as one-off tasks or automated workflows:
Start with manual tasks to refine your content queries, then automate repetitive content management and validation tasks.

​
2. Automated Workflows

Set up agents to run automatically:
  • PR-triggered: Audit performance when pull requests are merged
  • Scheduled: Run weekly bundle size audits across all sites
  • Manual: Analyze specific deploys or troubleshoot performance issues
Start with manual performance audits on specific PRs to refine your thresholds, then enable automated workflows to catch all performance regressions.

​
Troubleshooting

Problem: Agent can’t connect to Netlify APISolutions:
  • Verify personal access token is correct
  • Check that token hasn’t been revoked
  • Ensure token has necessary permissions
  • Try regenerating the token
Problem: Deploy preview is still building when agent tries to analyzeSolutions:
  • Verify you have deploy permissions for the site
  • Check that the site exists and is accessible
  • Ensure build hooks are configured if using webhooks
  • Review Netlify API rate limits
Problem: Agent can’t find deploy preview for the branchSolutions:
  • Verify branch name is correct
  • Check that PR has triggered a Netlify build
  • Ensure deploy previews are enabled in Netlify settings
  • Confirm the repository is connected to Netlify
Problem: Agent can’t download or analyze bundlesSolutions:
  • Verify deploy URLs are accessible
  • Check for authentication requirements on preview
  • Ensure assets are being generated correctly
  • Review build logs for errors
Problem: Agent can’t locate deploy previewsSolutions:
  • Verify branch name is correct
  • Check that deploy previews are enabled for the site
  • Ensure the commit has triggered a build
  • Wait for build to complete before querying
Problem: Can’t retrieve site performance metricsSolutions:
  • Verify Netlify Analytics is enabled for the site
  • Check that your plan includes analytics access
  • Ensure time range for queries is valid
  • Review API documentation for metrics endpoints

​
Support & Resources

Netlify MCP Cookbook

Complete guide to continuous deployment automation with Netlify and Continue

GitHub Integration

Combine Netlify with GitHub for end-to-end CI/CD automation