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 MCP Integration for Vercel AI SDK

Connect Render to Vercel AI SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API key auth

Submit Render feedback View package source

Connect Render to Vercel AI SDK

Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts.

Create an MCP client that starts or connects to the KosmoKrator gateway for the selected integration. The gateway is local, scoped to this integration, and starts with --write=deny so Vercel AI SDK can inspect read-capable tools without receiving write access by default.

Render MCP Config for Vercel AI SDK

Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Render Tools Visible to Vercel AI SDK

Vercel AI SDK sees stable MCP tool names generated from the Render integration catalog.

MCP tool	Source function	Type	Description
`integration__render2__render_list_services`	`render2.render_list_services`	Read	List all services in the Render account. Returns service IDs, names, type, status, and URLs.
`integration__render2__render_get_service`	`render2.render_get_service`	Read	Get details for a specific Render service by ID. Returns full service information including type, status, URLs, and configuration.
`integration__render2__render_create_service`	`render2.render_create_service`	Write	Create a new service on Render. Supports web services, background workers, cron jobs, and private services.
`integration__render2__render_list_deploys`	`render2.render_list_deploys`	Read	List deploys for a specific Render service. Returns deploy IDs, status, commit info, and timestamps.
`integration__render2__render_get_deploy`	`render2.render_get_deploy`	Read	Get details for a specific Render deploy by ID. Returns full deploy information including status, commit, and logs.
`integration__render2__render_list_jobs`	`render2.render_list_jobs`	Read	List jobs for a specific Render service. Returns job IDs, status, start command, and timestamps.
`integration__render2__render_get_current_user`	`render2.render_get_current_user`	Read	Get information about the current authenticated Render account, including email, name, and plan.

Related Render Pages

Render CLIUse direct JSON commands instead of MCP discovery. Render MCPFull gateway reference and MCP tool names. KosmoKrator for Vercel AI SDKClient-level gateway setup.