Netlify MCP 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南
Netlify 官方远程 MCP 服务器。AI 代理可通过 OAuth 列出站点与部署、读取构建日志、管理环境变量并触发部署。
本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"netlify": {
"url": "https://netlify-mcp.netlify.app/mcp"
}
}
}claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"netlify": {
"type": "http",
"url": "https://netlify-mcp.netlify.app/mcp"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://netlify-mcp.netlify.app/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"netlify": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://netlify-mcp.netlify.app/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"netlify": {
"serverUrl": "https://netlify-mcp.netlify.app/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"netlify": {
"url": "https://netlify-mcp.netlify.app/mcp"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.netlify] url = "https://netlify-mcp.netlify.app/mcp"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"netlify": {
"type": "streamableHttp",
"url": "https://netlify-mcp.netlify.app/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"netlify": {
"httpUrl": "https://netlify-mcp.netlify.app/mcp"
}
}
}🧰 Netlify MCP 工具与 Schema(13)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| search_netlify_docs ~31 tok | 🟢 Read | Search Netlify documentation. | — |
| list-sites ~27 tok | 🟢 Read | List Netlify sites. | — |
| get-site ~29 tok | 🟢 Read | Get details of a Netlify site. | — |
| create-site ~28 tok | 🟠 Write | Create a Netlify site. | — |
| deploy-site ~29 tok | 🟠 Write | Trigger a site deployment. | — |
| list-deploys ~28 tok | 🟢 Read | List deploys of a site. | — |
| get-deploy ~28 tok | 🟢 Read | Get details of a deploy. | — |
| get-deploy-log ~30 tok | 🟢 Read | Get the build log of a deploy. | — |
| list-forms ~27 tok | 🟢 Read | List forms of a site. | — |
| list-env-vars ~29 tok | 🟢 Read | List environment variables. | — |
| set-env-var ~29 tok | 🟠 Write | Set an environment variable. | — |
| lock-deploy ~29 tok | 🟠 Write | Lock a deploy to production. | — |
| unlock-deploy ~31 tok | 🟠 Write | Unlock a locked production deploy. | — |
🛡️ 安全评级、质量与上下文 Token 审计
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 与安全
- 认证方式
- OAuth 2.1
- 动态客户端注册(DCR)
- ✅ 支持
- PKCE S256
- ✅ 支持
- 受保护资源元数据
- https://netlify-mcp.netlify.app/.well-known/oauth-protected-resource
📡 官方远程端点与传输协议
远程端点 https://netlify-mcp.netlify.app/mcp 采用 Streamable HTTP(流式 HTTP,2025-03-26 规范)。Streamable HTTP 在单一 POST 端点上完成 JSON-RPC 双向交互,是当前 MCP 规范推荐的传输方式,可直接被 Claude、Cursor、VS Code 等客户端以 URL 形式接入,无需 npx mcp-remote 桥接。
接入前可将端点粘贴至本站 在线 MCP Inspector 实测 initialize / tools/list 握手,确认真实协议行为。
🔐 认证与权限机制
认证方式为 OAuth 2.1。首次连接时客户端会收到 401 挑战并从 WWW-Authenticate 头解析 RFC 9728 受保护资源元数据,随后自动完成授权服务器发现(RFC 8414)、动态客户端注册(DCR)与 PKCE S256 浏览器授权流程——你只需在浏览器中点击一次授权,无需手工粘贴任何密钥。
🛡️ 上下文开销与安全审计
该服务端当前登记 13 个工具,全部定义合计约 395 tokens,会在每次请求时注入模型系统提示词。安全评级为 A+,官方直营来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。
🧩 主流客户端快速接入
本站为 Netlify MCP 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。代表性工具包括 search_netlify_docs、list-sites、get-site、create-site、deploy-site 等。
📖 Netlify 详解
Netlify MCP — Remote MCP Server
Netlify's remote MCP covers the deploy lifecycle — enumerate sites, watch deploy progress, read build logs for failures, and set environment variables — the classic 'why did my build fail' workflow directly in chat.
Official Netlify MCP Endpoint & Transport Architecture
- Endpoint URL:
https://netlify-mcp.netlify.app/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Netlify MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Netlify MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.
Of the 6 cataloged tools, 4 are read-only and 2 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely. - OAuth is per Netlify user; agents see the sites your account can administer.
- Deploy triggers respect your site's build hooks and branch rules.
🚀 如何接入 Netlify MCP 远程 MCP
- 获取远程端点 — 复制官方端点 https://netlify-mcp.netlify.app/mcp。
- 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL(见下方分客户端指南)。
- 授权并验证 — 完成浏览器 OAuth 授权后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。
🔌 Netlify × 各客户端连接指南
❓ 常见问题
Netlify MCP 远程 MCP 服务器是官方提供的吗?
本条目标记为「官方直营」。端点由 Netlify 官方运营,所有收录端点均经过真实 MCP initialize 握手验证。
如何在 Claude / Cursor 中连接 Netlify MCP?
复制远程端点 https://netlify-mcp.netlify.app/mcp:Claude Code 执行 claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "netlify": { "url": "https://netlify-mcp.netlify.app/mcp" } } }。首次调用会自动弹出 OAuth 2.1 授权页面。
连接时返回 401 或需要密钥怎么办?
401 是 OAuth 2.1 的正常挑战响应——客户端会依据 RFC 9728 元数据自动完成授权,无需手工处理。若授权流程中断,可用本站 OAuth 2.1 Debugger 定位 PRM / DCR / CORS 配置问题。
本地 stdio MCP 和这个远程 MCP 有什么区别?
本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 Netlify 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。