Labsco
MCP SERVER

Render

by niyogi

Create a Render service, deploy it, read its deploy history, and change the environment variables and custom domains it runs with — from the client instead of the dashboard.

PaaS Deployment & App HostingVerified
Summary
Enough of Render to run a service end to end, minus the part that tells you why a deploy failed.

The set covers the lifecycle — create, deploy, read the history, delete — plus the settings that change between deploys, environment variables and custom domains. What it does not carry is the aftermath: no tool here returns build output or runtime logs, so a failed deploy shows up in get_deploys as an entry and the reason is still in the dashboard. Every tool takes one opaque params object rather than named arguments, so what you can set on a service is whatever that object accepts.

What it is

A control layer over the services in a Render account: eight tools that list, create, deploy and delete a service and reach the settings around it.

What you get
  • Every service in the account listed, and any one of them opened to its details
  • Services created and deleted
  • A deploy started on a service, with that service's deploy history to read afterwards
  • Environment variables changed per service
  • Custom domains attached to a service
Requirements

A Render account and an API key for it in RENDER_API_KEY.

Setup effort

One command plus a key — npm install -g @niyogi/render-mcp, then supply credentials