Can I use Netlify as a CLI?

Yes. KosmoKrator exposes a Netlify CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Netlify through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Netlify tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Netlify credentials stored?

Netlify credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Netlify MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Netlify MCP Integration for CrewAI

Connect Netlify to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Bearer token auth

Submit Netlify feedback View package source

Connect Netlify to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Netlify MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-netlify": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=netlify",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=netlify --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Netlify instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Netlify Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Netlify integration catalog.

MCP tool	Source function	Type	Description
`integration__netlify__netlify_get_current_user`	`netlify.netlify_get_current_user`	Read	Get details of the currently authenticated Netlify user. Returns user ID, email, name, and account info.
`integration__netlify__netlify_get_deploy`	`netlify.netlify_get_deploy`	Read	Get detailed information about a specific Netlify deploy, including its state, build log, and commit details.
`integration__netlify__netlify_get_site`	`netlify.netlify_get_site`	Read	Get detailed information about a specific Netlify site, including its ID, name, URL, build settings, and deploy status.
`integration__netlify__netlify_list_deploys`	`netlify.netlify_list_deploys`	Read	List deploys for a Netlify site. Returns deploy IDs, states, branches, and commit references.
`integration__netlify__netlify_list_dns_zones`	`netlify.netlify_list_dns_zones`	Read	List all DNS zones configured in Netlify. Returns zone IDs, domain names, and nameservers.
`integration__netlify__netlify_list_forms`	`netlify.netlify_list_forms`	Read	List all forms for a Netlify site. Returns form IDs, names, paths, and submission counts.
`integration__netlify__netlify_list_sites`	`netlify.netlify_list_sites`	Read	List all Netlify sites. Returns site IDs, names, URLs, and build status. Use this to discover site identifiers needed for deploy and form operations.

Related Netlify Pages

Netlify CLIUse direct JSON commands instead of MCP discovery. Netlify MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.