Render

Render

Official

Provision Render services, read deploy logs and metrics, and query Postgres read-only — over a hosted OAuth MCP.

Score 78(?)RenderApache-2.0154Verified Top MCPs for Web Hosting →

Quick answer

What it does

Exposes the Render API as MCP tools grouped by resource: workspaces (`list_workspaces`, `select_workspace`), services (`list_services`, `create_web_service`, `create_static_site`, `create_cron_job`, `update_environment_variables`), deploys (`list_deploys`, `trigger_deploy`), logs (`list_logs`, `list_log_label_values`), metrics (`get_metrics`), Postgres (`create_postgres`, `query_render_postgres`) and Key Value instances.

Best for

  • Provisioning web services, static sites and cron jobs
  • Triggering deploys and reading build logs
  • Performance metrics for services and databases
  • Read-only SQL against Render Postgres

Not for

  • Changing service settings (returns a dashboard link by design)
  • Writing to Postgres

Source: top-mcps.com/mcp/render — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "render": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://mcp.render.com/mcp"
          ]
        }
      }
    }

    Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.render.com/mcp. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI or .mcp.json
    claude mcp add --transport http render https://mcp.render.com/mcp

    Then run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .cursor/mcp.json
    {
      "mcpServers": {
        "render": {
          "url": "https://mcp.render.com/mcp"
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .vscode/mcp.json
    {
      "servers": {
        "render": {
          "type": "http",
          "url": "https://mcp.render.com/mcp"
        }
      }
    }

    VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "render": {
          "serverUrl": "https://mcp.render.com/mcp"
        }
      }
    }

    Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "render": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://mcp.render.com/mcp"
          ]
        }
      }
    }

    Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "streamable-http",
              "url": "https://mcp.render.com/mcp"
            }
          }
        ]
      }
    }

    Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI
    codex mcp add render --url https://mcp.render.com/mcp

    Codex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "render": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://mcp.render.com/mcp"
            ]
          }
        }
      }
    }

    Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ChatGPT → Settings → Connectors (remote URL)
    {
      "name": "Render",
      "transport": "http",
      "url": "https://mcp.render.com/mcp"
    }

    Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

ToolDescriptionArgsSide effects
list_workspacesList the workspaces the account can reach.—Read
select_workspaceChoose the workspace subsequent calls act on.—Read
list_servicesList all services in the account.—Read
create_web_serviceCreate a new web service.—Write
create_static_siteCreate a new static site.—Write
create_cron_jobCreate a new cron job.—Write
update_environment_variablesReplace all environment variables for a service.—Write
trigger_deployTrigger a deploy for a service that autoDeploy would not cover.—Write
list_deploysList deployment history for a service.—Read
list_logsList logs matching the provided filters.—Read
get_metricsPerformance metrics for services, Postgres and Key Value instances.—Read
query_render_postgresRun a read-only SQL query against a Render-hosted Postgres database.—Read
create_postgresCreate a new PostgreSQL database.—Write
create_key_valueCreate a new Key Value instance.—Write

Security & scope

Access scope
Read + write
Sandbox
No sandbox. Workspace selection is the scoping mechanism — `select_workspace` before anything else.
Gotchas
  • `update_environment_variables` replaces the full set for a service. Read the current variables first or the agent silently drops the ones it did not know about.
  • Creating services and databases provisions billable resources. There is no dry-run.
  • Postgres access is read-only by design and stays that way — do not work around it by handing the agent a separate database MCP with write access to the same instance.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. web hosting work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-web-hosting
Compare Render against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Render MCP vs [Railway MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/render
- top-mcps.com listing for Railway
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Render MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/render (fetch https://top-mcps.com/mcp/render.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Web Hosting MCPs

Other tools in the same category worth evaluating.

Cloudflare
Official

Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.

cloudflare, edge, workers, dns
5 minMedium
Official

Deploy a site, read the build, and manage projects, forms and extensions with Netlify's official MCP server.

netlify, web-hosting, deployment, jamstack
5 minLow
Railway
Official

Spin up Railway projects, services, and deploys via remote MCP with OAuth.

railway, hosting, deployment, paas
2 minLow

Compared with Render

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Web Hosting? See all Web Hosting MCPs →