Render MCP setup: workspace, services and logs

Choose an existing Render service as your test case. Note its workspace, service ID and the timestamp of a known deployment. These details help you recognise whether a response belongs to the intended environment. Start by looking up that service; creating a new resource is unnecessary for checking the connection.

Choose an authentication method

The hosted server is available at https://mcp.render.com/mcp. Render documents OAuth for supported integrations and API keys for relevant manual or non-interactive setups. The VS Code example below deliberately uses the documented bearer method. Create a key in your Render account and enter it through the client’s protected input prompt.

{
  "servers": {
    "render": {
      "type": "http",
      "url": "https://mcp.render.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:render-api-key}"
      }
    }
  },
  "inputs": [
    {
      "id": "render-api-key",
      "type": "promptString",
      "description": "Render API key",
      "password": true
    }
  ]
}

VS Code resolves ${input:render-api-key}. Do not replace that reference with a real key in a shared project file. password: true masks the input dialog; it does not restrict the key’s permissions. The VS Code guide covers the file format and starting the connection.

Select the workspace and compare the result

1. Start the connection and inspect its tool list. List the accessible workspaces, then select the specific workspace intended for this test.

2. List services within that workspace. Compare your prepared service ID with the Render dashboard. Matching names alone do not establish that you selected the same resource.

3. Read the existing deployment history or a small log excerpt. Specify the service and time range explicitly instead of requesting every available log.

4. Record the result, time and workspace. Repeat the selection after restarting the client before drawing conclusions about the environment from another response.

Narrow down errors

The management server can also trigger deployments and change environment variables. The suggested read test does not disable those operations. Use the access planner to decide which account permissions and tools you need. A shared test report usually needs the service ID and comparison result; keep access keys and full environment values out of that report.

Common questions

Do I have to install Render MCP locally?

Not for the hosted HTTP connection. Render also documents local variants; avoid adding a duplicate local configuration when the same service is already connected remotely.

Why do I have to select a workspace?

Platform actions operate within the selected workspace. Check it explicitly before treating a missing service as evidence that the resource does not exist.

Is documentation search part of the same server?

No. Render describes a separate experimental connection for documentation questions. The management server accesses your platform resources.

Can I remove the key from the JSON file?

The example already contains only an input reference. Do not put a real key there, and separately check how your client stores credentials after they are entered.

Find additional vendor declarations in the Render registry search. The operations app selection links to more setup guides.

Vendor sources checked on 3 October 2026. The checks are intended for your own environment; no customer account was connected.

1. Render: MCP server
   Show retrieval command

   curl -s https://render.com/docs/mcp-server
2. Render: documentation access
   Show retrieval command

   curl -s https://render.com/docs/llm-support
3. Render: server implementation
   Show retrieval command

   curl -s https://github.com/render-oss/render-mcp-server
4. VS Code: MCP configuration
   Show retrieval command

   curl -s https://code.visualstudio.com/docs/agent-customization/mcp-servers

All posts