render-mcp
为 AI 编码工具连接并配置 Render MCP server——按工具配置(Cursor、Claude Code、Codex)、认证、工作区选择、工具目录及排障。当 MCP 未配置、list_services() 失败、用户询问 Render MCP 配置,或某个操作类技能需要 MCP 但尚未连接时使用。触发词:MCP、Render MCP、list_services、MCP setup、MCP server、API key、Bearer token、mcp.render.com、workspace selection。
- License 许可
- MIT
- 最近更新
- 2026-11-08
- Stars
- ★ 37
- Forks
- 1
01 前言 Front Matter
- name
- render-mcp
- license
- MIT
- metadata
- { "author": "Render", "version": "1.0.0", "category": "operations" }
- description
- 为 AI 编码工具连接并配置 Render MCP server——按工具配置(Cursor、Claude Code、Codex)、认证、工作区选择、工具目录及排障。当 MCP 未配置、list_services() 失败、用户询问 Render MCP 配置,或某个操作类技能需要 MCP 但尚未连接时使用。触发词:MCP、Render MCP、list_services、MCP setup、MCP server、API key、Bearer token、mcp.render.com、workspace selection。
- compatibility
- Render MCP server (hosted at mcp.render.com)
02 资源文件 2
- 参考文档agents/openai.yaml202 B
- 参考文档references/troubleshooting.md3.1 KB
03 SKILL.md 正文
Render MCP Server
The Render MCP server lets AI coding tools manage Render services, databases, deploys, logs, and metrics directly. This skill covers setup, authentication, workspace selection, the tool catalog, and troubleshooting.
Action skills (render-deploy, render-debug, render-monitor) use MCP tools for their workflows. If MCP is not connected, set it up using this skill first.
When to Use
list_services()fails or MCP tools are unavailable- First-time Render MCP setup for any AI tool
- User asks how to connect their AI tool to Render
- Switching workspaces or troubleshooting auth errors
- Discovering which MCP tools exist and what they do
Connection Details
| Property | Value |
|---|---|
| URL | https://mcp.render.com/mcp |
| Transport | HTTP (streamable) |
| Auth | Bearer token (Render API key) |
| API key page | https://dashboard.render.com/u/*/settings#api-keys |
| Docs | https://render.com/docs/mcp-server |
Setup by Tool
Cursor
-
Get an API key from the Render Dashboard
-
Add to
~/.cursor/mcp.json:
{
"mcpServers": {
"render": {
"url": "https://mcp.render.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
- Restart Cursor, then verify with
list_services()
Claude Code
-
Get an API key from the Render Dashboard
-
Add the MCP server:
claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
- Restart Claude Code, then verify with
list_services()
Codex
-
Get an API key from the Render Dashboard
-
Set the key in your shell:
export RENDER_API_KEY="<YOUR_API_KEY>"
- Add the MCP server:
codex mcp add render --url https://mcp.render.com/mcp --bearer-token-env-var RENDER_API_KEY
- Restart Codex, then verify with
list_services()
Other Tools
For tools not listed above, use the generic HTTP MCP configuration:
- URL:
https://mcp.render.com/mcp - Auth header:
Authorization: Bearer <YOUR_API_KEY> - Transport: HTTP (streamable HTTP, not SSE)
See Render MCP docs for tool-specific instructions.
Workspace Selection
After MCP is connected, set the active workspace:
Set my Render workspace to [WORKSPACE_NAME]
Or programmatically:
get_selected_workspace() # Check current
list_workspaces() # List available
All MCP operations run against the active workspace.
Tool Catalog
Service management
| Tool | Purpose |
|---|---|
list_services() |
List all services and datastores |
get_service(serviceId) |
Get service details |
create_web_service(...) |
Create a web service from Git repo |
create_static_site(...) |
Create a static site from Git repo |
update_service(serviceId, ...) |
Update service configuration |
restart_service(serviceId) |
Restart a service |
Deploys
| Tool | Purpose |
|---|---|
list_deploys(serviceId, limit) |
List deploys for a service |
trigger_deploy(serviceId) |
Trigger a new deploy |
Logs
| Tool | Purpose |
|---|---|
list_logs(resource, level, type, text, statusCode, limit) |
Query logs with filters |
Key filters: level (error, warn, info), type (build, deploy), text (search string), statusCode (HTTP codes).
Metrics
| Tool | Purpose |
|---|---|
get_metrics(resourceId, metricTypes, ...) |
Get service or database metrics |
Metric types: cpu_usage, memory_usage, cpu_limit, memory_limit, http_latency, http_request_count, active_connections.
Optional: httpLatencyQuantile (0.5, 0.95, 0.99), httpPath (filter by endpoint).
Databases
| Tool | Purpose |
|---|---|
list_postgres_instances() |
List Postgres databases |
get_postgres(postgresId) |
Get database details |
query_render_postgres(postgresId, sql) |
Run SQL query |
Key Value
| Tool | Purpose |
|---|---|
list_key_value() |
List Key Value instances |
get_key_value(keyValueId) |
Get Key Value details |
Environment Variables
| Tool | Purpose |
|---|---|
update_environment_variables(serviceId, envVars) |
Set env vars on a service |
Workspace
| Tool | Purpose |
|---|---|
list_workspaces() |
List available workspaces |
get_selected_workspace() |
Get the active workspace |
Common Mistakes
| Mistake | Fix |
|---|---|
| Wrong URL (using SSE endpoint) | Use https://mcp.render.com/mcp (not /sse) |
| Expired or invalid API key | Generate a new key from Dashboard > Account Settings > API Keys |
| Wrong workspace selected | Run list_workspaces() and switch to the correct one |
| Using MCP to create image-backed services | Not supported — use Dashboard or API for prebuilt Docker images |
Missing Bearer prefix in auth header |
Header must be Authorization: Bearer <key> |
Troubleshooting
See references/troubleshooting.md for connection errors, auth failures, timeout issues, and tool-specific quirks.
References
| Document | Contents |
|---|---|
references/troubleshooting.md |
Connection errors, auth failures, tool-specific issues, timeout handling |
Related Skills
- render-deploy — Deploy flows using MCP tools
- render-debug — Debug failures using MCP logs and metrics
- render-monitor — Monitor health using MCP metrics
- render-cli — CLI alternative when MCP is unavailable
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建(通过 CLI 或手动方式)、SDK 安装(Python 或 TypeScript)、任务模式(重试、子任务、扇出)、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。
render-web-services
配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署,或排查端口绑定问题时使用。
render-static-sites
在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React/Vue/Hugo/Gatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header,或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。