← All integrations

Render MCP server

218 operations0 webhooks

Manage Render services and deploys, Postgres and Key Value databases, env groups, environments, custom domains, disks, logs, metrics, webhooks and workflows.

Try Render with your agent

Connect Render, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Render on my account, then run one read-only example and show me the result.

Runs once, when you ask

Render tools and triggers

Tools are what your agent can do in Render through Corsair's MCP server. Triggers are the Render events a routine can start from.

Services

  • Cancel DeployWrite

    Cancel a Render deployment

    services.cancelDeploy

  • CreateWrite

    Create a Render service

    services.create

  • Create PreviewWrite

    Create an image-backed preview for a Render service

    services.createPreview

  • Cron Jobs.Cancel RunDestructive

    Cancel a run of a Render cron job

    services.cronJobs.cancelRun

  • Cron Jobs.Trigger RunWrite

    Trigger a run of a Render cron job

    services.cronJobs.triggerRun

  • Custom Domains.CreateWrite

    Add a custom domain to a Render service

    services.customDomains.create

  • Custom Domains.DeleteDestructive

    Delete a custom domain from a Render service

    services.customDomains.delete

  • Custom Domains.ListRead-only

    List custom domains for a Render service

    services.customDomains.list

  • Custom Domains.RetrieveRead-only

    Retrieve a custom domain on a Render service

    services.customDomains.retrieve

  • Custom Domains.VerifyWrite

    Re-run DNS verification for a custom domain on a Render service

    services.customDomains.verify

  • DeleteDestructive

    Delete a Render service

    services.delete

  • Delete AutoscalingDestructive

    Delete autoscaling configuration for a Render service

    services.deleteAutoscaling

Connect Render to Claude, ChatGPT or Cursor

  1. 1

    Connect Render in Corsair

    Add your Render API key once in Corsair. Corsair stores the credential encrypted and makes the Render API calls for your agent, so it never goes into a prompt or a config file. Connect Render

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Render. On a ChatGPT personal plan, connect Render here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Render's read and write operations run right away and its 40 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/render, add the Render plugin, and connect with an API key. Then call methods like corsair.render.api.blueprints.disconnect() from your app. Corsair syncs data per tenant.

Yes. Render requires an API key from your Render account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Render, GitHub, Notion, Stripe, and the rest. Trigger Render from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage render services and deploys, postgres and key value databases, env groups, environments, custom domains, disks, logs, metrics, webhooks and workflows. Common builds include sync jobs, admin tooling, and agents that call Render APIs from your backend. Local DB entities let you query synced Render records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Render API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/render in the open repo. When Render ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Render data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Render data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Render on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 40 destructive Render operations. You can change a link's mode at hub.corsair.dev/me.