Use Render from Codex to deploy apps, validate render.yaml, debug failed deploys, monitor services, and work through common platform workflows.

• Bundled Render skills for deployment, debugging, monitoring, migrations, and workflows
• A bundled .mcp.json file for the hosted Render MCP server
• A helper script at scripts/validate-render-yaml.sh for render blueprints validate
• Plugin metadata and assets for Codex installation

Install the plugin from the Codex plugin library in the app when it is available there. That is the preferred install path for most users.

Use the local install flow below for development, testing, or pre-release access.

1. Copy the plugin into ~/.codex/plugins/render:

mkdir -p ~/.codex/plugins
rsync -a ./ ~/.codex/plugins/render/

2. Add the plugin to ~/.agents/plugins/marketplace.json.

If the file already exists, add the render entry to the existing plugins array.

{
  "name": "local-plugins",
  "interface": {
    "displayName": "Local Plugins"
  },
  "plugins": [
    {
      "name": "render",
      "source": {
        "source": "local",
        "path": "./.codex/plugins/render"
      },
      "policy": {
        "installation": "AVAILABLE",
        "authentication": "ON_INSTALL"
      },
      "category": "Developer Tools"
    }
  ]
}

3. Restart Codex.
4. Open the plugin directory in Codex and install Render from your marketplace.

Use the plugin to:

• Deploy a project to Render
• Validate and troubleshoot render.yaml
• Debug failed deploys and check service status
• Work through common setup and migration tasks

Good first prompts:

• Help me deploy this project to Render.
• Help me validate my render.yaml for Render.
• Debug a failed Render deployment.

Many Render workflows depend on the Render CLI.

1. Install the Render CLI:

brew install render

2. Authenticate:

render login

3. Verify access:

render whoami -o json

If render whoami -o json fails, fix authentication before you rely on Render workflows in Codex.

The plugin bundles .mcp.json for the hosted Render MCP server. To use it, set RENDER_API_KEY before you start Codex.

1. Create a Render API key in the Render Dashboard.
2. Open Account settings > API Keys.
3. Start Codex from Terminal with the key set:

export RENDER_API_KEY="rnd_..."
open -a Codex

4. Keep using that Terminal-launched session. If you start Codex from the Dock or Spotlight, it might not inherit RENDER_API_KEY.
5. If you want the variable to persist, add it to your shell profile such as ~/.zshrc, then start a new Terminal session.

Never set RENDER_API_KEY to a placeholder value such as your_render_api_key. Use a real key or leave the variable unset.

Run the sync script to refresh skills/ from render-oss/skills:

./scripts/sync-skills.sh

GitHub Actions also runs .github/workflows/sync-skills.yml each day and opens a pull request when upstream skills change.

MIT. See LICENSE.