Menu
Mattering Automations connector

Render MCP access for automations that run your deploys

Connect Render once and your services, deploys, custom domains, environment variables, one-off jobs, Postgres, and Key Value instances become building blocks for visual automations and AI agent workflows. 60 nodes over Render's REST API, with one API key credential.

60 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Render MCP connector does

The Render connector for Mattering Automations covers the operations Render publishes on its REST API: list, create, update, suspend, resume, restart, and delete services, trigger, cancel, and roll back deploys, manage custom domains and their DNS verification, set environment variables directly or through shared environment groups, run one-off jobs and cron job runs, provision and recover Postgres, read Key Value connection details, manage persistent disks and registry credentials, and query logs, service events, notification settings, and platform maintenance windows. That is 60 nodes in total: 29 read nodes and 31 action nodes.

Each capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, and they also power Matter, the platform's built-in AI assistant. Describe the deployment workflow you want in plain language and it gets built on the canvas in front of you, where you can see every step and change it before anything touches production.

Render also ships its own official MCP server, hosted at mcp.render.com, built for managing Render from AI development tools such as Claude Code and Cursor. It is a good fit for that job, and nothing here replaces it. The Render nodes on Mattering serve a different one: durable workflows that run on a schedule or an event, branch on conditions, and combine Render with the rest of your stack, so a failed deploy can roll itself back, pull its own logs, and open an assigned task without an editor session open anywhere. The same nodes are then exposed over MCP for assistants, so you get both surfaces from one credential.

The catalog is honest about its edges. Render's metrics charting endpoints, Blueprints, and the new Workflows product surface are deliberately not covered yet, and there are no Redis nodes because Render's Redis endpoints are deprecated: the Key Value nodes cover the current product. Six nodes are destructive, including Render: Replace All Env Vars, and each one says so plainly in its description rather than hiding it.

One connection, three surfaces

  • Visual automations. Drag Render nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Render node, ready to drop on the canvas

60 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 29

Render: Get Custom Domain

Fetch one custom domain by id or name: verification status, domain type and redirect pairing.

Render: Get Deploy

Fetch one deploy: commit or image reference, status, trigger and timestamps. Poll this after triggering a deploy to watch it go live.

Render: Get Disk

Fetch one persistent disk: size, mount path and attached service.

Render: Get Env Group

Fetch one environment group including its env vars, secret files and linked services. WARNING: the response contains each variable's plaintext value, and node outputs are stored in automation execution records.

Render: Get Event

Fetch one event by id with its full details payload.

Render: Get Job

Fetch one one-off job: start command, plan, status and timestamps. Poll this after Render: Create Job to watch it finish.

Render: Get Key Value Connection Info

Fetch a Key Value instance's connection details: internal and external connection strings and a ready CLI command. WARNING: the response contains LIVE credentials (password and connection strings) and node outputs are stored in automation execution records, so running this copies the credentials into execution history.

Render: Get Key Value Instance

Fetch one Key Value instance: plan, region, status, eviction policy, persistence mode and IP allow list.

Render: Get Maintenance Run

Fetch one maintenance run: state, scheduled time, deadline and the affected resource.

Render: Get Notification Settings

Fetch a workspace's notification settings: email and Slack toggles, preview-environment notifications and which events notify (none, failure or all).

Render: Get Postgres Connection Info

Fetch a Postgres instance's connection details: password, internal and external connection strings and a ready psql command. WARNING: the response contains LIVE credentials (password and connection strings) and node outputs are stored in automation execution records, so running this copies the credentials into execution history.

Render: Get Postgres Instance

Fetch one Postgres instance: version, plan, disk size, status, IP allow list and dashboard URL. Connection strings live on the separate connection-info node.

Render: Get Postgres Recovery Info

Check a Postgres instance's point-in-time recovery status: AVAILABLE, BACKUP_NOT_READY or NOT_AVAILABLE, plus the start of the recovery window.

Render: Get Service

Fetch one service by id: type, repo, branch, plan, region, URL, suspension state and the type-specific serviceDetails block.

Render: Get Workspace

Fetch one workspace (owner) by id: name, email and type. Use the id as the ownerId when creating services or databases.

Render: List Custom Domains

List a service's custom domains with type (apex or subdomain), verification status and any redirect pairing.

Render: List Deploys

List a service's deploys newest first: commit, status (live, build_failed, canceled...), trigger and timestamps. The first live deploy's id is what rollback needs.

Render: List Disks

List persistent disks with size, mount path and the service each disk is attached to.

Render: List Env Groups

List environment groups (shared sets of env vars and secret files) with the services each group is linked to.

Render: List Env Vars

List the environment variables set directly on a service (variables from linked environment groups are NOT included). WARNING: the response contains each variable's plaintext value, and node outputs are stored in automation execution records.

Render: List Jobs

List one-off jobs run against a service with their start command, status and timestamps.

Render: List Key Value Instances

List Render Key Value instances (Redis-compatible, Valkey backed) with plan, region, status, eviction policy and persistence mode. Supersedes the deprecated Redis endpoints.

Render: List Logs

Query logs across services, cron jobs, jobs and Postgres instances with text, level, status-code and path filters (wildcards supported). Returns up to 100 lines plus hasMore/nextStartTime for continuing. Rate limited to 30 log reads per minute.

Render: List Maintenance Runs

List scheduled and past platform maintenance runs for services, Postgres and Key Value instances so automations can anticipate maintenance windows.

Render: List Postgres Instances

List Render Postgres instances with version, plan, disk size, region, status and suspension state.

Render: List Registry Credentials

List container registry credentials (Docker Hub, GitHub, GitLab, Google Artifact Registry, AWS ECR) available for image-backed services. Auth tokens are never returned.

Render: List Service Events

List a service's activity events (build_started, deploy_ended, suspension changes...) newest first. Defaults to the last hour; widen with startTime/endTime. Useful as a polling trigger source for deploy outcomes.

Render: List Services

List services (web services, static sites, private services, background workers and cron jobs) with repo, branch, region, plan, URL and suspension state. Filter by name, type, region, workspace or timestamps; page with cursor/limit.

Render: List Workspaces

List the workspaces (owners) the API key can access, with each workspace's id (the ownerId that service and Postgres creation require), name, email and type (user or team). A Render API key is user-scoped and reaches every workspace its user belongs to.

Action nodes 31

Render: Add Custom Domain

Attach a custom domain to a service. Adding an apex domain also creates its www subdomain (and vice versa) as a redirect. DNS must then be pointed at Render and verified. Rate limited to 50 custom-domain calls per hour.

Render: Add Disk

Attach a new persistent disk to a service. Disks are BILLABLE per GB per month and attaching one redeploys the service (and removes its ability to scale to multiple instances).

Render: Cancel Deploy

Cancel an in-progress deploy. The previously live deploy stays live. Not supported for cron jobs.

Render: Cancel Job

Cancel a running one-off job. Returns the job with its updated status.

Render: Create Env Group

Create an environment group of shared env vars (and optional secret files) and optionally link it to services in the same call.

Render: Create Job

Run a one-off job (an arbitrary command) using a service's environment and most recent build. The job runs on billable compute (per-second on the chosen plan). Rate limited to 100 job creations per minute.

Render: Create Postgres Instance

Create a Render Postgres instance. Paid plans begin billing immediately; the free plan allows one instance per workspace with 1 GB storage that EXPIRES 30 days after creation (14-day grace period before deletion).

Render: Create Registry Credential

Store a container registry credential for pulling private images into image-backed services.

Render: Create Service

Create a service (web service, static site, private service, background worker or cron job) from a Git repo or a container image and start its first build. Paid instance types begin billing immediately; the first deploy consumes pipeline minutes. Rate limited to 20 service creations per hour.

Render: Delete Custom Domain

Detach a custom domain from a service. The domain stops routing to the service immediately; re-adding it requires DNS re-verification.

Render: Delete Env Var

Delete one environment variable from a service. The value is gone unless you captured it first (Render: List Env Vars). Takes effect on the next deploy.

Render: Delete Postgres Instance

Permanently delete a Postgres instance AND ITS DATA. IRREVERSIBLE outside the point-in-time recovery window.

Render: Delete Registry Credential

Delete a registry credential. Services still configured to use it will fail to pull their image on the next deploy.

Render: Delete Service

Permanently delete a service, its deploys and its custom domain attachments. IRREVERSIBLE: the service and its history cannot be recovered.

Render: Link Env Group To Service

Link an environment group to a service so the service receives all of the group's env vars and secret files. Reversible with Render: Unlink Env Group From Service.

Render: Replace All Env Vars

REPLACE the full set of environment variables on a service: any existing variable not present in the submitted array is DELETED. To change one variable without touching the rest use Render: Set Env Var instead. Changes take effect on the next deploy.

Render: Restart Service

Restart a service's running instances without rebuilding. Brief downtime while instances cycle; no pipeline minutes consumed.

Render: Resume Postgres Instance

Resume a suspended Postgres instance so it accepts connections again.

Render: Resume Service

Resume a suspended service so it deploys and serves traffic again. Rate limited to 10 per minute per service.

Render: Rollback Deploy

Roll a service back to a previous deploy by id. Rollback does NOT disable autodeploy: the next commit on the connected branch will deploy over the rollback unless autoDeploy is set to no first (Render: Update Service).

Render: Run Cron Job Now

Trigger an immediate run of a cron job service outside its schedule. CANCELS any currently active run of the same cron job first. The run consumes billable compute like a scheduled run.

Render: Set Env Var

Add or update ONE environment variable on a service without touching the others. Provide value, or set generateValue true to have Render generate one. Applies only to variables set directly on the service, not linked environment groups. Takes effect on the next deploy.

Render: Suspend Postgres Instance

Suspend a Postgres instance: it stops accepting connections until resumed. Data is retained. Reversible with Render: Resume Postgres Instance.

Render: Suspend Service

Suspend a running service: it stops serving traffic and stops accruing instance charges until resumed. Reversible with Render: Resume Service. Rate limited to 10 per minute per service.

Render: Trigger Deploy

Trigger a new deploy of a service - the latest commit by default, or a specific commit or image. This runs a real build that consumes the workspace's monthly pipeline minutes; beyond the included allowance Render bills or suspends. Render also rate-limits deploy calls to 10 per minute per service.

Render: Trigger Postgres Recovery

Restore a Postgres instance to a point in time. Render creates a NEW instance from the recovery point (the source is untouched); the new instance bills on its plan. Check Render: Get Postgres Recovery Info first.

Render: Unlink Env Group From Service

Unlink an environment group from a service: the service loses access to the group's env vars and secret files. The group itself is untouched and can be re-linked.

Render: Update Disk

Update a persistent disk's name, size or mount path. Size can only GROW (growing raises the monthly charge); it can never shrink. Changes trigger a service redeploy.

Render: Update Notification Settings

Update a workspace's notification settings. Only the fields you send change.

Render: Update Service

Update a service's settings (name, branch, auto-deploy, root directory, build filter, type-specific details). Only the fields you send change. Rate limited to 10 per minute per service.

Render: Verify Custom Domain DNS

Trigger a re-check of a custom domain's DNS configuration (returns 202; poll Render: Get Custom Domain for the resulting verificationStatus). Harmless to repeat; counts against the 50-per-hour custom-domain rate limit.

Connecting Render takes one credential

Render authenticates with an API key sent as an Authorization Bearer header. You can create an API key from Account Settings in the Render dashboard on any plan. The key is user-scoped rather than workspace-scoped: Render's documentation states that an API key provides access to all workspaces you belong to, so treat it like a password and store it only as an encrypted credential.

1

In the Render dashboard, open Account Settings, find the API Keys section, create a new API key, and copy the value somewhere safe.

2

In Mattering Automations, open Connectors, click Add Connector, and choose Render.

3

Create a new credential, paste the API key, and save. Credentials are stored encrypted in Google Secret Manager and never appear in workflow logs.

4

Click Test Connection. The connector calls Render's workspaces endpoint with your key, so a passing test means the key authenticates against the live API.

5

Connect, then drop Render: List Workspaces onto a canvas and run it. It needs no parameters and returns each workspace with its id, which is the ownerId that service and database creation nodes require. All 60 Render nodes are now in your palette.

Common uses for the Render MCP

Deploy from a schedule, an event, or a chat message

Trigger a deployment when a release checklist closes, on a timer, or on an agent's instruction. Render: Trigger Deploy ships the latest commit by default or pins a specific commit or image, and Render: Get Deploy polls the result until it goes live, so the workflow knows whether the ship actually landed.

Roll back automatically when a deploy fails

Poll Render: List Deploys, branch when the newest deploy failed, and call Render: Rollback Deploy against the last deploy that went live. Rollback does not disable autodeploy, so the same workflow can call Render: Update Service to switch autoDeploy off until a human clears the incident.

Triage incidents with the evidence attached

Render: List Logs filters logs by text, level, status code, and path across services and databases, and Render: List Service Events shows what the platform did and when. Feed both into an AI summary step and post the result to a task or a channel, so whoever picks it up starts with the failure, not a dashboard link.

Manage environment variables without hand edits

Render: Set Env Var changes one variable and leaves the rest alone, which makes it the safe default for workflows. Shared configuration lives in groups: Render: Create Env Group builds a set once and Render: Link Env Group To Service rolls it out to each service that needs it.

Provision and protect Postgres

Render: Create Postgres Instance provisions a database in a workflow, Render: Get Postgres Recovery Info checks whether point-in-time recovery is available before you need it, and Render: Trigger Postgres Recovery restores to a new instance while leaving the source untouched. Suspend and resume nodes park a database without losing data.

Run one-off jobs and cron runs on demand

Render: Create Job runs an arbitrary command, such as a migration or a backfill, using a service's environment and most recent build, and Render: Run Cron Job Now fires a cron job outside its schedule. Render: Get Job polls the outcome so the next step only runs when the job finished.

Example: A failed deploy rolls itself back and opens a task

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule runs every few minutes after a release goes out.

2

Render: List Deploys returns the service's deploys newest first, with each deploy's status.

3

A condition node branches when the newest deploy's status is build_failed or update_failed.

4

Render: List Logs pulls the failing build's log lines so the reason travels with the alert.

5

Render: Rollback Deploy restores the most recent deploy whose status was live.

6

Render: Update Service sets autoDeploy to no, so the next push cannot deploy over the rollback while the incident is open.

7

Mattering Productivity: a task is created with the service name, the failed deploy id, and the log excerpt, so the fix has an owner instead of a scroll of alerts.

Render MCP questions, answered

Render ships its own official MCP server. How is this different?

It does: Render's hosted MCP server at mcp.render.com lets AI development tools such as Claude Code and Cursor manage Render directly, and it is the right choice for working on Render from inside an editor. The Render nodes on Mattering are built for a different job: automations that keep running when no editor is open. They are steps on a visual canvas with schedules, conditions, and approvals, they chain with nodes for GitHub, Slack, Mattering Productivity, and the rest of the connector catalog, and they are also exposed over MCP for assistants. Plenty of teams will sensibly use both.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Render through them. Matter, the assistant built into the platform, uses the same nodes natively.

What credential does the connector need, and is the API available on Render's free plan?

It needs a Render API key, sent as an Authorization Bearer header. You can create one from Account Settings in the Render dashboard on any plan, and Render's documentation does not gate the REST API behind a paid tier. The key is user-scoped: Render states that an API key provides access to all workspaces you belong to. Render's free offering is enough to try the connector end to end, with the documented limits: free web services share 750 free instance hours per workspace per month and spin down after 15 minutes of idle time, and a free Postgres instance is limited to one per workspace at 1 GB and expires 30 days after creation.

Can an AI agent deploy, cancel, and roll back Render services?

Yes. Render: Trigger Deploy starts a deploy of the latest commit or a pinned commit or image, Render: Cancel Deploy stops one in progress, and Render: Rollback Deploy restores a previous deploy by id. Two honest caveats: deploys run real builds that consume your workspace's monthly pipeline minutes, and Render rate-limits deploy, suspend, resume, and service update calls to 10 per minute per service. Also note that a rollback does not disable autodeploy, so the next push to the connected branch will deploy over it unless Render: Update Service turns autoDeploy off first.

What are Render's API rate limits?

Render documents them per family: GET requests are limited to 400 per minute in general and other requests to 30 per minute, with tighter caps on specific endpoints, including 20 service creations per hour, 10 deploy, suspend, resume, or service update calls per minute per service, 50 custom domain calls per hour, 100 job creations per minute, and 30 log reads per minute. Responses carry Ratelimit-Limit, Ratelimit-Remaining, and Ratelimit-Reset headers, and a breach returns HTTP 429. Node descriptions state the per-endpoint caps where they bite.

Which nodes are destructive?

Six: Render: Delete Service, Render: Delete Postgres Instance, Render: Delete Custom Domain, Render: Delete Env Var, Render: Delete Registry Credential, and Render: Replace All Env Vars. The last one deserves the most respect: it replaces the full set of environment variables on a service, so any variable missing from the submitted array is deleted. Render: Set Env Var changes one variable safely, and Render: Suspend Service parks a service reversibly, so the destructive nodes are rarely the ones a workflow actually needs. Put a condition or an approval step in front of any of them.

Is it safe to read environment variables and database connection strings in an automation?

Read them deliberately. Render: Get Postgres Connection Info and Render: Get Key Value Connection Info return live passwords and connection strings, and Render: List Env Vars and Render: Get Env Group return plaintext variable values. Node outputs are stored in automation execution records, so running these nodes copies those values into execution history. Use them only where the workflow genuinely needs a value, and never wire their output into a logging, message, or notification node.

Why do list results look like data[0].service.id instead of data[0].id?

That is Render's real response shape, kept intact so field paths on the canvas match the API documentation. List endpoints return an array of wrapper objects, each holding the entity and a cursor side by side, so a service list reads from data[0].service and its pagination cursor from data[0].cursor. To page, pass the last item's cursor back to the same node; list nodes accept a limit from 1 to 100, defaulting to 20.

60 nodes waiting on the canvas

Put Render to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Render is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products