{
  "markdown": "# Render Claude plugin\n\nUse Render from Claude Code to deploy apps, validate `render.yaml`, debug failed deploys, monitor services, and work through common platform workflows.\n\n## What you get\n\n- The Render MCP server preconfigured over OAuth (`.mcp.json`) so Claude can manage services, deploys, logs, metrics, and databases directly — no API key required\n- Bundled Render skills for deployment, debugging, monitoring, migrations, and workflows (synced from [render-oss/skills](https://github.com/render-oss/skills))\n- A `render-assistant` agent that specializes in Render deploys\n- Slash commands: `/deploy-to-render` and `/check-render-status`\n- A `PostToolUse` hook that validates `render.yaml` whenever you edit it\n- Helper scripts at `scripts/` for skills sync and Blueprint validation\n\n## Install the plugin\n\nAdd this repo as a Claude Code marketplace, then install the `render` plugin from it:\n\n```\n/plugin marketplace add render-oss/render-plugin-claude-code\n/plugin install render\n```\n\n## Install locally for development\n\n1. Clone this repo, then add it as a local marketplace:\n\n```bash\ngit clone https://github.com/render-oss/render-plugin-claude-code.git\n```\n\n2. In Claude Code, point at the local checkout:\n\n```\n/plugin marketplace add ./render-plugin-claude-code\n/plugin install render\n```\n\n3. Restart Claude Code if the plugin doesn't show up immediately.\n\n## Get started\n\nUse the plugin to:\n\n- Deploy a project to Render\n- Validate and troubleshoot `render.yaml`\n- Debug failed deploys and check service status\n- Work through common setup and migration tasks\n\nGood first prompts:\n\n- `Help me deploy this project to Render.`\n- `Help me validate my render.yaml for Render.`\n- `Debug a failed Render deployment.`\n\nYou can also run the slash commands directly:\n\n- `/deploy-to-render`\n- `/check-render-status`\n\n## Set up the Render CLI\n\nThe plugin uses the Render CLI for live operations and Blueprint validation. Most workflows depend on it.\n\n1. Install the Render CLI:\n\n```bash\nbrew install render\n```\n\n2. Authenticate:\n\n```bash\nrender login\n```\n\n3. Verify access:\n\n```bash\nrender whoami -o json\n```\n\nIf `render whoami -o json` fails, fix authentication before relying on Render workflows in Claude Code.\n\n## MCP server\n\nThe plugin bundles Render's [MCP server](https://render.com/docs/mcp-server) through the `.mcp.json` at the repo root, so Claude can manage your Render services, deploys, logs, metrics, and databases directly.\n\nAuthentication is handled over OAuth — you don't need an API key. The first time Claude uses a Render MCP tool, it opens your browser to sign in to Render and authorize access to `https://mcp.render.com/mcp`. After you approve, Claude connects automatically on future runs.\n\nThe MCP server and the Render CLI (below) are complementary: MCP covers day-to-day service, log, metric, and database operations, while the CLI still backs Blueprint validation and other CLI-only workflows.\n\n## For maintainers\n\nRun the sync script to refresh `skills/` from [render-oss/skills](https://github.com/render-oss/skills):\n\n```bash\n./scripts/sync-skills.sh\n```\n\nGitHub Actions also runs `.github/workflows/sync-skills.yml` each day and opens a pull request when upstream skills change.\n\n## License\n\nMIT. See [LICENSE](LICENSE).\n",
  "bytes": 3258,
  "sha": "70a9b8c8fa18d47a74bb830437fd322db863e09c39f904d7abc8d5b2fbcda4a1",
  "repo_slug": "render-oss/render-plugin-claude-code",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_render_oss_render_plugin_claude_code_ren_3a8ee0e5/readme"
}