Can I use Render as a CLI?

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

Can I expose Render through MCP?

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

Where are Render credentials stored?

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

Can I deny write access for Render MCP tools?

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

productivity

Render CLI for Headless Automation

Use the Render CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API key auth

Submit Render feedback View package source

Render CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Render CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Render CLI for Headless Automation
kosmokrator integrations:configure render2 --set api_key="$RENDER2_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call render2.render_list_services '{"limit":1,"cursor":"example_cursor"}' --json

Discovery Before Execution

Agents and scripts can inspect Render docs and schemas before choosing a function.

kosmo integrations:docs render2 --json
kosmo integrations:docs render2.render_list_services --json
kosmo integrations:schema render2.render_list_services --json
kosmo integrations:search "Render" --json
kosmo integrations:list --json

Useful Render CLI Functions

Function	Type	Parameters	Description
`render2.render_list_services`	Read	limit, cursor	List all services in the Render account. Returns service IDs, names, type, status, and URLs.
`render2.render_get_service`	Read	service_id	Get details for a specific Render service by ID. Returns full service information including type, status, URLs, and configuration.
`render2.render_create_service`	Write	type, name, repo, branch, region, plan, runtime, build_command, start_command, env_vars	Create a new service on Render. Supports web services, background workers, cron jobs, and private services.
`render2.render_list_deploys`	Read	service_id, limit, cursor	List deploys for a specific Render service. Returns deploy IDs, status, commit info, and timestamps.
`render2.render_get_deploy`	Read	deploy_id	Get details for a specific Render deploy by ID. Returns full deploy information including status, commit, and logs.
`render2.render_list_jobs`	Read	service_id, limit, cursor	List jobs for a specific Render service. Returns job IDs, status, start command, and timestamps.
`render2.render_get_current_user`	Read	none	Get information about the current authenticated Render account, including email, name, and plan.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Render CLI Pages

CI Render CLI for CI. Cron Jobs Render CLI for cron jobs. Shell Scripts Render CLI for shell scripts. Coding Agents Render CLI for coding agents.