Integration

Render integration

Cloud platform API for deploying and managing web services, databases, and static sites. Create and manage services, deployments, environment variables, and custom domains. Perfect for DevOps automation and infrastructure management.

Connect Render How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Render.Built from the 13 Render tools below, on the connection you add once.

Common Render use cases

Cleanup
Cost saving
Manual deploy
Job monitoring
New deployments
Service recovery
Config management
Domain management
Custom domain setup
Deployment tracking

What you can do with Render

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Service, 7 operations

create_serviceCreate servicePOSTCreates a new service on Render.
delete_serviceDelete serviceDELETEDeletes a service permanently.
get_serviceGet serviceGETRetrieves details of a specific service.
list_servicesList servicesGETRetrieves all services in your account.
resume_serviceResume servicePOSTResumes a suspended service.
suspend_serviceSuspend servicePOSTSuspends a running service.
update_serviceUpdate servicePATCHUpdates service configuration.

Deploy, 2 operations

list_deploysList deploysGETRetrieves deployment history for a service.
trigger_deployTrigger deployPOSTTriggers a new deployment.

Domain, 2 operations

add_custom_domainAdd custom domainPOSTAdds a custom domain to a service.
list_custom_domainsList custom domainsGETRetrieves custom domains for a service.

Env group, 1 operation

list_env_groupsList env groupsGETRetrieves all environment groups.

Job, 1 operation

list_jobsList jobsGETRetrieves one-off job run history for a service.

Use Render from Claude Code, Cursor or Codex

Connect Render in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Render operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Render

Create your workspace
Sign up free. Nothing to install.
Connect Render once
Add your Render connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Render integration FAQ

What can you do with the Render integration?

LiveContext exposes 13 operations on Render, covering service, deploy, domain and env group. Common uses include Cleanup, Cost saving and Manual deploy.