Render MCP

Created By
shivammaurya042a year ago
MCP server for managing services on Render.com
Overview

what is Render.com MCP?

Render is a cloud hosting platform offering a simplified way to build, deploy, and scale applications and websites.

how to use Render.com MCP?

To use Render.com MCP, connect it to your preferred Model Context Protocol (MCP) client, such as the Claude app or windsurf/cursor. You can then instruct your LLM on the tasks you want to perform, and it will manage your Render services without the need for a user interface.

Usage

To integrate this server with the MCP client (ex: claude app, windsurf/cursor, cline), add the following to your app's server configuration:

NPX

{
  "mcpServers": {
    "render": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-render"
      ],
      "env": {
        "RENDER_API_KEY": "<YOUR_RENDER_API_KEY>"
      }
    }
  }
}

key features of Render.com MCP?

  1. Get services list
  2. Get deploys list
  3. Trigger deploy
  4. Retrieve deploy
  5. Cancel deploy
  6. List environment variables
  7. Add/update environment variables
  8. Delete environment variables
  9. Get logs

use cases of Render.com MCP?

  1. Get me render services list.
  2. What is the status of my last deploy for <service name>.
  3. Check logs for <service name>.
  4. Redeploy <service name>.
  5. Add new environment variable for <service name>, <env key> = <env value>.

FAQ from Render.com MCP?

  • What is the purpose of Render.com MCP?

It simplifies the management of services on Render.com, allowing for easier deployment and scaling of applications.

  • Is there a cost associated with using Render.com MCP?

Render.com MCP is free to use, but you will need a Render.com account to manage your services.

Server Config

{
  "mcpServers": {
    "render": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-render"
      ],
      "env": {
        "RENDER_API_KEY": "<YOUR_RENDER_API_KEY>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shivammaurya042
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago