> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to the Render MCP server

The Render MCP connector routes your AI agent's tool calls to Render's own MCP server through Scalekit. Each user connects their own Render access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 48 tools.

**Authentication:** Bearer Token
**Categories:** Developer Tools, Productivity
**Tools:** 48: 32 read, 10 write, 6 destructive
**Users sign in with:** Access token
**Built by:** Vendor MCP
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=RENDERMCP)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Render MCP connection

   In **AgentKit > Connections**, create a Render MCP connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

   **Console steps with screenshots:**

   Register your Render API key with Scalekit so it can authenticate requests to the Render MCP server on behalf of your users. Render MCP uses API key authentication: the key is sent as a Bearer token.

   1. ### Create a Render API key

      - Log in to your [Render dashboard](https://dashboard.render.com).
      - Click your workspace name, then **Account Settings**.
      - Select **API Keys** from the settings sidebar.

        > Image: Render Account settings showing the API Keys panel with existing keys and a Create API Key button

      - Click **Create API Key**, give it a descriptive name (for example, `Scalekit`), and copy the key.

      > caution: Copy the key now
      >
      > Render shows the full key only once. A Render API key has access to every workspace your account can reach, so store it in a secrets manager.

   2. ### Create a connection in Scalekit

      - In the [Scalekit dashboard](https://app.scalekit.com), go to **AgentKit** → **Connections** → **Create Connection**.
      - Search for **Render MCP** and click **Create**.
      - Note the **Connection name** — use this as `connection_name` in your code (for example, `rendermcp`).

   3. ### Add a connected account

      Connected accounts link a specific user identifier in your system to a Render API key. Add one in the dashboard to test. In production, each user adds their own through the authorization link: they enter their credentials on the page it opens.

      **In the dashboard, to test**

      - Open the connection and click the **Connected Accounts** tab → **Add account**.
      - Fill in **Your User's ID** and **API Key**, then click **Save**.

      **From your backend, if your app already has the credentials**

      For example, when users enter them on a settings page in your app:

        **Node.js**

        ```typescript
        import { ConnectorStatus } from '@scalekit-sdk/node'

        const authorizationDetails = {
          details: {
            case: 'staticAuth',
            value: { details: { token: process.env.USER_API_KEY } },
          },
        };

        let { connectedAccount } = await scalekit.actions.upsertConnectedAccount({
          connectionName: 'rendermcp',
          identifier: 'user_123',
          authorizationDetails,
        });

        // Make sure the account is ACTIVE before the first tool call.
        if (connectedAccount?.status !== ConnectorStatus.ACTIVE) {
          ({ connectedAccount } = await scalekit.actions.upsertConnectedAccount({
            connectionName: 'rendermcp',
            identifier: 'user_123',
            authorizationDetails,
          }));
        }
        ```

        **Python**

        ```python
        authorization_details = {"static_auth": {"token": user_api_key}}

        response = scalekit_client.actions.upsert_connected_account(
            connection_name="rendermcp",
            identifier="user_123",
            authorization_details=authorization_details,
        )

        # Make sure the account is ACTIVE before the first tool call.
        if response.connected_account.status != "ACTIVE":
            response = scalekit_client.actions.upsert_connected_account(
                connection_name="rendermcp",
                identifier="user_123",
                authorization_details=authorization_details,
            )
        ```

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'rendermcp'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Render MCP:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'rendermcp_get_selected_workspace',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "rendermcp"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Render MCP:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="rendermcp_get_selected_workspace",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Render MCP server credentials there. If your app already has a user's credentials, add the account from your backend instead, as the console steps above show. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'rendermcp_get_blueprint',
  toolInput: {
    blueprintId: '<blueprintId>',
  },
  connector: 'rendermcp',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="rendermcp_get_blueprint",
    tool_input={
        "blueprintId": "<blueprintId>",
    },
    connection_name="rendermcp",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `rendermcp_get_blueprint`

Get Blueprint details · Read-only

This tool is in public alpha (early access). Access to this tool and its contract are subject to change. Retrieve a Blueprint's settings and status, along with the IDs of the resources it manages. The tool returns the Blueprint detail object from the REST API. When autoSync is true, the Blueprint is configured to sync automatically on Git pushes to its configured branch. Automatic syncing requires approval of the Blueprint's first sync. When autoSync is false, syncing requires manual planning and approval. The Blueprint's status remains "created" until its first sync has been approved. After that approval, the status is "paused" whenever autoSync is false, regardless of the state of any manual sync. You can still use plan_blueprint and approve_blueprint while automatic syncing is paused. When autoSync is true and the first sync has been approved, the status reflects the latest sync. A status of "syncing" means that the sync is queued or running, and "error" means that it failed. The status can be "in_sync" when the latest sync has succeeded or when a plan is awaiting approval. Do not use the status alone to determine whether services are healthy or whether the infrastructure matches the current Blueprint file. To check for infrastructure changes, use plan_blueprint and follow its guidance for reviewing the plan with the user before approval. This tool does not create a plan or apply infrastructure changes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `blueprintId` (`string`, required): This ID identifies the Blueprint to retrieve. Blueprint IDs start with exs-.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"blueprintId":"<blueprintId>"}`

### `rendermcp_get_deploy`

Get deploy details · Read-only

Retrieve the details of a particular deploy for a particular service.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `deployId` (`string`, required): The ID of the deployment to retrieve
- `serviceId` (`string`, required): The ID of the service to get deployments for
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"deployId":"<deployId>","serviceId":"<serviceId>"}`

### `rendermcp_get_flow`

Get flow · Read-only

Get a registered flow's name, workflow ID and version ID in the selected workspace.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `flowId` (`string`, required): Flow ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"flowId":"<flowId>"}`

### `rendermcp_get_flow_run`

Get flow run · Read-only

Inspect a flow run's status, error, error details and attempts (zero-indexed). A flow run gets a new attempt when it resumes after its process is interrupted; it replays completed steps rather than rerunning them. Errors are capped at 4 KiB each with errorTruncated flags. Inputs and results are omitted: use get_flow_run_results for results, list_flow_run_steps for steps, and list_logs with the workflow ID as resource and this ID as taskRun for logs. Poll this tool to wait for a run started with start_flow_run. Flow failure is data, not a tool failure.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `flowRunId` (`string`, required): Flow run ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"flowRunId":"<flowRunId>"}`

### `rendermcp_get_flow_run_results`

Get flow run results · Read-only

Read a terminal flow run's results as paged JSON text, preserving arrays and integers exactly. Nonterminal runs return ready=false, not a final result. Concatenate content pages, passing nextOffset and sha256 on each follow-up; nextOffset=null marks the end. Do not infer success from ready=true: inspect status. Failed and canceled runs may have null or empty results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `flowRunId` (`string`, required): Flow run ID
- `limit` (`number`, optional): Maximum result bytes in this page. Default: `32768`.
- `offset` (`number`, optional): UTF-8 byte offset, use nextOffset from the preceding page. Default: `0`.
- `sha256` (`string`, optional): Result hash from the first page; required for offsets greater than zero
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"flowRunId":"<flowRunId>"}`

### `rendermcp_get_flow_run_step`

Get flow run step · Read-only

Get one flow run step's status, result, and error. The step's input is omitted. Errors are capped at 4 KiB each with errorTruncated flags. result is present only when the step succeeded; null means the step returned no value.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `flowRunId` (`string`, required): Flow run ID
- `seq` (`number`, required): The step's seq from list_flow_run_steps
- `stepKey` (`string`, optional): The stepKey from list_flow_run_steps, used to distinguish steps with the same seq. Omit for a step recorded without a key
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"flowRunId":"<flowRunId>","seq":1}`

### `rendermcp_get_key_value`

Get Key Value instance details · Read-only

Retrieve a Key Value instance by ID

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `keyValueId` (`string`, required): The ID of the Key Value instance to retrieve
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"keyValueId":"<keyValueId>"}`

### `rendermcp_get_metrics`

Get resource metrics · Read-only

Get performance metrics for any Render resource (services, Postgres databases, key-value stores). Supports CPU usage/limits/targets, memory usage/limits/targets, service instance counts, HTTP request counts and response time metrics, bandwidth usage metrics, database active connection counts for debugging, capacity planning, and performance optimization. Returns time-series data with timestamps and values for the specified time range. HTTP metrics support filtering by host and path for more granular analysis. Limits and targets help understand resource constraints and autoscaling thresholds. Metrics may be empty if the metric is not valid for the given resource.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `metricTypes` (`array`, required): Which metrics to fetch. CPU usage/limits/targets, memory usage/limits/targets, and instance count metrics are available for all resources. HTTP request counts and response time metrics, and bandwidth usage metrics are only available for services. Active connection metrics are only available for databases and key-value stores. Limits show resource constraints, targets show autoscaling thresholds.
- `resourceId` (`string`, required): The ID of the resource to get metrics for (service ID, Postgres ID, or key-value store ID)
- `aggregateHttpRequestCountsBy` (`string`, optional): Field to aggregate HTTP request metrics by. Only supported for http_request_count metric. Options: host (aggregate by request host), statusCode (aggregate by HTTP status code). When not specified, returns total request counts. One of: `host`, `statusCode`.
- `cpuUsageAggregationMethod` (`string`, optional): Method for aggregating metric values over time intervals. Only supported for CPU usage metrics. Options: AVG, MAX, MIN. Defaults to AVG. One of: `AVG`, `MAX`, `MIN`. Default: `AVG`.
- `endTime` (`string`, optional): End time for metrics query in RFC3339 format (e.g., '2024-01-01T13:00:00Z'). Defaults to the current time. The end time must be within the last 30 days.
- `httpHost` (`string`, optional): Filter HTTP metrics to specific request hosts. Supported for http_request_count and http_latency metrics. Example: 'api.example.com' or 'myapp.render.com'. When not specified, includes all hosts.
- `httpLatencyQuantile` (`number`, optional): The quantile/percentile of HTTP latency to fetch. Only supported for http_latency metric. Common values: 0.5 (median), 0.95 (95th percentile), 0.99 (99th percentile). Defaults to 0.95 if not specified. Default: `0.95`.
- `httpPath` (`string`, optional): Filter HTTP metrics to specific request paths. Supported for http_request_count and http_latency metrics. Example: '/api/users' or '/health'. When not specified, includes all paths.
- `resolution` (`number`, optional): Time resolution for data points in seconds. Lower values provide more granular data. Higher values provide more aggregated data points. API defaults to 60 seconds if not provided. There is a limit to the number of data points that can be returned, after which the metrics endpoint will return a 500. If you are getting a 500, try reducing granularity (increasing the value of resolution).
- `startTime` (`string`, optional): Start time for metrics query in RFC3339 format (e.g., '2024-01-01T12:00:00Z'). Defaults to 1 hour ago. The start time must be within the last 30 days.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"metricTypes":[],"resourceId":"<resourceId>"}`

### `rendermcp_get_postgres`

Get Postgres instance details · Read-only

Retrieve a Postgres instance by ID

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `postgresId` (`string`, required): The ID of the Postgres instance to retrieve
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"postgresId":"<postgresId>"}`

### `rendermcp_get_selected_workspace`

Get selected workspace · Read-only

Get the workspace stored in the session compatibility fallback. Request-scoped workspaces supplied with an explicit workspaceId are not reflected by this tool.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `rendermcp_get_service`

Get service details · Read-only

Get details about a specific service

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `serviceId` (`string`, required): The ID of the service to retrieve
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"serviceId":"<serviceId>"}`

### `rendermcp_get_workflow`

Get workflow · Read-only

Get a Workflow's configuration and verify it belongs to the selected workspace.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workflowId` (`string`, required): Workflow ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"workflowId":"<workflowId>"}`

### `rendermcp_get_workflow_run`

Get workflow run · Read-only

Inspect a task run's status, errors and all attempts (zero-indexed), plus parent/root relationships. Errors are capped at 4 KiB each with errorTruncated flags. Inputs/results are omitted. Use get_workflow_run_results for results. Report attempts as returned; retries and timestamps alone do not prove how many attempts ran or how long they queued. Task failure is data, not a tool failure.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `taskRunId` (`string`, required): Task run ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"taskRunId":"<taskRunId>"}`

### `rendermcp_get_workflow_run_results`

Get workflow run results · Read-only

Read a terminal run's or attempt's results as paged JSON text, preserving arrays and integers exactly. Nonterminal states return ready=false, not a final result. Concatenate content pages, passing nextOffset and sha256 on each follow-up; nextOffset=null marks the end. Do not unwrap the API's results array or infer success from ready=true: inspect status. Failed/canceled runs may have null/empty results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `taskRunId` (`string`, required): Task run ID
- `attempt` (`number`, optional): Optional zero-indexed attempt number; omit for the run's results
- `limit` (`number`, optional): Maximum result bytes in this page
- `offset` (`number`, optional): UTF-8 byte offset, use nextOffset from the preceding page
- `sha256` (`string`, optional): Result hash from the first page; required for offsets greater than zero
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"taskRunId":"<taskRunId>"}`

### `rendermcp_get_workflow_task`

Get workflow task · Read-only

Get a registered task's name, workflow ID and version ID in the selected workspace.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `taskId` (`string`, required): Task ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"taskId":"<taskId>"}`

### `rendermcp_get_workflow_version`

Get workflow version · Read-only

Get a Workflow version's build/registration status in the selected workspace.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workflowVersionId` (`string`, required): Workflow version ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"workflowVersionId":"<workflowVersionId>"}`

### `rendermcp_list_deploys`

List deploys · Read-only

List deploys matching the provided filters. If no filters are provided, all deploys for the service are returned.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `serviceId` (`string`, required): The ID of the service to get deployments for
- `cursor` (`string`, optional): A unique string that corresponds to a position in the result list. If provided, the endpoint returns results that appear after the corresponding position. To fetch the first page of results, set to the empty string.
- `limit` (`number`, optional): The maximum number of deploys to return in a single page. To fetch additional pages of results, set the cursor to the last deploy in the previous page. It should be rare to need to set this value greater than 20.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"serviceId":"<serviceId>"}`

### `rendermcp_list_events`

List service events · Read-only

List a service's event history: deploys, builds, restarts, failures, scaling, suspensions, and disk changes. Use it to find out what happened to a service and why. Failure events carry the reason a service went down, such as out-of-memory kills, non-zero exits, failed health checks, and evictions, which may not show up in logs. The first page covers the last 7 days unless startTime says otherwise. For older events, page with the cursor from the previous call. If the first page comes back empty there is no cursor to follow, so set an earlier startTime instead. Events cover services only, not Postgres or Key Value instances.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `serviceId` (`string`, required): The ID of the service to list events for
- `cursor` (`string`, optional): A unique string that corresponds to a position in the result list. If provided, the endpoint returns results that appear after the corresponding position. To fetch the first page of results, set to the empty string.
- `endTime` (`string`, optional): End of the time range in RFC3339 format (e.g. '2024-01-01T13:00:00Z'). Defaults to the current time.
- `eventTypes` (`array`, optional): Filter to specific event types. Returns all types when omitted. For debugging a failure, server_failed, deploy_ended, build_ended, and image_pull_failed carry the most detail.
- `limit` (`number`, optional): The maximum number of events to return, newest first.
- `startTime` (`string`, optional): Start of the time range in RFC3339 format (e.g. '2024-01-01T12:00:00Z'). Defaults to 7 days ago on the first page. Set it to reach events older than that.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"serviceId":"<serviceId>"}`

### `rendermcp_list_flow_run_steps`

List flow run steps · Read-only

List a flow run's steps in the order the flow started them, with type, status, and timestamps. Use get_flow_run_step for a step's result and error.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `flowRunId` (`string`, required): Flow run ID
- `cursor` (`string`, optional): Cursor returned by the preceding page; omit for the first page
- `limit` (`number`, optional): Maximum records on this page, 1 to 100
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"flowRunId":"<flowRunId>"}`

### `rendermcp_list_flow_runs`

List flow runs · Read-only

List flow runs with status and timestamps. A page is not the entire history. Use get_flow_run for errors and attempts, get_flow_run_results for results, and list_flow_run_steps for steps.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Cursor returned by the preceding page; omit for the first page
- `flowId` (`string`, optional): Filter by flow ID
- `flowSlug` (`string`, optional): Filter by workflow-slug/flow-name, optionally :version
- `limit` (`number`, optional): Maximum records on this page, 1 to 100
- `status` (`string`, optional): Filter by flow run status. One of: `pending`, `running`, `succeeded`, `failed`, `canceled`.
- `workflowId` (`string`, optional): Filter by workflow ID
- `workflowVersionId` (`string`, optional): Filter by workflow version ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_flows`

List flows · Read-only

Discover registered flows, their IDs and slugs in the selected workspace. Flows whose workflow cannot be retrieved are omitted. Each workflow version registers its own flows, so the same name can appear once per version. Filter by workflowVersionId to choose a version, then pass the flow's id (flw-...) to start_flow_run. Use nextCursor for another page, even if this page is empty.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Cursor returned by the preceding page; omit for the first page
- `flowSlug` (`string`, optional): Filter by workflow-slug/flow-name, optionally :version
- `limit` (`number`, optional): Maximum records on this page, 1 to 100. Default: `20`.
- `workflowVersionId` (`string`, optional): Filter by workflow version ID, for example a version from create_workflow_version
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_key_value`

List Key Value instances · Read-only

List all Key Value instances in your Render account

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_log_label_values`

List log label values · Read-only

List all values for a given log label in the logs matching the provided filters. This can be used to discover what values are available for filtering logs using the list_logs tool. You can query for logs across multiple resources, but all resources must be in the same region and belong to the same owner.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `label` (`string`, required): The label to list values for. One of: `host`, `instance`, `level`, `method`, `statusCode`, `type`.
- `resource` (`array`, required): Filter by resource. A resource is the id of a server, cronjob, job, postgres, or redis.
- `direction` (`string`, optional): The direction to query logs for. Backward will return most recent logs first. Forward will start with the oldest logs in the time range. One of: `backward`, `forward`. Default: `backward`.
- `endTime` (`string`, optional): End time for log query (RFC3339 format). Defaults to the current time. The end time must be within the last 30 days.
- `host` (`array`, optional): Filter request logs by their host. Wildcards and regex are supported.
- `instance` (`array`, optional): Filter logs by the instance they were emitted from.
- `level` (`array`, optional): Filter logs by their severity level. Wildcards and regex are supported.
- `method` (`array`, optional): Filter request logs by their requests method. Wildcards and regex are supported.
- `path` (`array`, optional): Filter request logs by their path. Wildcards and regex are supported.
- `startTime` (`string`, optional): Start time for log query (RFC3339 format). Defaults to 1 hour ago. The start time must be within the last 30 days.
- `statusCode` (`array`, optional): Filter request logs by their status code. Wildcards and regex are supported.
- `text` (`array`, optional): Filter by the text of the logs. Wildcards and regex are supported.
- `type` (`array`, optional): Filter logs by their type.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"label":"host","resource":[]}`

### `rendermcp_list_logs`

List logs · Read-only

List logs matching the provided filters. Logs are paginated by start and end timestamps. There are more logs to fetch if hasMore is true in the response. Provide the nextStartTime and nextEndTime timestamps as the startTime and endTime query parameters to fetch the next page of logs. You can query for logs across multiple resources, but all resources must be in the same region and belong to the same owner.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `resource` (`array`, required): Filter logs by their resource. A resource is the id of a server, cronjob, job, postgres, redis, or workflow.
- `direction` (`string`, optional): The direction to query logs for. Backward will return most recent logs first. Forward will start with the oldest logs in the time range. One of: `backward`, `forward`. Default: `backward`.
- `endTime` (`string`, optional): End time for log query (RFC3339 format). Defaults to the current time. The end time must be within the last 30 days.
- `host` (`array`, optional): Filter request logs by their host. Wildcards and regex are supported.
- `instance` (`array`, optional): Filter logs by the instance they were emitted from. An instance is the id of a specific running server.
- `level` (`array`, optional): Filter logs by their severity level. Wildcards and regex are supported.
- `limit` (`number`, optional): Maximum number of logs to return
- `method` (`array`, optional): Filter request logs by their requests method. Wildcards and regex are supported.
- `path` (`array`, optional): Filter request logs by their path. Wildcards and regex are supported.
- `startTime` (`string`, optional): Start time for log query (RFC3339 format). Defaults to 1 hour ago. The start time must be within the last 30 days.
- `statusCode` (`array`, optional): Filter request logs by their status code. Wildcards and regex are supported.
- `task` (`array`, optional): Filter workflow logs by task or flow ID. Requires the workflow ID in resource.
- `taskRun` (`array`, optional): Filter workflow logs by task run or flow run ID, for example the id start_flow_run returns. Requires the workflow ID in resource. Set startTime to before the run started: the default window is the last hour.
- `text` (`array`, optional): Filter by the text of the logs. Wildcards and regex are supported.
- `type` (`array`, optional): Filter logs by their type. Types include app for application logs, request for request logs, and build for build logs. You can find the full set of types available for a query by using the list_log_label_values tool.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"resource":[]}`

### `rendermcp_list_postgres_instances`

List Postgres instances · Read-only

List all Postgres databases in your Render account

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_services`

List services · Read-only

List all services in your Render account

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `includePreviews` (`boolean`, optional): Whether to include preview services in the response. Defaults to false. Default: `false`.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_workflow_runs`

List workflow runs · Read-only

List task runs with status, attempts and parent/root relationships. A page is not the entire history. The API does not support status/time filters here. Use get_workflow_run for errors and get_workflow_run_results for results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Cursor returned by the preceding page; omit for the first page
- `limit` (`number`, optional): Maximum records on this page, 1 to 100. Default: `20`.
- `rootTaskRunId` (`string`, optional): Filter to the run tree with this root run ID
- `taskSlug` (`string`, optional): Filter by workflow-slug/task-name, optionally :version
- `workflowId` (`string`, optional): Filter by workflow ID
- `workflowVersionId` (`string`, optional): Filter by workflow version ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_workflow_tasks`

List workflow tasks · Read-only

Discover registered tasks, their IDs and versions in the selected workspace. Use nextCursor for another page.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Cursor returned by the preceding page; omit for the first page
- `limit` (`number`, optional): Maximum records on this page, 1 to 100. Default: `20`.
- `taskSlug` (`string`, optional): Filter by workflow-slug/task-name, optionally :version
- `workflowId` (`string`, optional): Filter by workflow ID
- `workflowVersionId` (`string`, optional): Filter by workflow version ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_workflow_versions`

List workflow versions · Read-only

List Workflow versions and their build/registration status. Use nextCursor for another page.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Cursor returned by the preceding page; omit for the first page
- `limit` (`number`, optional): Maximum records on this page, 1 to 100. Default: `20`.
- `workflowId` (`string`, optional): Filter by workflow ID
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_workflows`

List workflows · Read-only

Discover Workflows in the selected workspace. Returns one page and nextCursor; follow until null or an empty page.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Cursor returned by the preceding page; omit for the first page
- `environmentId` (`string`, optional): Filter by environment ID
- `limit` (`number`, optional): Maximum records on this page, 1 to 100. Default: `20`.
- `name` (`string`, optional): Filter by workflow name
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{}`

### `rendermcp_list_workspaces`

List workspaces · Read-only

List the workspaces that you have access to

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `rendermcp_query_render_postgres`

Query Postgres · Read-only

Run a read-only SQL query against a Render-hosted Postgres database. This tool creates a new connection for each query and closes it after the query completes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `postgresId` (`string`, required): The ID of the Postgres instance to query
- `sql` (`string`, required): The SQL query to run. Note that the query will be wrapped in a read-only transaction.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"postgresId":"<postgresId>","sql":"<sql>"}`

### `rendermcp_create_blueprint`

Create Blueprint · Write

This tool is in public alpha (early access). Access to this tool and its contract are subject to change. Create a Render Blueprint from a Blueprint YAML file in a public repository or a repository accessible through a connected Git provider, and plan its first sync. By default, the plan creates separate resources and leaves existing resources unchanged. Resource changes are applied only after approval with approve_blueprint. After the first approval, later pushes deploy automatically when autoSync is enabled. All Blueprint changes are read from the remote repository. When working in a local checkout, push your changes first and pass its origin URL as repoUrl and current branch as branch. The tool returns blueprint, planningOutcome, sync, and notices. Use planningOutcome to determine whether planning succeeded and what to do next. Read planningOutcome to determine the next step. If planningOutcome is "failed", inspect the errors in notices. Address the reported issues and push any Blueprint file changes, then call plan_blueprint with the Blueprint ID again. Do not approve a failed plan, even if sync is present. If planningOutcome is "no_changes", this planning attempt found no infrastructure changes. Do not call approve_blueprint for this result. If planningOutcome is "planned", sync contains the proposed infrastructure changes. Summarize them for the user or share sync.dashboardUrl for review. To apply the changes, call approve_blueprint with the Blueprint ID and follow its guidance for supplying any required environment variable values. Call approve_blueprint only after the user authorizes applying the reviewed plan. Providing or allowing generation of manual environment values, or accepting costs, does not by itself authorize deployment.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `repoUrl` (`string`, required): Repository URL starting with https:// or ssh://, without a query string or fragment. SSH URLs are converted to HTTPS. SCP-style remotes (git@host:path) are not accepted. Specify the branch separately with branch.
- `autoSync` (`boolean`, optional): Automatically apply later pushes to the branch after the first sync is approved. Defaults to true. Default: `true`.
- `branch` (`string`, optional): Branch containing the Blueprint file. Defaults to the repository's default branch.
- `existingResources` (`string`, optional): How Sync planning should handle existing resources. Defaults to create_new. create_new creates a separate set of resources using a Blueprint-specific random suffix, leaving existing resources unchanged. adopt brings matching existing resources under this Blueprint's management and updates their configuration to match the Blueprint file. One of: `adopt`, `create_new`. Default: `create_new`.
- `name` (`string`, optional): Blueprint name. Defaults to the repository name without the .git suffix.
- `path` (`string`, optional): Blueprint file path relative to the repository root. Defaults to render.yaml. Default: `render.yaml`.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"repoUrl":"<repoUrl>"}`

### `rendermcp_create_cron_job`

Create cron job · Write

Create a new cron job in your Render account. A cron job is a scheduled task that runs on a recurring schedule specified using cron syntax. Cron jobs are ideal for background tasks like data processing, cleanup operations, sending emails, or generating reports. By default, these services are automatically deployed when the specified branch is updated. This tool is currently limited to support only a subset of the cron job configuration parameters. Deploying prebuilt images from a container registry is not supported. To create a cron job without those limitations, please use the dashboard at: https://dashboard.render.com/create

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): A unique name for your cron job.
- `runtime` (`string`, required): The runtime environment for your cron job. This determines how your job is built and run. One of: `node`, `python`, `go`, `rust`, `ruby`, `elixir`, `docker`.
- `schedule` (`string`, required): The cron schedule expression that determines when the job runs. Uses standard cron syntax with 5 fields: minute (0-59), hour (0-23), day of month (1-31), month (1-12), day of week (0-6, Sunday=0). Examples: '0 0 * * *' (daily at midnight), '*/15 * * * *' (every 15 minutes), '0 9 * * 1-5' (weekdays at 9am), '0 0 1 * *' (first day of each month at midnight). For natural language requests like 'every hour' or 'daily at 3pm', convert to cron syntax.
- `autoDeploy` (`string`, optional): Whether to automatically deploy the cron job when the specified branch is updated. Defaults to 'yes'. One of: `yes`, `no`. Default: `yes`.
- `branch` (`string`, optional): The repository branch to deploy. This branch will be deployed when you manually trigger deploys and when auto-deploy is enabled. If left empty, this will fall back to the default branch of the repository.
- `buildCommand` (`string`, optional): The command used to build your cron job. For example, 'npm install' for Node.js or 'pip install -r requirements.txt' for Python. Required unless runtime is 'docker'.
- `dockerCommand` (`string`, optional): Overrides the image's startup command. When omitted, uses the Dockerfile's ENTRYPOINT and CMD. An empty string also uses that default. Applies when runtime is 'docker'. Default: ``.
- `dockerContext` (`string`, optional): Build context directory, relative to the repository root. Defaults to '.'. Applies when runtime is 'docker'. Default: `.`.
- `dockerfilePath` (`string`, optional): Path to the Dockerfile, relative to the repository root. Defaults to './Dockerfile'. Applies when runtime is 'docker'. Default: `./Dockerfile`.
- `envVars` (`array`, optional): Environment variables to set for your cron job. These are exposed during builds and at runtime.
- `plan` (`string`, optional): The pricing plan for your cron job. Different plans offer different levels of resources and features. One of: `free`, `starter`, `standard`, `pro`, `pro_plus`, `pro_max`, `pro_ultra`, `0.5c-512mb`, `1c-2g`, `2c-4g`, `2c-8g`, `2c-16g`, `4c-8g`, `4c-16g`, `4c-32g`, `8c-16g`, `8c-32g`, `8c-64g`, `12c-24g`, `12c-48g`, `12c-96g`. Default: `starter`.
- `region` (`string`, optional): The geographic region where your cron job will be deployed. Defaults to Oregon. One of: `oregon`, `frankfurt`, `singapore`, `ohio`, `virginia`. Default: `oregon`.
- `repo` (`string`, optional): The repository containing the source code for your cron job. Must be a valid Git URL that Render can clone and deploy. Do not include the branch in the repo string. You can instead supply a 'branch' parameter.
- `startCommand` (`string`, optional): The command that runs when your cron job executes. For example, 'node scripts/cleanup.js' for Node.js or 'python scripts/process_data.py' for Python. Required unless runtime is 'docker'.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"name":"<name>","runtime":"node","schedule":"<schedule>"}`

### `rendermcp_create_key_value`

Create Key Value instance · Write

Create a new Key Value instance in your Render account

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name of the Key Value instance
- `maxmemoryPolicy` (`string`, optional): The eviction policy for the Key Value store. One of: `noeviction`, `allkeys_lfu`, `allkeys_lru`, `allkeys_random`, `volatile_lfu`, `volatile_lru`, `volatile_random`, `volatile_ttl`.
- `persistenceMode` (`string`, optional): The data persistence behavior for the Key Value store. One of: `journal_snapshot`, `snapshot`, `off`.
- `plan` (`string`, optional): Pricing plan for the Key Value instance. One of: `free`, `starter`, `standard`, `pro`, `pro_plus`, `256mb`, `1g`, `5g`, `10g`, `20g`, `40g`. Default: `free`.
- `region` (`string`, optional): Region where the Key Value instance will be deployed. One of: `oregon`, `frankfurt`, `singapore`, `ohio`, `virginia`. Default: `oregon`.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"name":"<name>"}`

### `rendermcp_create_postgres`

Create Postgres instance · Write

Create a new Postgres instance in your Render account

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the database as it will appear in the Render Dashboard
- `version` (`number`, required): PostgreSQL version to use (e.g., 14, 15)
- `diskSizeGb` (`number`, optional): Your database's capacity, in GB. You can increase storage at any time, but you can't decrease it. Specify 1 GB or any multiple of 5 GB.
- `plan` (`string`, optional): Pricing plan for the database. One of: `free`, `basic_256mb`, `basic_1gb`, `basic_4gb`, `pro_4gb`, `pro_8gb`, `pro_16gb`, `pro_32gb`, `pro_64gb`, `pro_128gb`, `pro_192gb`, `pro_256gb`, `pro_384gb`, `pro_512gb`, `accelerated_16gb`, `accelerated_32gb`, `accelerated_64gb`, `accelerated_128gb`, `accelerated_256gb`, `accelerated_384gb`, `accelerated_512gb`, `accelerated_768gb`, `accelerated_1024gb`, `0.1c-256mb`, `0.5c-1g`, `1c-2g`, `1c-4g`, `2c-4g`, `2c-8g`, `2c-16g`, `4c-16g`, `4c-32g`, `8c-32g`, `8c-64g`, `16c-64g`, `16c-128g`, `32c-128g`, `32c-256g`, `48c-192g`, `48c-384g`, `64c-256g`, `64c-512g`, `96c-384g`, `96c-768g`, `128c-512g`, `128c-1024g`. Default: `free`.
- `region` (`string`, optional): Region where the database will be deployed. One of: `oregon`, `frankfurt`, `singapore`, `ohio`, `virginia`.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"name":"<name>","version":14}`

### `rendermcp_create_static_site`

Create static site · Write

Create a new static site in your Render account. Apps that consist entirely of statically served assets (commonly HTML, CSS, and JS). Static sites have a public onrender.com subdomain and are served over a global CDN. Create a static site if you're building with a framework like: Create React App, Vue.js, Gatsby, etc.This tool is currently limited to support only a subset of the static site configuration parameters.To create a static site without those limitations, please use the dashboard at: https://dashboard.render.com/static/new

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `buildCommand` (`string`, required): Render runs this command to build your app before each deploy. For example, 'yarn; yarn build' a React app.
- `name` (`string`, required): A unique name for your service. This will be used to generate the service's URL if it is public.
- `autoDeploy` (`string`, optional): Whether to automatically deploy the service when the specified branch is updated. Defaults to 'yes'. One of: `yes`, `no`. Default: `yes`.
- `branch` (`string`, optional): The repository branch to deploy. This branch will be deployed when you manually trigger deploys and when auto-deploy is enabled. If left empty, this will fall back to the default branch of the repository.
- `envVars` (`array`, optional): Environment variables to set for your service. These are exposed during builds and at runtime.
- `publishPath` (`string`, optional): The relative path of the directory containing built assets to publish. Examples: ./, ./build, dist and frontend/build. This is the directory that will be served to the public. Default: `public`.
- `repo` (`string`, optional): The repository containing the source code for your service. Must be a valid Git URL that Render can clone and deploy. Do not include the branch in the repo string. You can instead supply a 'branch' parameter.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"buildCommand":"<buildCommand>","name":"<name>"}`

### `rendermcp_create_web_service`

Create web service · Write

Create a new web service in your Render account. A web service is a public-facing service that can be accessed by users on the internet. By default, these services are automatically deployed when the specified branch is updated and do not require a manual trigger of a deploy. The user should only be prompted to manually trigger a deploy if auto-deploy is disabled. This tool is currently limited to support only a subset of the web service configuration parameters. Deploying prebuilt images from a container registry is not supported. To create a service without those limitations, please use the dashboard at: https://dashboard.render.com/web/new

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): A unique name for your service. This will be used to generate the service's URL if it is public.
- `runtime` (`string`, required): The runtime environment for your service. This determines how your service is built and run. One of: `node`, `python`, `go`, `rust`, `ruby`, `elixir`, `docker`.
- `autoDeploy` (`string`, optional): Whether to automatically deploy the service when the specified branch is updated. Defaults to 'yes'. One of: `yes`, `no`. Default: `yes`.
- `branch` (`string`, optional): The repository branch to deploy. This branch will be deployed when you manually trigger deploys and when auto-deploy is enabled. If left empty, this will fall back to the default branch of the repository.
- `buildCommand` (`string`, optional): The command used to build your service. For example, 'npm run build' for Node.js or 'pip install -r requirements.txt' for Python. Required unless runtime is 'docker'.
- `dockerCommand` (`string`, optional): Overrides the image's startup command. When omitted, uses the Dockerfile's ENTRYPOINT and CMD. An empty string also uses that default. Applies when runtime is 'docker'. Default: ``.
- `dockerContext` (`string`, optional): Build context directory, relative to the repository root. Defaults to '.'. Applies when runtime is 'docker'. Default: `.`.
- `dockerfilePath` (`string`, optional): Path to the Dockerfile, relative to the repository root. Defaults to './Dockerfile'. Applies when runtime is 'docker'. Default: `./Dockerfile`.
- `envVars` (`array`, optional): Environment variables to set for your service. These are exposed during builds and at runtime.
- `plan` (`string`, optional): The pricing plan for your service. Different plans offer different levels of resources and features. One of: `free`, `starter`, `standard`, `pro`, `pro_plus`, `pro_max`, `pro_ultra`, `0.5c-512mb`, `1c-2g`, `2c-4g`, `2c-8g`, `2c-16g`, `4c-8g`, `4c-16g`, `4c-32g`, `8c-16g`, `8c-32g`, `8c-64g`, `12c-24g`, `12c-48g`, `12c-96g`. Default: `free`.
- `region` (`string`, optional): The geographic region where your service will be deployed. Defaults to Oregon. Choose the region closest to your users for best performance. One of: `oregon`, `frankfurt`, `singapore`, `ohio`, `virginia`. Default: `oregon`.
- `repo` (`string`, optional): The repository containing the source code for your service. Must be a valid Git URL that Render can clone and deploy. Do not include the branch in the repo string. You can instead supply a 'branch' parameter.
- `startCommand` (`string`, optional): The command used to start your service. For example, 'npm start' for Node.js or 'gunicorn app:app' for Python. Required unless runtime is 'docker'.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"name":"<name>","runtime":"node"}`

### `rendermcp_create_workflow`

Create workflow · Write

Create a real workflow in the selected workspace from a Git repository Render can clone. The configuration request is limited to 256 KiB. Automatic deployment defaults to commit; creation starts the initial build unless autoDeploy is off. Do not immediately call create_workflow_version after creation. Use list_workflow_versions and get_workflow_version to check readiness. A timeout does not prove creation failed; reconcile with list_workflows before retrying. Task execution is separate.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `buildCommand` (`string`, required): Command that installs dependencies and builds the workflow; must not be blank
- `name` (`string`, required): Name of the new workflow; must not be blank
- `repo` (`string`, required): Git repository URL Render can clone. Pass its branch separately; do not include credentials in the URL
- `runCommand` (`string`, required): Command that registers the workflow's tasks; must not be blank
- `runtime` (`string`, required): Workflow language runtime. One of: `node`, `python`, `go`, `ruby`, `elixir`.
- `autoDeploy` (`string`, optional): commit deploys on pushes, checksPass waits for repository checks, off requires a manual deploy. Omit for Render's commit default. Creation starts an initial build for commit or checksPass. Sent to the API as autoDeployTrigger. One of: `commit`, `checksPass`, `off`.
- `branch` (`string`, optional): Repository branch; omit to use the repository's default branch
- `envVars` (`array`, optional): Environment variables for builds and task execution, as key/value objects. Empty values are allowed. No fromDatabase or generateValue inputs
- `region` (`string`, optional): Workflow region; defaults to oregon. One of: `oregon`, `frankfurt`, `singapore`, `ohio`, `virginia`. Default: `oregon`.
- `rootDir` (`string`, optional): Repository subdirectory containing the workflow; omit to use the repository root
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"buildCommand":"<buildCommand>","name":"<name>","repo":"<repo>","runCommand":"<runCommand>","runtime":"node"}`

### `rendermcp_plan_blueprint`

Plan Blueprint sync · Write

This tool is in public alpha (early access). Access to this tool and its contract are subject to change. Preview infrastructure changes for an existing Blueprint using its configured Git branch and Blueprint file path. Push any local Blueprint file changes before calling this tool so that the plan includes them. Planning does not apply infrastructure changes. Review the plan with the user before calling approve_blueprint, even when auto-sync is enabled. If another sync is pending or running, wait for it to finish before requesting a new plan. The tool waits for planning to finish and returns planningOutcome, sync, and notices. Use planningOutcome to determine whether planning succeeded and what to do next. Read planningOutcome to determine the next step. If planningOutcome is "failed", inspect the errors in notices. Address the reported issues and push any Blueprint file changes, then call plan_blueprint with the Blueprint ID again. Do not approve a failed plan, even if sync is present. If planningOutcome is "no_changes", this planning attempt found no infrastructure changes. Do not call approve_blueprint for this result. If planningOutcome is "planned", sync contains the proposed infrastructure changes. Summarize them for the user or share sync.dashboardUrl for review. To apply the changes, call approve_blueprint with the Blueprint ID and follow its guidance for supplying any required environment variable values. Call approve_blueprint only after the user authorizes applying the reviewed plan. Providing or allowing generation of manual environment values, or accepting costs, does not by itself authorize deployment.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `blueprintId` (`string`, required): Specify the Blueprint ID, which starts with exs-. Use the Blueprint ID rather than a sync ID.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"blueprintId":"<blueprintId>"}`

### `rendermcp_select_workspace`

Select workspace · Write

Deprecated: this tool is scheduled for removal; pass the confirmed workspaceId directly on each tool call instead. Select a workspace for clients that rely on MCP session state. This tool should only be used after explicitly asking the user to select one, it should not be invoked as part of an automated process. Having the wrong workspace selected can lead to destructive actions being performed on unintended resources.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ownerID` (`string`, required): The ID of the workspace to select

Example input: `{"ownerID":"<ownerID>"}`

### `rendermcp_start_flow_run`

Start flow run · Write

Start a flow run in the selected workspace using an exact flow ID from list_flows. This runs the user's code, so start a run only when asked to. The ID selects a registered workflow version; it does not automatically select the latest version. After create_workflow_version, wait until get_workflow_version reports the new version ready, then use list_flows with that workflowVersionId to find its flow ID. Returns the new run, which starts pending; poll get_flow_run until it is terminal, then read get_flow_run_results, list_flow_run_steps, and list_logs. Always pass an idempotencyKey. If the call times out or disconnects, retry with the same key to get the same run, never without one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `flow` (`string`, required): Exact flow ID (flw-...) returned as id by list_flows. Select the desired workflowVersionId when listing flows. Slugs are not accepted
- `idempotencyKey` (`string`, optional): A fresh UUID for this run. Repeating it within 24 hours returns the first run instead of starting another, and ignores the repeated input. Keys are scoped to the workflow
- `input` (`array`, optional): The flow's arguments: an array for positional arguments or an object for named ones. Omit for a flow that takes none. The request is limited to 256 KiB
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"flow":"<flow>"}`

### `rendermcp_approve_blueprint`

Approve Blueprint sync · Destructive

This tool is in public alpha (early access). Access to this tool and its contract are subject to change. Approve and apply the Blueprint's newest planned sync after confirming that planning succeeded. Approval can update existing resources. After the first approval, Git pushes apply changes automatically when autoSync is enabled. Manually requested plans require approval even when autoSync is enabled. Call approve_blueprint only after the user authorizes applying the reviewed plan. Providing or allowing generation of manual environment values, or accepting costs, does not by itself authorize deployment. Supply a user-provided value in manualEnvVars for every entry in sync.requiredManualEnvVars. Use values the user has already supplied and ask only for missing values. Never invent a value. These values appear as plaintext in the agent context. If the user prefers to keep secrets outside that context, explain that they can supply manualEnvVars directly through POST /v1/blueprints/{blueprintId}/approve, or approve the sync at dashboardUrl and then set values on each service's Environment page. For the Dashboard option, explain that initial deployments may fail until the values are set. The tool returns before the sync and deployments finish. Report the returned sync state and share dashboardUrl so the user can track progress in the Render Dashboard.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `blueprintId` (`string`, required): Specify the Blueprint ID, which starts with exs-. Use the Blueprint ID, not a sync ID.
- `manualEnvVars` (`array`, optional): Provide values for the environment variables listed in sync.requiredManualEnvVars.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"blueprintId":"<blueprintId>"}`

### `rendermcp_cancel_flow_run`

Cancel flow run · Destructive

Request cancellation of a pending or running flow run. Cancellation stops the flow and cannot be undone. Returns once the request is accepted; poll get_flow_run until the status is canceled.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `flowRunId` (`string`, required): Exact ID of the flow run to cancel in the selected workspace
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"flowRunId":"<flowRunId>"}`

### `rendermcp_create_workflow_version`

Create workflow version · Destructive

Request a new deployment of an existing workflow. This changes which version subsequent task runs use once ready; it does not start a task run. Skip after creation or a push when an automatic deployment is already expected: commit starts on pushes, checksPass waits for repository checks. Use for manual deployment when autoDeploy is off, an explicitly requested redeploy, or a chosen commit. Returns acceptance, not readiness; follow with get_workflow_version or list_workflow_versions. Do not automatically retry a timed-out or disconnected request.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `workflowId` (`string`, required): Exact ID of the workflow to deploy in the selected workspace
- `commit` (`string`, optional): Git commit to deploy; omit to deploy the linked branch's current commit
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"workflowId":"<workflowId>"}`

### `rendermcp_trigger_deploy`

Trigger deploy · Destructive

Trigger a new deploy for a service. Services with autoDeploy enabled deploy automatically when their branch or image is updated, so do NOT use this tool after pushing code to such a service — the push already triggers a deploy. Use it only when a deploy won't happen automatically: services with autoDeploy disabled, redeploying without a code change, or redeploying with a cleared build cache.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `serviceId` (`string`, required): The ID of the service to trigger a deploy for
- `clearCache` (`boolean`, optional): Whether to clear the build cache before deploying. Defaults to false. Default: `false`.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"serviceId":"<serviceId>"}`

### `rendermcp_update_blueprint`

Update Blueprint · Destructive

This tool is in public alpha (early access). Access to this tool and its contract are subject to change. Update a Blueprint's name, Git branch, Blueprint file path, or auto-sync setting. Provide the Blueprint ID and at least one setting. Omitted settings retain their current values. Empty or whitespace-only names, branches, and paths are rejected. If all supplied values match the Blueprint's current settings, the tool returns the Blueprint without updating it or creating a plan. Changing the branch or path also creates a plan. Changing only the name or auto-sync setting does not create a plan. Planning uses the Blueprint file in the remote Git repository. When changing the branch or path, ensure any local Blueprint file changes intended for the plan have been pushed. The tool waits for planning to finish before returning. Changes to the Blueprint's settings take effect immediately. Review any returned plan with the user before calling approve_blueprint, even when auto-sync is enabled. To request a plan without updating the Blueprint, use plan_blueprint. If an update request fails, changes may still have been applied to the Blueprint. Consider checking its current settings before retrying. The response includes blueprint, planningOutcome, sync, notices, and error. If planningOutcome and error are both null, planning was skipped. Report the Blueprint update and the planning outcome separately to the user. If error is non-null, explain that the Blueprint was updated but no planning result is available. When planningOutcome is non-null, use it to determine the next step. Read planningOutcome to determine the next step. If planningOutcome is "failed", inspect the errors in notices. Address the reported issues and push any Blueprint file changes, then call plan_blueprint with the Blueprint ID again. Do not approve a failed plan, even if sync is present. If planningOutcome is "no_changes", this planning attempt found no infrastructure changes. Do not call approve_blueprint for this result. If planningOutcome is "planned", sync contains the proposed infrastructure changes. Summarize them for the user or share sync.dashboardUrl for review. To apply the changes, call approve_blueprint with the Blueprint ID and follow its guidance for supplying any required environment variable values. Call approve_blueprint only after the user authorizes applying the reviewed plan. Providing or allowing generation of manual environment values, or accepting costs, does not by itself authorize deployment.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `blueprintId` (`string`, required): This ID identifies the Blueprint to update. Blueprint IDs start with exs-. Use the Blueprint ID rather than a sync ID.
- `autoSync` (`boolean`, optional): Set this to true to enable automatic syncing on later Git pushes, or false to disable it. Automatic syncing requires approval of the Blueprint's first sync. Omit this setting to keep its current value.
- `branch` (`string`, optional): This value sets the Git branch from which the Blueprint file is read. If it differs from the current branch, the tool also creates a plan. Omit this setting to keep the current branch.
- `name` (`string`, optional): This value sets the Blueprint's new name. Omit this setting to keep the current name.
- `path` (`string`, optional): This value sets the Blueprint file's new path relative to the repository root. If it differs from the current path, the tool also creates a plan. Omit this setting to keep the current path.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"blueprintId":"<blueprintId>"}`

### `rendermcp_update_environment_variables`

Update environment variables · Destructive

Update environment variables for a service. By default, environment variables passed in will be merged with the service's existing environment variables. This makes it safe to update environment variableswithout pulling the existing ones into the MCP host's context. To replace all existing environment variables, set the 'replace' parameter to 'true'.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `envVars` (`array`, required): The list of environment variables to update or set for the service.
- `serviceId` (`string`, required): The ID of the service to update
- `replace` (`boolean`, optional): Whether to replace all existing environment variables with the provided list, or merge with the existing ones. Defaults to false. Default: `false`.
- `workspaceId` (`string`, optional): The ID of the Render workspace to use. Reuse the workspaceId the user confirmed from list_workspaces.

Example input: `{"envVars":[],"serviceId":"<serviceId>"}`

## Related

Other Developer Tools connectors ([all 200](/agentkit/connectors/?category=developer-tools)):

- [GitHub](/agentkit/connectors/github/): Scalekit connector, OAuth, 217 tools
- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
