diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
index 6429917..f48e1ed 100644
--- a/.claude-plugin/marketplace.json
+++ b/.claude-plugin/marketplace.json
@@ -9,7 +9,7 @@
     {
       "name": "render",
       "description": "Deploy, debug, and monitor applications on Render",
-      "version": "0.1.0",
+      "version": "0.2.0",
       "author": {
         "name": "Render",
         "email": "devrel@render.com"
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 0ffcf9f..8188595 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "render",
-  "description": "Deploy, debug, and monitor applications on Render. Includes skills, an agent, slash commands, and a render.yaml validation hook.",
-  "version": "0.1.0",
+  "description": "Deploy, debug, and monitor applications on Render. Includes skills, an agent, slash commands, a render.yaml validation hook, and the Render MCP server preconfigured over OAuth.",
+  "version": "0.2.0",
   "author": {
     "name": "Render",
     "email": "support@render.com",
diff --git a/.mcp.json b/.mcp.json
new file mode 100644
index 0000000..5245e16
--- /dev/null
+++ b/.mcp.json
@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "render": {
+      "type": "http",
+      "url": "https://mcp.render.com/mcp",
+      "oauth": {
+        "clientId": "claude"
+      }
+    }
+  }
+}
diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 0000000..2be2a0a
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,25 @@
+# Changelog
+
+All notable changes to the Render plugin are documented here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.2.0] - 2026-07-06
+
+### Added
+
+- Bundled the Render MCP server, preconfigured over OAuth (`.mcp.json`), so Claude can manage services, deploys, logs, metrics, and databases directly — no API key required.
+- README section documenting the MCP server, its OAuth sign-in flow, and how it complements the Render CLI.
+
+## [0.1.0] - Initial release
+
+### Added
+
+- Skills covering deploying, debugging, and monitoring applications on Render, including blueprints, web services, static sites, background workers, cron jobs, Postgres, key-value stores, disks, domains, networking, scaling, environment variables, Docker, private services, the Render CLI, and Heroku migration.
+- `render-assistant` agent.
+- `deploy-to-render` and `check-render-status` slash commands.
+- `render.yaml` validation hook.
+
+[0.2.0]: https://github.com/render-oss/render-plugin-claude-code/releases/tag/v0.2.0
+[0.1.0]: https://github.com/render-oss/render-plugin-claude-code/releases/tag/v0.1.0
diff --git a/README.md b/README.md
index 7f9fb48..dd6355a 100644
--- a/README.md
+++ b/README.md
@@ -4,6 +4,7 @@ Use Render from Claude Code to deploy apps, validate `render.yaml`, debug failed
 
 ## What you get
 
+- The Render MCP server preconfigured over OAuth (`.mcp.json`) so Claude can manage services, deploys, logs, metrics, and databases directly — no API key required
 - Bundled Render skills for deployment, debugging, monitoring, migrations, and workflows (synced from [render-oss/skills](https://github.com/render-oss/skills))
 - A `render-assistant` agent that specializes in Render deploys
 - Slash commands: `/deploy-to-render` and `/check-render-status`
@@ -82,7 +83,11 @@ If `render whoami -o json` fails, fix authentication before relying on Render wo
 
 ## MCP server
 
-Render's MCP server isn't included in this plugin yet because it doesn't support OAuth. Once OAuth is available, the plugin will ship with an `.mcp.json` so Claude can use Render MCP tools directly. Until then, the plugin uses the Render CLI for service creation, log retrieval, metrics, and database inspection.
+The 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.
+
+Authentication 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.
+
+The 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.
 
 ## For maintainers