# Netlify

Skills for the Netlify platform: serverless and edge functions, Blobs storage, managed Postgres, Image CDN, forms, identity, caching, AI Gateway, framework adapters, and the Netlify CLI and deploys.

Netlify is a cloud hosting platform for web applications and static sites with continuous deployment, forms, and serverless functions.

- Category: Security & Ops
- Connection: Sign in. Sign in with your Netlify account, or paste an API key instead.
- Plans: Free: Not included; MCP only ($9/mo): 2,000 calls a month; Pro: 20,000 calls a month; Max: 20,000 calls a month
- Vendor site: https://netlify.com

## Tools

- Get account by id (`NETLIFY__GET_ACCOUNT_BY_ID`): Get information about a specific account/team by its ID or slug.
- Get accounts (`NETLIFY__GET_ACCOUNTS`): List all accounts/teams that the authenticated user has access to. In Netlify's API, accounts are equivalent to teams.
- Get deploy (`NETLIFY__GET_DEPLOY`): Get information about a specific deployment.
- Get deploy key (`NETLIFY__GET_DEPLOY_KEY`): Get information about a specific deploy key.
- Get env variables (`NETLIFY__GET_ENV_VARIABLES`): Get environment variables for an account/team.
- Get site (`NETLIFY__GET_SITE`): Get information about a specific site by its ID or domain.
- Get site deploy (`NETLIFY__GET_SITE_DEPLOY`): Get information about a specific deployment for a specific site.
- Get sites (`NETLIFY__GET_SITES`): Get all sites that the authenticated user has access to.
- Create build hook (`NETLIFY__CREATE_BUILD_HOOK`): Create a new build hook for a site. Build hooks provide unique URLs to trigger new builds and deploys from external services or scripts. Once created, use NETLIFY__TRIGGER_BUILD_HOOK to actually trigger builds.
- Create deploy key (`NETLIFY__CREATE_DEPLOY_KEY`): Step 1 of private repository deployment: Create a new deploy key pair. This generates SSH keys that allow Netlify to access private repositories. After creating this, use NETLIFY__GET_DEPLOY_KEY or NETLIFY__LIST_DEPLOY_KEYS to get the public key, then add it to your GitHub repository using GITHUB__CREATE_DEPLOY_KEY.
- Create site (`NETLIFY__CREATE_SITE`): Create a new site/project on Netlify with full support for both public and private repositories. For private repositories, use NETLIFY__CREATE_DEPLOY_KEY first to generate a deploy key, then GITHUB__CREATE_DEPLOY_KEY to add it to your repository, then use this function with the deploy_key_id parameter. IMPORTANT: Verify the correct branch name (main vs master) in your repository before deployment to avoid branch not found errors.
- Delete deploy key (`NETLIFY__DELETE_DEPLOY_KEY`): Delete a deploy key.
- Delete site (`NETLIFY__DELETE_SITE`): Permanently delete a site.
- List deploy keys (`NETLIFY__LIST_DEPLOY_KEYS`): List all deploy keys for the account.
- List deploys (`NETLIFY__LIST_DEPLOYS`): List all deployments for a specific site.
- Trigger build hook (`NETLIFY__TRIGGER_BUILD_HOOK`): Trigger a new build and deployment by calling a build hook URL. Build hooks pull the latest code from the connected Git repository and rebuild the site. This is the recommended method for triggering Git-based deployments.
- Update site (`NETLIFY__UPDATE_SITE`): Update an existing site's configuration.

## Skills included

- netlify-access-control: Picks the right Netlify site-protection layer and disambiguates the three unrelated "auth" concepts users conflate — app-user login (Netlify Identity), site-load gating (Password Protection / project visibility), and dashboard SAML SSO. Use it when asked to password-protect a site or Deploy Preview, make a project private/public, restrict a site to your team, require SSO to view a site, set up company-wide app SSO, or invite users to a private project. Also use it for SSO-session symptoms on protected sites: "logged out mid-session", 401s after about an hour, or token expiry/refresh questions. Not for wiring auth code — route app-login setup to netlify-identity.
- netlify-agent-runner: Run AI agent tasks remotely on Netlify using Claude, Codex, or Gemini. Use when the user wants to run an AI agent on their site, get a second opinion from another model, or delegate development tasks to run remotely against their repo.
- netlify-ai-gateway: Use Netlify AI Gateway to call OpenAI, Anthropic Claude, Google Gemini, or OpenRouter-hosted models (DeepSeek/Meta/Mistral/Qwen) from Netlify Functions or Edge Functions without managing provider accounts or API keys. Reach for this when adding an AI feature to a Netlify app — a chatbot, text summarizer, image generator, joke/content generator, form-submission routing or analysis, or any LLM call — or when wiring the OpenAI/Anthropic/Gemini/TypeSafe/OpenRouter SDK into a Netlify Function, choosing which env vars to use, streaming long generations, or debugging why gateway calls fail at build time or return 401.
- netlify-blobs: Store and retrieve unstructured objects, files, and cache-like state on Netlify with the @netlify/blobs module. Use when persisting user file uploads (images/documents), caching computed output from functions or Background Functions, serving downloadable assets, storing JSON blobs keyed by ID, or seeding deploy-specific data. Reach for this for key/value or object storage from Functions, Edge Functions, or Build Plugins — not for per-user, transactional, or relational data (use Netlify DB for that). Triggers include "save an uploaded file", "cache API results", "store generated site map", "key/value store for a function", or "file uploads without a database".
- netlify-caching: Cache dynamic and static responses on Netlify's CDN from Functions, Edge Functions, and proxies. Use when you add caching or cache-control headers to a function response, tune cache TTL or stale-while-revalidate, set up the durable cache, vary a cache key by query/header/cookie/country/language, purge or invalidate the cache by site or cache tag, use the programmatic Cache API (caches.open/match/put) or @netlify/cache helpers (fetchWithCache/cacheHeaders/getCacheStatus), speed up an expensive API call, add ISR or on-demand revalidation, or debug why a response is or isn't cached via the Cache-Status header.
- netlify-config: Configure Netlify builds and routing via netlify.toml, _redirects, and _headers. Use when setting a build command or publish directory, adding redirects or rewrites or proxies, adding an SPA fallback rewrite, setting custom response headers or basic auth, managing environment variables and secrets, scoping vars per deploy context, marking a var as secret, disabling secret scanning, configuring functions bundling, ignoring builds, or wiring up a monorepo or JavaScript SPA on Netlify.
- netlify-database: Zero-config Postgres for Netlify apps via @netlify/database — querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev with netlify dev, database branches for deploy previews, and migrating an existing Postgres project onto Netlify. Use when adding a database, building a contact form or CRUD API, writing SQL migrations, wiring up Drizzle, running netlify database commands, testing with a local Postgres, or switching from Neon/Supabase/RDS to Netlify Database.
- netlify-deploy: Create, configure, and manage Netlify deploys from code — reach for this when setting up Git continuous deployment, running netlify deploy or netlify deploy --prod from the CLI, writing netlify.toml deploy contexts, adding a Deploy to Netlify button, wiring build hooks, configuring Deploy Previews or branch deploys, locking or skipping deploys, fixing a failed or secrets-scanning deploy, or when someone asks to "deploy my site", "set up preview deploys", "add per-branch build config", or "add a deploy button to my README".
- netlify-edge-functions: Write and configure Netlify Edge Functions — TypeScript/JavaScript handlers running in a Deno runtime at the network edge. Use when adding auth middleware or auth redirects, geolocation or localization logic, A/B testing or personalization, request/response transforms (rewrites/redirects), or edge SSR to a Netlify site. Triggers on tasks like "add an edge function", "auth check at the edge", "redirect visitors by country", "A/B test with cookies", "rewrite requests", "personalize by geo", or "cache an edge response". Covers the config export, path routing, the Context object, response caching, environment variables, and edge-vs-serverless choices. Check the framework's adapter first — only hand-write an edge function when the framework doesn't already generate one.
- netlify-forms: Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; or debugging missing submissions and forms that silently fail to register.
- netlify-frameworks: Deploy and configure web frameworks on Netlify — build settings and SSR/edge adapters plus local platform emulation and env vars. Use when setting up or fixing a framework deploy (Next.js / Astro / Nuxt / SvelteKit / Remix / React Router / TanStack Start / SolidStart / Gatsby / Angular / Vite / Express / Hydrogen / Hugo / Eleventy / Vue / React), adding SSR or edge functions or middleware wired to Netlify context, fixing SPA redirect and catch-all rules, setting a build command or publish directory, or debugging "why isn't my env var updating" and framework build failures.
- netlify-functions: Write, configure, and deploy Netlify serverless functions in TypeScript, JavaScript, or Go. Use this when adding an API endpoint or backend route, adding a contact form handler, wiring auth or Identity signup/login hooks, building streaming or AI-proxy responses, scheduling cron jobs, running long background jobs (batch processing/scraping), reacting to deploy or form events, setting up rate limiting or region/memory config, or reading environment variables and secrets inside a function. Covers file locations, the Request/Context/Response handler shape, path routing, config options, and local testing with netlify dev.
- netlify-identity: Add user authentication to a Netlify site with @netlify/identity — signup/login/logout, Google/GitHub/GitLab/Bitbucket OAuth, server-side getUser() checks, role-based access control, and Identity event functions. Use it when a task involves adding a login or signup form, gating content to members or roles, "auth middleware" or verifying users in Netlify Functions or Edge Functions, handling OAuth or email-confirmation callbacks, assigning roles at signup, or customizing Identity emails. For locking a whole site to your company or employees-only access, use netlify-access-control instead.
- netlify-image-cdn: Transforms images on demand via Netlify Image CDN's /.netlify/images endpoint with query parameters for resizing/cropping/format/quality. Use when adding image optimization or responsive images, converting formats (WebP/AVIF/PNG), generating thumbnails or blur placeholders, serving remote/third-party images through the CDN, allowlisting remote domains in netlify.toml, setting up image redirects or cache headers, building user-uploaded image pipelines, or debugging a 404 on /.netlify/images. Also covers framework image handling for Angular/Astro/Gatsby/Next.js/Nuxt.
- netlify-mcp-servers: Build, deploy, and secure Model Context Protocol (MCP) servers on Netlify. Use whenever the task involves creating an MCP server, exposing an app or API to AI agents as MCP tools, letting Claude / Cursor / Claude Code call a custom remote server, or adding MCP tools to an existing Netlify site. Covers the MCP SDK + Streamable HTTP transport on a Netlify Function, authentication (single shared secret vs per-user API keys with Netlify Identity), read/write safety, file uploads, and connecting clients. Use even when the user just says "MCP", "tool server for an agent", or "let an AI use my API".

## Questions

### How do I connect Netlify to Krypton?

Open Integrations in Krypton, find Netlify and choose Sign in. Every bot in the workspace can then use it, and you choose which bots get which apps.

### Which plan includes Netlify?

MCP only with 2,000 calls a month, Pro and Max with 20,000. Calls are shared by every catalog app in the workspace. Past the monthly number they keep working from AI credits at $0.90 per 1,000 calls; the count resets on the 1st (UTC) and a retried call counts once.

### Can I use Netlify from Claude or Cursor?

Yes. Connect it in your workspace, then add https://mcp.krypton.bot as a streamable HTTP MCP server with your kmcp_ workspace key. Calls count toward the same monthly number.

Back to the [MCP catalog](https://krypton.bot/mcp-catalog/).