OpenBot
DownloadApp
All plugins

Render

Services, deploys and logs

Render lets agents list workspaces and services, read logs, events and metrics, see the deploy history, trigger deploys, and run read-only SQL on Render Postgres. A Render API key goes into one Authorization header. The key reaches every workspace of the Render account. Agents can create web services, static sites, cron jobs, Postgres databases and Key Value instances, which can cost money, and they can replace the environment variables of a service. The server cannot delete a resource.

What an agent can do with Render

  • See workspaces and services

    The list_workspaces and select_workspace tools choose the workspace that the agent uses. The list_services and get_service tools list the services in it and show their details. The agent can tell you what runs where before you change it.

  • Find why a deploy or a service failed

    The list_deploys and get_deploy tools read the deploy history of a service. The list_events tool shows builds, restarts and failures, with the reason a service went down, such as an out-of-memory kill or a failed health check. The list_logs tool reads the logs that match a filter.

  • Check metrics and data

    The get_metrics tool reads CPU and memory use, instance count, response counts and bandwidth. The query_render_postgres tool runs a read-only SQL query on a Render Postgres database.

  • Create services and trigger deploys

    The agent can create web services, static sites, cron jobs, Postgres databases and Key Value instances. The trigger_deploy tool starts a deploy, and the update_environment_variables tool replaces the environment variables of a service.

How to connect Render to OpenBot

  1. Open Render in OpenBot

    Press Open in OpenBot on this page, or find Render in the app's Apps tab. Get the app first if it is not on this computer.

  2. Add your API key

    Press Connect and enter this value. OpenBot keeps it on the computer that runs OpenBot.

    • API key - Render Account settings → API keys

    Create a key

  3. Give an agent a task

    Ask an agent for work that needs Render, such as one of the example prompts below. The agent uses the plugin's tools to do it.

Example prompts3

  • RenderWhich services are in my Render workspace?
  • RenderWhich errors did my Render web service log in the last hour?
  • RenderWhy did the last deploy of my Render service fail?

Apps1

  • Render

    Services, deploys, logs, and metrics, over Render's MCP server with an API key.

Information6

Developer
Render
Category
Coding
Version
1.0.0
Website
render.com
Privacy policy
render.com/privacy
Terms
render.com/terms

Questions

Is the Render MCP server official?

Yes. Render hosts the MCP server at mcp.render.com and documents it on render.com. Its source is in Render's render-oss GitHub organization. This plugin uses the hosted server.

Which key does the Render plugin need?

A Render API key, which you create in your Render Account settings. Type the key in the connect dialog in OpenBot. OpenBot sends it as a bearer token in the Authorization header. The key gives access to every workspace of your Render account. The plugin catalog holds no secret.

What can the agent change in Render?

The agent can create services, databases and Key Value instances, trigger deploys, and replace the environment variables of a service. The server cannot delete a resource, and it cannot change scaling or most service settings. Render warns that a change to environment variables can be destructive, so check what the agent changes.

What data does Render get?

Render gets the requests that the agent sends, and the results go back to the agent. Render does not promise that secrets, such as database connection strings, stay out of the agent's context. Your workspaces, conversations and files stay on the computer that runs OpenBot.

Sources

Every statement about Render comes from the pages below, checked on . They can change after that date.