Integration · Automate and collaborate

Render and Meteor AI agents

Connect Render to a Met: check services, deploys, logs and metrics, and run read-only Postgres queries with Render's official MCP.

Book a demo See every integration

How does Render connect to Meteor?

With the Render ready connector, your Met uses Render's official MCP server with the API key the admin pastes in. It lists your services, brings the deploy history, reads logs with filters and checks CPU, memory and traffic metrics, so it can tell you on WhatsApp whether your site is down and what the logs say. It also runs read-only queries on your Render Postgres databases. Triggering a deploy, replacing a service's environment variables and creating new services or databases in your account start turned off until the admin turns them on in Connections.

What it automates

What a Meteor Met does with Render

Answer whether your site is down

When you ask on WhatsApp whether the site is down, the Met finds the service, checks its latest deploy and reads the recent error logs to tell you what it found.

See how a service is doing

The Met brings the service's metrics, such as CPU, memory, instances and HTTP requests, within the last 30 days, and sums up what they show.

Redeploy a service

The deploy action starts turned off. If the admin turns it on, the Met triggers a new deploy of the service, and can clear the build cache first. That deploy reaches production.

Query your Postgres database without writing to it

The Met runs a read-only query on your Render Postgres database, for example to count today's orders, and replies with the result.

Create a new service or database

The create actions start turned off. If the admin turns them on, the Met creates a web service, a static site, a cron job, a Postgres database or a Key Value in your account, with the plan given.

25 tools

Everything your Met can ask Render for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_workspaces`	Lists the Render workspaces the API key can access.
`select_workspace`	Selects the workspace to work in. Render marks it as deprecated.
`get_selected_workspace`	Returns the workspace currently selected.
`list_services`	Lists the services in your Render account, with or without preview services.
`get_service`	Returns the details of a service by its ID.
`create_web_service`	Creates a new web service in your Render account, with the repository, branch, plan and region given. Starts turned off.
`create_static_site`	Creates a new static site in your Render account from a repository. Starts turned off.
`create_cron_job`	Creates a new cron job in your Render account, with its schedule and command. Starts turned off.
`create_postgres`	Creates a new Postgres database with the pricing plan given, the free one among them. Starts turned off.
`create_key_value`	Creates a new Key Value instance with the pricing plan given. Starts turned off.
`update_environment_variables`	Replaces all of a service's environment variables with the complete list it receives. Starts turned off.
`update_web_service`	Does not change the web service. Returns the link to its settings in the Render Dashboard.
`update_static_site`	Does not change the static site. Returns the link to its settings in the Render Dashboard.
`update_cron_job`	Does not change the cron job. Returns the link to its settings in the Render Dashboard.
`list_deploys`	Lists a service's deploy history.
`get_deploy`	Returns the details of one deploy of a service.
`trigger_deploy`	Triggers a new deploy of a service, with the option to clear the build cache first. Starts turned off.
`list_logs`	Lists the logs that match the filters, such as level, type, path, status code, text or time range.
`list_log_label_values`	Lists every value of a label in the logs that match the filters.
`get_metrics`	Returns metrics for a service, a database or a Key Value, such as CPU, memory, instances, HTTP requests or active connections.
`list_postgres_instances`	Lists the Postgres databases in your Render account.
`get_postgres`	Returns the details of a Postgres database.
`query_render_postgres`	Runs a read-only SQL query against a Postgres database hosted on Render.
`list_key_value`	Lists the Key Value instances in your Render account.
`get_key_value`	Returns the details of a Key Value instance.

The limits

What the Render integration does NOT do

We would rather say it here than have you find out during rollout.

It does not delete services or databases, or change a service's settings, scaling or other controls. The update tools return the Dashboard link; it only changes environment variables and triggers deploys.
It does not ask you for confirmation in the chat before creating a service, triggering a deploy or replacing environment variables. Those actions start turned off; if the admin turns them on in Connections, the Met runs them.
It does not create every kind of service. Only web services, static sites, cron jobs, Postgres and Key Value; it does not deploy prebuilt images from a container registry or set up IP allowlists.
It does not query a Postgres database with a restricted IP allowlist. Render's hosted server does not have IP addresses you can add to that list yet.
It does not guarantee secrets stay out of the conversation. Render tries not to expose sensitive data such as connection strings, but says it does not guarantee it.
It does not bring metrics older than 30 days, and a web service's response times need a Pro workspace or higher on Render.

Before you start

What you need to connect Render

1

A Render API key

In the Render dashboard, open Account Settings → API Keys and create a key. That key gives the Met access to your workspaces and services.
2

Connect it in Met

In Met, open Connections → Render → Connect and paste the API key. Then the admin chooses which actions stay on.
3

The right workspace

Every action works on one Render workspace. The Met lists yours and uses the one you set in its instructions or in the conversation.

Frequently asked questions

Questions about Render and Meteor

Only if the admin turns on the create actions in Connections, which start turned off. What it creates runs in your Render account with the plan chosen. If you do not want the Met to create resources, leave them off.

Not with this connector. The Postgres query is read-only according to Render. What it can change is a service's environment variables, and it replaces all of them at once.

No. Render's MCP server has no deletion tools: deletions and other changes are made in the Dashboard or with the Render API.

You do, with your Render account and plan. Meteor does not resell Render: the connector uses your company's API key, and whatever it creates or deploys runs in that account.

Step by step