docs: Clarify read-only mode is optional and deployments are allowed by default

facundofarias · claude · facundofarias · commit 2035df003d95 · 2025-11-13T11:28:20.000+01:00
Reorganized documentation to emphasize: - Deployments are allowed by default (no configuration needed) - Read-only mode is completely optional - Full functionality works out of the box - Read-only mode is a safety feature for users who want extra protection This makes it clear that the feature works properly but isn't the default behavior. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/README.md b/README.md
@@ -407,18 +407,22 @@ npm run test:ui       # Interactive UI for debugging
 
 ### Read-Only Mode (Optional)
 
-The DeployHQ MCP Server supports an optional **read-only mode** that can be enabled to prevent deployment creation when using AI assistants.
+**By default, the MCP server allows all operations, including creating deployments.** This is the recommended configuration for most users.
 
-**Default Behavior:**
-- &#9989; All operations work by default (list, get, create)
-- &#9989; Deployments can be created through AI assistants
-- &#9888;&#65039; Consider enabling read-only mode in production environments
+For users who want additional protection against accidental deployments, the server includes an **optional read-only mode** that can be enabled to block deployment creation.
 
-**When to enable read-only mode:**
-- You want to prevent accidental deployments via AI
-- You're connecting to production environments
-- You want an extra layer of protection
+**Default Behavior (No Configuration Needed):**
+- &#9989; Deployments are **allowed by default**
+- &#9989; All operations work: list, get, and create deployments
+- &#9989; Full functionality out of the box
+
+**When you might want to enable read-only mode:**
+- You want extra protection against accidental deployments via AI
+- You're connecting to production environments and want an additional safety layer
 - You only need read access to monitor deployments
+- You're still testing the integration and want to be cautious
+
+**Important:** Read-only mode is **completely optional**. The server works fully without it.
 
 **How to enable read-only mode:**
 
diff --git a/docs/USER_GUIDE.md b/docs/USER_GUIDE.md
@@ -585,16 +585,26 @@ Choose the scope that best fits your needs. For most users, `--scope user` or us
 
 ### Read-Only Mode (Optional)
 
-The DeployHQ MCP Server supports an optional **read-only mode** that can be enabled to prevent deployment creation when using AI assistants.
+**By default, the MCP server allows all operations, including creating deployments.** This is the recommended configuration for most users who want full functionality.
 
-**Default Behavior:**
-- &#9989; All operations work by default (list, get, create deployments)
-- &#9989; Deployments can be created through AI assistants
-- &#9888;&#65039; Consider enabling read-only mode in production environments for extra protection
+For users who want additional protection against accidental deployments, the server includes an **optional read-only mode** that can be enabled to block deployment creation while still allowing read operations.
+
+**Default Behavior (No Configuration Needed):**
+- &#9989; Deployments are **allowed by default**
+- &#9989; All operations work: list projects, get details, and create deployments
+- &#9989; Full functionality out of the box
+
+**When you might want to enable read-only mode:**
+- You want extra protection against accidental deployments via AI
+- You're connecting to production environments and want an additional safety layer
+- You only need read access to monitor deployments
+- You're still testing the integration and want to be cautious
+
+**Important:** Read-only mode is **completely optional**. The server works fully without it.
 
 **Enabling Read-Only Mode:**
 
-If you want to prevent deployments through the MCP server (read-only access), you can enable read-only mode in two ways:
+If you want to prevent deployments through the MCP server, you can enable read-only mode in two ways:
 
 **Method 1: Environment Variable**
 ```json
