Netlify MCP Server

Netlify's MCP server enables AI agents to manage static site deployments, create new projects, configure environment variables, and manage form submissions. It allows agents to monitor web build statuses, inspect request logs, manage extensions, and streamline modern web development pipelines.

Start for free

Netlify MCP Server

Benefits with Ory + Netlify MCP Server

Netlify's MCP server lets your agents create projects, deploy sites, manage environment variables, and work with forms and extensions in your Netlify team. Environment variables can hold API keys, and a deploy goes straight to your site. Ory Agent Security lets agents check builds and project settings while deployments and configuration changes stay with the agents you approve.

View documentation

Use Cases

— 01 use case

Agent IAM

Status checkers at Read, deploys, project setup and environment variables with Admin agents, Write rarely needed, and Block for agents that never touch Netlify.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Netlify MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for agents checking builds and deploy status, write for agents managing smaller project settings, admin for deployment agents, and no access for agents with no role in your sites.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied deploy stops before it reaches Netlify, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents deploy or change environment variables and for whom without blocking anything, so you can apply Ory's pre-built policy for the Netlify MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Netlify MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent pushed a deploy and which user it acted for.