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

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

7 functions 6 read 1 write API key auth

Submit Render feedback View package source

Render CLI Setup

Render can be configured headlessly with `kosmokrator integrations:configure render2`.

# 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 render2 --set api_key="$RENDER2_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor render2 --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. 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
`api_key`	`RENDER2_API_KEY`	Secret `secret`	yes	API Key
`url`	`RENDER2_URL`	URL `url`	no	API Base URL

Call Render Headlessly

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

kosmo integrations:call render2.render_list_services '{
  "limit": 1,
  "cursor": "example_cursor"
}' --json

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

kosmo integrations:render2 render_list_services '{
  "limit": 1,
  "cursor": "example_cursor"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities 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

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

`render2.render_list_services`

Read read

List all services in the Render account. Returns service IDs, names, type, status, and URLs.

Parameters: limit, cursor

Generic CLI call

kosmo integrations:call render2.render_list_services '{"limit":1,"cursor":"example_cursor"}' --json

Provider shortcut

kosmo integrations:render2 render_list_services '{"limit":1,"cursor":"example_cursor"}' --json

`render2.render_get_service`

Read read

Get details for a specific Render service by ID. Returns full service information including type, status, URLs, and configuration.

Parameters: service_id

Generic CLI call

kosmo integrations:call render2.render_get_service '{"service_id":"example_service_id"}' --json

Provider shortcut

kosmo integrations:render2 render_get_service '{"service_id":"example_service_id"}' --json

`render2.render_create_service`

Write write

Create a new service on Render. Supports web services, background workers, cron jobs, and private services.

Parameters: type, name, repo, branch, region, plan, runtime, build_command, start_command, env_vars

Generic CLI call

kosmo integrations:call render2.render_create_service '{"type":"example_type","name":"example_name","repo":"example_repo","branch":"example_branch","region":"example_region","plan":"example_plan","runtime":"example_runtime","build_command":"example_build_command"}' --json

Provider shortcut

kosmo integrations:render2 render_create_service '{"type":"example_type","name":"example_name","repo":"example_repo","branch":"example_branch","region":"example_region","plan":"example_plan","runtime":"example_runtime","build_command":"example_build_command"}' --json

`render2.render_list_deploys`

Read read

List deploys for a specific Render service. Returns deploy IDs, status, commit info, and timestamps.

Parameters: service_id, limit, cursor

Generic CLI call

kosmo integrations:call render2.render_list_deploys '{"service_id":"example_service_id","limit":1,"cursor":"example_cursor"}' --json

Provider shortcut

kosmo integrations:render2 render_list_deploys '{"service_id":"example_service_id","limit":1,"cursor":"example_cursor"}' --json

`render2.render_get_deploy`

Read read

Get details for a specific Render deploy by ID. Returns full deploy information including status, commit, and logs.

Parameters: deploy_id

Generic CLI call

kosmo integrations:call render2.render_get_deploy '{"deploy_id":"example_deploy_id"}' --json

Provider shortcut

kosmo integrations:render2 render_get_deploy '{"deploy_id":"example_deploy_id"}' --json

`render2.render_list_jobs`

Read read

List jobs for a specific Render service. Returns job IDs, status, start command, and timestamps.

Parameters: service_id, limit, cursor

Generic CLI call

kosmo integrations:call render2.render_list_jobs '{"service_id":"example_service_id","limit":1,"cursor":"example_cursor"}' --json

Provider shortcut

kosmo integrations:render2 render_list_jobs '{"service_id":"example_service_id","limit":1,"cursor":"example_cursor"}' --json

`render2.render_get_current_user`

Read read

Get information about the current authenticated Render account, including email, name, and plan.

Parameters: none

Generic CLI call

kosmo integrations:call render2.render_get_current_user '{}' --json

Provider shortcut

kosmo integrations:render2 render_get_current_user '{}' --json

Function Schemas

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

`render2.render_list_services`

List all services in the Render account. Returns service IDs, names, type, status, and URLs.

Operation: Read read
Schema command: kosmo integrations:schema render2.render_list_services --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of services to return per page (default: 20, max: 100).
`cursor`	string	no	Pagination cursor from a previous response.

`render2.render_get_service`

Get details for a specific Render service by ID. Returns full service information including type, status, URLs, and configuration.

Operation: Read read
Schema command: kosmo integrations:schema render2.render_get_service --json

Parameter	Type	Required	Description
`service_id`	string	yes	The service ID (e.g., "srv-cabc12345678").

`render2.render_create_service`

Create a new service on Render. Supports web services, background workers, cron jobs, and private services.

Operation: Write write
Schema command: kosmo integrations:schema render2.render_create_service --json

Parameter	Type	Required	Description
`type`	string	yes	Service type: "web_service", "background_worker", "cron_job", or "private_service".
`name`	string	yes	The name for the service.
`repo`	string	yes	The Git repository URL (e.g., "https://github.com/user/repo").
`branch`	string	no	The Git branch to deploy (default: "main").
`region`	string	no	Region slug (e.g., "oregon", "ohio", "frankfurt", "singapore").
`plan`	string	no	Plan type: "starter", "standard", "pro", "pro_plus" (default: "starter").
`runtime`	string	no	Runtime for the service (e.g., "node", "python", "ruby", "docker").
`build_command`	string	no	Shell command to build the service.
`start_command`	string	no	Shell command to start the service.
`env_vars`	object	no	Environment variables as key-value pairs.

`render2.render_list_deploys`

List deploys for a specific Render service. Returns deploy IDs, status, commit info, and timestamps.

Operation: Read read
Schema command: kosmo integrations:schema render2.render_list_deploys --json

Parameter	Type	Required	Description
`service_id`	string	yes	The service ID to list deploys for.
`limit`	integer	no	Number of deploys to return per page (default: 20, max: 100).
`cursor`	string	no	Pagination cursor from a previous response.

`render2.render_get_deploy`

Get details for a specific Render deploy by ID. Returns full deploy information including status, commit, and logs.

Operation: Read read
Schema command: kosmo integrations:schema render2.render_get_deploy --json

Parameter	Type	Required	Description
`deploy_id`	string	yes	The deploy ID (e.g., "dep-cabc12345678").

`render2.render_list_jobs`

List jobs for a specific Render service. Returns job IDs, status, start command, and timestamps.

Operation: Read read
Schema command: kosmo integrations:schema render2.render_list_jobs --json

Parameter	Type	Required	Description
`service_id`	string	yes	The service ID to list jobs for.
`limit`	integer	no	Number of jobs to return per page (default: 20, max: 100).
`cursor`	string	no	Pagination cursor from a previous response.

`render2.render_get_current_user`

Get information about the current authenticated Render account, including email, name, and plan.

Operation: Read read
Schema command: kosmo integrations:schema render2.render_get_current_user --json

Parameter	Type	Required	Description
No parameters.

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.