Standardize environment variable naming and update documentation

- Update environment variable names to consistent UMBRACO_* pattern:
  - INCLUDE_MANAGEMENT_TOOLS → UMBRACO_INCLUDE_TOOLS
  - EXCLUDE_MANAGEMENT_TOOLS → UMBRACO_EXCLUDE_TOOLS
  - INCLUDE_MANAGEMENT_COLLECTIONS → UMBRACO_INCLUDE_TOOL_COLLECTIONS
  - EXCLUDE_MANAGEMENT_COLLECTIONS → UMBRACO_EXCLUDE_TOOL_COLLECTIONS

- Update all configuration files, tests, and documentation
- Fix TypeScript compilation issue in property-type-test-helper.ts
- Create comprehensive tool collection filtering documentation
- Remove outdated OpenAPI group filtering plan document

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: Phil Whittaker

OPENAPI_GROUP_FILTERING_PLAN.md

@@ -40,8 +40,8 @@ Once you have this information head back into Claude desktop app and head to Set
         "UMBRACO_CLIENT_ID": "umbraco-back-office-mcp",
         "UMBRACO_CLIENT_SECRET": "1234567890",
         "UMBRACO_BASE_URL": "https://localhost:44391",
-        "INCLUDE_MANAGEMENT_COLLECTIONS": "culture,document,media",
-        "EXCLUDE_MANAGEMENT_TOOLS": "delete-document,empty-recycle-bin"
+        "UMBRACO_INCLUDE_TOOL_COLLECTIONS": "culture,document,media",
+        "UMBRACO_EXCLUDE_TOOLS": "delete-document,empty-recycle-bin"
       }
     }
   }
@@ -71,7 +71,7 @@ Or configure environment variables and scope:
 npm install -g @anthropic-ai/claude-code
 
 # Add with environment variables
-claude mcp add umbraco-mcp --env UMBRACO_CLIENT_ID="your-id" --env UMBRACO_CLIENT_SECRET="your-secret" --env UMBRACO_BASE_URL="https://your-domain.com" --env NODE_TLS_REJECT_UNAUTHORIZED="0" --env INCLUDE_MANAGEMENT_COLLECTIONS="culture,document,media" -- npx @umbraco-mcp/umbraco-mcp-cms@alpha
+claude mcp add umbraco-mcp --env UMBRACO_CLIENT_ID="your-id" --env UMBRACO_CLIENT_SECRET="your-secret" --env UMBRACO_BASE_URL="https://your-domain.com" --env NODE_TLS_REJECT_UNAUTHORIZED="0" --env UMBRACO_INCLUDE_TOOL_COLLECTIONS="culture,document,media" -- npx @umbraco-mcp/umbraco-mcp-cms@alpha
 
 # Verify installation
 claude mcp list
@@ -86,7 +86,7 @@ This will add umbraco-mcp to the existing project in the claude.json config file
 <summary>VS Code</summary>
 
 #### Click the button to install:
-[<img src="https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20Server&color=0098FF" alt="Install in VS Code">](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522umbraco-mcp%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522%2540umbraco-mcp%252Fumbraco-mcp-cms%2540alpha%2522%255D%252C%2522env%2522%253A%257B%2522UMBRACO_CLIENT_ID%2522%253A%2522%253CAPI%2520user%2520name%253E%2522%252C%2522UMBRACO_CLIENT_SECRET%2522%253A%2522%253CAPI%2520client%2520secert%253E%2522%252C%2522UMBRACO_BASE_URL%2522%253A%2522https%253A%252F%252F%253Cdomain%253E%2522%252C%2522EXCLUDE_MANAGEMENT_TOOLS%2522%253A%2522%253Ctoolname%253E%252C%253Ctoolname%253E%2522%257D%257D)
+[<img src="https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20Server&color=0098FF" alt="Install in VS Code">](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522umbraco-mcp%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522%2540umbraco-mcp%252Fumbraco-mcp-cms%2540alpha%2522%255D%252C%2522env%2522%253A%257B%2522UMBRACO_CLIENT_ID%2522%253A%2522%253CAPI%2520user%2520name%253E%2522%252C%2522UMBRACO_CLIENT_SECRET%2522%253A%2522%253CAPI%2520client%2520secert%253E%2522%252C%2522UMBRACO_BASE_URL%2522%253A%2522https%253A%252F%252F%253Cdomain%253E%2522%252C%2522UMBRACO_EXCLUDE_TOOLS%2522%253A%2522%253Ctoolname%253E%252C%253Ctoolname%253E%2522%257D%257D)
 
 **Requirements:** VS Code 1.101+ with GitHub Copilot Chat extension installed.
 
@@ -104,8 +104,8 @@ Follow the MCP [install guide](https://code.visualstudio.com/docs/copilot/custom
         "UMBRACO_CLIENT_ID": "<API user name>",
         "UMBRACO_CLIENT_SECRET": "<API client secret>",
         "UMBRACO_BASE_URL": "https://<domain>",
-        "INCLUDE_MANAGEMENT_COLLECTIONS": "<collection>,<collection>",
-        "EXCLUDE_MANAGEMENT_TOOLS": "<toolname>,<toolname>"
+        "UMBRACO_INCLUDE_TOOL_COLLECTIONS": "<collection>,<collection>",
+        "UMBRACO_EXCLUDE_TOOLS": "<toolname>,<toolname>"
       }
     }
   }
@@ -132,8 +132,8 @@ Add the following to the config file and update the env variables.
         "UMBRACO_CLIENT_ID": "<API user name>",
         "UMBRACO_CLIENT_SECRET": "<API client secret>",
         "UMBRACO_BASE_URL": "https://<domain>",
-        "INCLUDE_MANAGEMENT_COLLECTIONS": "<collection>,<collection>",
-        "EXCLUDE_MANAGEMENT_TOOLS": "<toolname>,<toolname>"
+        "UMBRACO_INCLUDE_TOOL_COLLECTIONS": "<collection>,<collection>",
+        "UMBRACO_EXCLUDE_TOOLS": "<toolname>,<toolname>"
       }
     }
   }
@@ -156,26 +156,26 @@ Umbraco API User client secert
 
 Url of the site you want to connect to, it only needs to be the scheme and domain e.g https://<nolink/>example.com
 
-`EXCLUDE_MANAGEMENT_TOOLS`
+`UMBRACO_EXCLUDE_TOOLS`
 
 The allows you to specify tools by name if you wish to exclude them for the usable tools list. This is helpful as some Agents, cant handle so many tools. This is a commma seperated list of tools which can be found below.
 
-`INCLUDE_MANAGEMENT_TOOLS`
+`UMBRACO_INCLUDE_TOOLS`
 
 The allows you to specify tools by name if you wish to include only specific tools in the usable tools list. When specified, only these tools will be available. This is a commma seperated list of tools which can be found below.
 
-`INCLUDE_MANAGEMENT_COLLECTIONS`
+`UMBRACO_INCLUDE_TOOL_COLLECTIONS`
 
 The allows you to specify collections by name if you wish to include only specific collections. When specified, only tools from these collections will be available. This is a commma seperated list of collection names (see tool list below for collection names).
 
-`EXCLUDE_MANAGEMENT_COLLECTIONS`
+`UMBRACO_EXCLUDE_TOOL_COLLECTIONS`
 
 The allows you to specify collections by name if you wish to exclude them from the usable tools list. This is a commma seperated list of collection names (see tool list below for collection names).
 
 
 ##  Umbraco Management API Tools
 
-**Note:** Collection names are shown in brackets for use with `INCLUDE_MANAGEMENT_COLLECTIONS` and `EXCLUDE_MANAGEMENT_COLLECTIONS`.
+**Note:** Collection names are shown in brackets for use with `UMBRACO_INCLUDE_TOOL_COLLECTIONS` and `UMBRACO_EXCLUDE_TOOL_COLLECTIONS`.
 
 <details>
 <summary> View Tool list</summary>

README.md

@@ -5,9 +5,16 @@ This document provides a comprehensive comparison between the available Umbraco
 ## Summary
 
 - **Total API Endpoints**: 393
-- **Implemented Tools**: 187
-- **Coverage**: ~47.6%
-- **Missing Endpoints**: ~206
+- **Implemented Tools**: 269
+- **Coverage**: ~68.4%
+- **Missing Endpoints**: ~124
+
+**Recent Updates:**
+- Added Document Version tools (4 endpoints)
+- Added Stylesheet tools (11 endpoints) 
+- Added Script tools (10 endpoints)
+- Expanded Partial View coverage
+- Enhanced test infrastructure and collection filtering system
 
 ## Coverage by Section
 
@@ -17,6 +24,7 @@ This document provides a comprehensive comparison between the available Umbraco
 - **Dictionary**: ~90% coverage (9/10 endpoints)  
 - **Document Blueprints**: ~85% coverage (6/7 endpoints)
 - **Document Types**: ~88% coverage (22/25 endpoints)
+- **Document Versions**: 100% coverage (4/4 endpoints) *NEW*
 - **Documents**: ~79% coverage (38/48 endpoints)
 - **Languages**: ~85% coverage (6/7 endpoints)
 - **Log Viewer**: ~90% coverage (9/10 endpoints)
@@ -25,9 +33,12 @@ This document provides a comprehensive comparison between the available Umbraco
 - **Member Groups**: ~85% coverage (6/7 endpoints)
 - **Member Types**: ~80% coverage (8/10 endpoints)
 - **Members**: ~83% coverage (5/6 endpoints)
+- **Partial Views**: ~83% coverage (10/12 endpoints) *IMPROVED*
 - **Property Types**: 100% coverage (1/1 endpoints)
 - **Redirects**: 100% coverage (5/5 endpoints)
+- **Scripts**: 100% coverage (10/10 endpoints) *NEW*
 - **Server**: 100% coverage (5/5 endpoints)
+- **Stylesheets**: 100% coverage (11/11 endpoints) *NEW*
 - **Templates**: 100% coverage (10/10 endpoints)
 - **Temporary Files**: 100% coverage (4/4 endpoints)
 - **User Groups**: 100% coverage (8/8 endpoints)
@@ -291,11 +302,11 @@ This document provides a comprehensive comparison between the available Umbraco
 1. **User Management** - Critical for user administration
 2. **Authentication & Security** - Essential for security operations
 3. **Package Management** - Important for deployment and maintenance
-4. **Version Management** - Important for content workflows
+4. ~~**Version Management**~~ - ✅ COMPLETED (Document Versions added)
 
 ### Medium Priority (Development tools)
-1. **Scripting & Views** - Important for developers
-2. **Stylesheets** - Important for theming
+1. ~~**Scripting & Views**~~ - ✅ COMPLETED (Scripts and Partial Views added)
+2. ~~**Stylesheets**~~ - ✅ COMPLETED (100% coverage achieved)
 3. **System Operations** - Important for maintenance
 
 ### Low Priority (Specialized features)
@@ -305,11 +316,21 @@ This document provides a comprehensive comparison between the available Umbraco
 
 ## Implementation Notes
 
-Most missing endpoints fall into these categories:
-- Advanced administrative functions
-- Developer-focused tools
-- System maintenance operations
+**Recent Achievements (68.4% coverage):**
+- ✅ **Document Versions** - Complete rollback and cleanup functionality
+- ✅ **Stylesheets** - Full CRUD operations and tree navigation
+- ✅ **Scripts** - Complete script file management
+- ✅ **Enhanced Test Infrastructure** - Comprehensive testing patterns and collection filtering
+- ✅ **Improved Coverage** - Significant jump from 47.6% to 68.4%
+
+**Remaining gaps focus on:**
+- Advanced administrative functions (User management, Security)
+- System maintenance operations (Packages, Health checks)
 - Import/export functionality
-- Advanced content workflows
+- Specialized features (Relations, Tags, Static files)
 
-The current MCP implementation covers the core content management workflows very well, with strong coverage of the primary content, media, and type management operations that most users need day-to-day.
+The current MCP implementation now provides excellent coverage of the core content management workflows, with strong support for:
+- All content types (Documents, Media, Members)
+- Development workflow (Scripts, Stylesheets, Templates, Partial Views)
+- Content versioning and rollback capabilities
+- Comprehensive testing and quality assurance

docs/analysis/UNSUPPORTED_ENDPOINTS.md

@@ -504,15 +504,24 @@
 ## Summary Statistics
 
 **Total Endpoints:** 393
+**MCP Tools Implemented:** 269
+**Coverage:** 68.4%
 
 **Categories:** 37
 
 **Major Functional Areas:**
-- **Content Management:** Documents (48 endpoints), Media (34 endpoints), Templates (10 endpoints)
+- **Content Management:** Documents (48 endpoints), Document Versions (4 endpoints), Media (34 endpoints), Templates (10 endpoints)
 - **Content Types:** Document Types (25 endpoints), Media Types (25 endpoints), Data Types (20 endpoints)
 - **User Management:** Users (36 endpoints), User Groups (8 endpoints), Members (10 endpoints)
-- **Development:** Scripts (10 endpoints), Stylesheets (10 endpoints), Partial Views (12 endpoints)
+- **Development:** Scripts (10 endpoints), Stylesheets (11 endpoints), Partial Views (12 endpoints)
 - **System Management:** Server (5 endpoints), Security (4 endpoints), Health Check (4 endpoints)
 - **Configuration:** Various configuration endpoints across categories
 - **Tree Operations:** Tree navigation endpoints for hierarchical content
-- **Search & Filtering:** Search and filter endpoints across content types
+- **Search & Filtering:** Search and filter endpoints across content types
+
+**Recent Additions:**
+- Document Version management (rollback, cleanup)
+- Complete Stylesheet file management
+- Full Script file operations
+- Enhanced collection filtering system
+- Comprehensive testing infrastructure