> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Render

> Give the Sazabi agent tools to inspect and manage Render services, deploys, environment variables, logs, and metrics.

[All Render integration capabilities](https://docs.sazabi.com/catalogs/integrations/render)

## About

This is an MCP connector that gives the Sazabi agent tools from Render's hosted MCP server at `https://mcp.render.com/mcp`. Sazabi stores your Render API key securely and sends it as the `Authorization: Bearer` token to Render's MCP endpoint. Once connected, the agent can browse services, read logs and metrics to investigate incidents, and update environment variables.

**What the agent can do:**

* Browse workspaces, services, and environment configuration
* List and get deploys (read-only)
* Read service logs and metrics to investigate incidents
* Create supported Render resources
* Update service environment variables

## Prerequisites

* A Render account
* A Render API key from **Account Settings > API Keys** in the [Render dashboard](https://dashboard.render.com/settings/api-keys)

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Render in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Add your key

Create a Render API key in **Account Settings > API Keys** in the [Render dashboard](https://dashboard.render.com/settings/api-keys). Sazabi stores it securely and sends it as the `Authorization: Bearer` token to Render's MCP endpoint (`https://mcp.render.com/mcp`). Note: a Render API key is account-wide and can manage and deploy every service in the account, so treat it as a high-privilege credential.

## Set up with the CLI

Render authenticates with a Render API key. With the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) installed and authenticated (see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)), connect it in one command, passing the credential as a header:

```bash theme={"system"}
sazabi mcp-connectors connect render --header "Authorization=Bearer <api-key>"
```

The CLI connects to the MCP server at once and prints the connection with the tools it discovered; a credential the server rejects is reported, and the connection is left needing attention. Use `NAME=@<file>` to read a value from a file, or `--header-file <file.json>` for a JSON object of header names and values. To rotate the stored credentials later, use `sazabi mcp-connectors update-credentials <connection-id>`; find the connection ID with `sazabi mcp-connectors list`.

## Verify

Open the connector's connection page under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the key is correct.

## Troubleshooting

**No tools discovered** — Confirm the API key is valid and has not been revoked. Re-enter it from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Connection shows needs attention** — The authorization or key may have expired or been revoked; reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.