개요

렌더 MCP 서버는 모델 컨텍스트 프로토콜(MCP)입니다 LLM을 통해 렌더 리소스와 상호작용할 수 있게 해주는 서버입니다.

시작하기

공식 문서를 따라 MCP 서버를 시작하세요: https://render.com/docs/mcp-server

프로토콜 지원

서버는 Streamable HTTP 및 MCP 프로토콜 버전의 Stdio를 지원합니다 2025-11-25, 2025-06-18, 2025-03-26, 그리고 2024-11-05. Stdio는 세션 없는 프로토콜 [2026-07-28도 지원합니다. 스트리밍 가능한 HTTP 위에 나열된 버전 중 하나로 초기화 핸드셰이크가 필요합니다.

사용 사례

• Render에서 웹 서비스, 정적 사이트, cron 작업 및 데이터베이스 생성 및 관리
• 문제 해결을 돕기 위한 애플리케이션 로그와 배포 상태 모니터링
• 디버깅, 용량 계획 및 최적화를 위한 서비스 성능 지표 모니터링
• LLM 내에서 Postgres 데이터베이스를 직접 조회하기

피드백

피드백을 남겨주세요. GitHub 이슈가 있다면 제출하겠습니다 기능 요청, 버그 보고, 제안, 의견 또는 우려 사항.

도구

작업 공간

• list_workspaces - 접근 가능한 작업 공간을 나열하세요

• 매개변수 불필요

Render MCP Server

Overview

The Render MCP Server is a Model Context Protocol (MCP) server that allows you to interact with your Render resources via LLMs.

Getting Started

Get started with the MCP server by following the official docs: https://render.com/docs/mcp-server

Protocol Support

The server supports Streamable HTTP and stdio with MCP protocol versions 2025-11-25, 2025-06-18, 2025-03-26, and 2024-11-05. Stdio also supports the sessionless protocol 2026-07-28. Streamable HTTP requires the initialize handshake with one of the versions listed above.

Use Cases

• Creating and managing web services, static sites, cron jobs, and databases on Render
• Monitoring application logs and deployment status to help troubleshoot issues
• Monitoring service performance metrics for debugging, capacity planning, and optimization
• Querying your Postgres databases directly inside an LLM

Feedback

Please leave feedback via filing a GitHub issue if you have any feature requests, bug reports, suggestions, comments, or concerns.

Tools

Workspaces

• list_workspaces - List the workspaces that you have access to

  • No parameters required

• select_workspace - Select a workspace to use

  • ownerID: The ID of the workspace to select (string, required). Kept as ownerID so existing callers of this deprecated tool keep working; new code should pass workspaceId on each resource tool call instead.

• get_selected_workspace - Get the currently selected workspace

  • No parameters required

Every resource tool also accepts an optional workspaceId. After the user confirms a workspace from list_workspaces, pass that workspaceId on each related tool call. This keeps the target workspace explicit across MCP reconnects and transport-session changes. If workspaceId is omitted, the server temporarily falls back to the workspace selected in the current MCP session. That implicit session-based behavior is deprecated and is scheduled for removal.

Services

• list_services - List all services in your Render account

  • includePreviews: Whether to include preview services, defaults to false (boolean, optional)

• get_service - Get details about a specific service

  • serviceId: The ID of the service to retrieve (string, required)

• create_web_service - Create a new web service in your Render account

  • name: A unique name for your service (string, required)
  • runtime: Runtime environment for your service (string, required). Accepted values:
    • node
    • python
    • go
    • rust
    • ruby
    • elixir
    • docker
  • buildCommand: Command used to build your service (string, required unless runtime is docker)
  • startCommand: Command used to start your service (string, required unless runtime is docker)