create_service
Create a new service
LABSCO 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
USE CASES
01
Shipping a fix without leaving the editor
Find the service among the ones in the account, start the deploy, then read the deploy history to see the new entry land.
02
Rotating a key your services share
Walk the services in the account, change the variable on each one that carries it, and redeploy so the running process picks up the new value.
03
Pointing a domain at a service you just created
Create the service, attach the custom domain to it, then read the service back to see the state it settled into.
04
Clearing out preview services that outlived their branch
List what is still running, use each service's deploy history to find the ones nobody has pushed to in a while, and delete those.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
delete_service
Delete a service
deploy_service
Deploy a service
get_deploys
Get deployment history for a service
get_service
Get details of a specific service
list_services
List all services in your Render account
manage_domains
Manage custom domains for a service
manage_env_vars
Manage environment variables for a service
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected; the project documents 14. The documentation also names create_web_service, create_static_site, create_cron_job, list_logs, get_metrics and query_render_postgres; query_render_postgres needs the pg driver added with npm install.
Requires
- npx on PATH
- RENDER_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @niyogi/render-mcpMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"render": {
"command": "npx",
"args": [
"-y",
"@niyogi/render-mcp",
"start"
],
"env": {
"RENDER_API_KEY": "<YOUR_RENDER_API_KEY>"
}
}
}
}Cline
CLINE · JSON
{
"mcpServers": {
"render": {
"command": "node",
"args": [
"<YOUR_PATH_TO_RENDER_MCP>/bin/render-mcp.js",
"start"
],
"env": {
"RENDER_API_KEY": "<YOUR_RENDER_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}<YOUR_PATH_TO_RENDER_MCP> is the package folder the global install created: after npm install -g @niyogi/render-mcp, run npm root -g and use <that folder>/@niyogi/render-mcp/bin/render-mcp.js. <YOUR_RENDER_API_KEY> is your Render API key (dashboard.render.com/account/api-keys).
