Use Render from OpenCode to deploy apps, validate Blueprints, debug failed deploys, monitor services, and work through common platform workflows.
- An npm-installable OpenCode plugin with a
render_validate_blueprinttool - Automatic validation when an agent edits
render.yamlorrender.yml - Bundled Render skills for deploys, debugging, monitoring, migrations, and service configuration
- OpenCode commands for
/deploy-to-renderand/check-render-status - A Render-focused
@rendersubagent - Optional Render MCP server configuration
Until the package is published to npm, install the local OpenCode plugin, skills, commands, and agent directly from GitHub:
curl -fsSL https://raw.githubusercontent.com/render-oss/render-opencode-plugin/main/install.sh | bashThis writes files to ~/.config/opencode/:
plugins/render.tsskills/render-*/SKILL.mdcommands/deploy-to-render.mdcommands/check-render-status.mdagents/render.md
The installer doesn't overwrite existing files unless you pass --force:
curl -fsSL https://raw.githubusercontent.com/render-oss/render-opencode-plugin/main/install.sh | bash -s -- --forcePreview changes without writing files:
curl -fsSL https://raw.githubusercontent.com/render-oss/render-opencode-plugin/main/install.sh | bash -s -- --dry-runInstall the Render MCP server config too:
curl -fsSL https://raw.githubusercontent.com/render-oss/render-opencode-plugin/main/install.sh | bash -s -- --enable-mcpThis preserves your existing opencode.json fields and skips an existing mcp.render entry unless you pass --force. Set RENDER_API_KEY before using Render MCP.
Restart OpenCode after installation.
Add the npm package to your OpenCode config:
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["@render/opencode-plugin"]
}OpenCode installs npm plugins with Bun at startup and caches them in ~/.cache/opencode/node_modules/. This flow requires the package to be published to npm.
OpenCode npm plugins can provide tools and hooks, but they don't automatically register bundled skills, commands, or agents. OpenCode discovers those files from your OpenCode config directory.
Run the explicit setup command after adding the plugin:
npx @render/opencode-plugin setupThis opt-in step writes files to ~/.config/opencode/:
skills/render-*/SKILL.mdcommands/deploy-to-render.mdcommands/check-render-status.mdagents/render.md
The setup command doesn't overwrite existing files unless you pass --force.
npx @render/opencode-plugin setup --forceTo preview changes without writing files:
npx @render/opencode-plugin setup --dry-runTo install into a different OpenCode config directory:
npx @render/opencode-plugin setup --config-dir ./tmp-opencodeIf you want OpenCode to use Render MCP tools, run setup with --enable-mcp:
npx @render/opencode-plugin setup --enable-mcpThis merges the following server into opencode.json:
{
"mcp": {
"render": {
"type": "remote",
"url": "https://mcp.render.com/mcp",
"enabled": true,
"oauth": false,
"headers": {
"Authorization": "Bearer {env:RENDER_API_KEY}"
}
}
}
}Set RENDER_API_KEY in your environment before using Render MCP.
The plugin can validate Blueprints with the Render CLI.
- Install the Render CLI:
brew install render- Authenticate:
render login- Verify access:
render whoami -o jsonIf render whoami -o json fails, fix authentication before relying on live Render workflows in OpenCode.
Good first prompts:
Help me deploy this project to Render.Validate my render.yaml for Render.Debug a failed Render deployment.How are my Render services doing?
You can also run:
/deploy-to-render
/check-render-status
Refresh bundled skills from render-oss/skills:
./scripts/sync-skills.shUse a different source repo or subdirectory:
./scripts/sync-skills.sh --repo https://github.com/render-oss/skills --subdir skillsVerify the package before publishing:
npm run checkMIT. See LICENSE.