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 CLI for AI Agents

Use the Netlify CLI from KosmoKrator to call Netlify tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 7 read 0 write Bearer token auth

Submit Netlify feedback View package source

Netlify CLI Setup

Netlify can be configured headlessly with `kosmokrator integrations:configure netlify`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure netlify --set access_token="$NETLIFY_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor netlify --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_token`	`NETLIFY_ACCESS_TOKEN`	Secret `secret`	yes	Personal Access Token
`url`	`NETLIFY_URL`	URL `url`	no	API Base URL

Call Netlify Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call netlify.netlify_get_current_user '{}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:netlify netlify_get_current_user '{}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs netlify --json
kosmo integrations:docs netlify.netlify_get_current_user --json
kosmo integrations:schema netlify.netlify_get_current_user --json
kosmo integrations:search "Netlify" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Netlify.

`netlify.netlify_get_current_user`

Read read

Get details of the currently authenticated Netlify user. Returns user ID, email, name, and account info.

Parameters: none

Generic CLI call

kosmo integrations:call netlify.netlify_get_current_user '{}' --json

Provider shortcut

kosmo integrations:netlify netlify_get_current_user '{}' --json

`netlify.netlify_get_deploy`

Read read

Get detailed information about a specific Netlify deploy, including its state, build log, and commit details.

Parameters: deploy_id

Generic CLI call

kosmo integrations:call netlify.netlify_get_deploy '{"deploy_id":"example_deploy_id"}' --json

Provider shortcut

kosmo integrations:netlify netlify_get_deploy '{"deploy_id":"example_deploy_id"}' --json

`netlify.netlify_get_site`

Read read

Get detailed information about a specific Netlify site, including its ID, name, URL, build settings, and deploy status.

Parameters: site_id

Generic CLI call

kosmo integrations:call netlify.netlify_get_site '{"site_id":"example_site_id"}' --json

Provider shortcut

kosmo integrations:netlify netlify_get_site '{"site_id":"example_site_id"}' --json

`netlify.netlify_list_deploys`

Read read

List deploys for a Netlify site. Returns deploy IDs, states, branches, and commit references.

Parameters: site_id, page, per_page

Generic CLI call

kosmo integrations:call netlify.netlify_list_deploys '{"site_id":"example_site_id","page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:netlify netlify_list_deploys '{"site_id":"example_site_id","page":1,"per_page":1}' --json

`netlify.netlify_list_dns_zones`

Read read

List all DNS zones configured in Netlify. Returns zone IDs, domain names, and nameservers.

Parameters: page, per_page

Generic CLI call

kosmo integrations:call netlify.netlify_list_dns_zones '{"page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:netlify netlify_list_dns_zones '{"page":1,"per_page":1}' --json

`netlify.netlify_list_forms`

Read read

List all forms for a Netlify site. Returns form IDs, names, paths, and submission counts.

Parameters: site_id

Generic CLI call

kosmo integrations:call netlify.netlify_list_forms '{"site_id":"example_site_id"}' --json

Provider shortcut

kosmo integrations:netlify netlify_list_forms '{"site_id":"example_site_id"}' --json

`netlify.netlify_list_sites`

Read 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.

Parameters: name, page, per_page

Generic CLI call

kosmo integrations:call netlify.netlify_list_sites '{"name":"example_name","page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:netlify netlify_list_sites '{"name":"example_name","page":1,"per_page":1}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`netlify.netlify_get_current_user`

Get details of the currently authenticated Netlify user. Returns user ID, email, name, and account info.

Operation: Read read
Schema command: kosmo integrations:schema netlify.netlify_get_current_user --json

Parameter	Type	Required	Description
No parameters.

`netlify.netlify_get_deploy`

Get detailed information about a specific Netlify deploy, including its state, build log, and commit details.

Operation: Read read
Schema command: kosmo integrations:schema netlify.netlify_get_deploy --json

Parameter	Type	Required	Description
`deploy_id`	string	yes	The deploy identifier.

`netlify.netlify_get_site`

Get detailed information about a specific Netlify site, including its ID, name, URL, build settings, and deploy status.

Operation: Read read
Schema command: kosmo integrations:schema netlify.netlify_get_site --json

Parameter	Type	Required	Description
`site_id`	string	yes	The site identifier or site name (e.g., "abc123" or "mysite.netlify.app").

`netlify.netlify_list_deploys`

List deploys for a Netlify site. Returns deploy IDs, states, branches, and commit references.

Operation: Read read
Schema command: kosmo integrations:schema netlify.netlify_list_deploys --json

Parameter	Type	Required	Description
`site_id`	string	yes	The site identifier.
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of deploys per page (default: 30).

`netlify.netlify_list_dns_zones`

List all DNS zones configured in Netlify. Returns zone IDs, domain names, and nameservers.

Operation: Read read
Schema command: kosmo integrations:schema netlify.netlify_list_dns_zones --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination.
`per_page`	integer	no	Number of DNS zones per page.

`netlify.netlify_list_forms`

List all forms for a Netlify site. Returns form IDs, names, paths, and submission counts.

Operation: Read read
Schema command: kosmo integrations:schema netlify.netlify_list_forms --json

Parameter	Type	Required	Description
`site_id`	string	yes	The site identifier.

`netlify.netlify_list_sites`

List all Netlify sites. Returns site IDs, names, URLs, and build status. Use this to discover site identifiers needed for deploy and form operations.

Operation: Read read
Schema command: kosmo integrations:schema netlify.netlify_list_sites --json

Parameter	Type	Required	Description
`name`	string	no	Filter by site name.
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of sites per page (default: 30).

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.