Update README and ignored endpoints documentation

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

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

Author: Phil Whittaker

README.md

@@ -1,7 +1,7 @@
 # Umbraco MCP ![GitHub License](https://img.shields.io/github/license/umbraco/Umbraco-CMS-MCP-Dev?style=plastic&link=https%3A%2F%2Fgithub.com%2Fumbraco%2FUmbraco-CMS-MCP-Dev%2Fblob%2Fmain%2FLICENSE)
 
 An MCP (Model Context Protocol) server for [Umbraco CMS](https://umbraco.com/)
-it provides access to key parts of the Management API enabling you to do back office tasks with your agent.
+it provides developer access to the majority of the Management API enabling you to complete most back office tasks with your agent that you can accomplish using the UI.
 
 ## Intro
 
@@ -29,6 +29,7 @@ Start up your Umbraco instance (currently working with version **15.latest**) an
 
 Once you have this information head back into Claude desktop app and head to Settings > Developer > Edit Config. Open the json file in a text editor of your choice and add the below, replacing the `UMBRACO_CLIENT_ID`, `UMBRACO_CLIENT_SECRET` and `UMBRACO_BASE_URL` with your local connection information. The addition of the `NODE_TLS_REJECT_UNAUTHORIZED` env flag is to allow Claude to connect to the MCP using a self-signed cert.
 
+
 ```
 {
   "mcpServers": {
@@ -141,21 +142,53 @@ Add the following to the config file and update the env variables.
 ```
 </details>
 
-
-### Configuration Environment Variables
+### Authentication Configuration Keys
 
 `UMBRACO_CLIENT_ID`
 
 Umbraco API User name
 
-`UMBRACO_CLIENT_SECRET` 
-
+`UMBRACO_CLIENT_SECRET`
 Umbraco API User client secert
 
 `UMBRACO_BASE_URL`
 
 Url of the site you want to connect to, it only needs to be the scheme and domain e.g https://<nolink/>example.com
 
+## API Coverage
+
+This MCP server provides **comprehensive coverage** of the Umbraco Management API. We have achieved **full parity** with all applicable endpoints, implementing tools for every operational endpoint suitable for AI-assisted content management.
+
+### Implementation Status
+
+**✅ Implemented:** All 36 tool collections covering operational endpoints
+- Content management (Documents, Media, Members)
+- Configuration (Document Types, Media Types, Data Types)
+- System management (Templates, Scripts, Stylesheets)
+- User administration (Users, User Groups, Permissions)
+- Advanced features (Webhooks, Relations, Health Checks)
+
+**⚠️ Intentionally Excluded:** 69 endpoints across 14 categories
+
+Certain endpoints are intentionally not implemented due to security, complexity, or contextual concerns. For a detailed breakdown of excluded endpoints and the rationale behind each exclusion, see [Ignored Endpoints Documentation](./docs/analysis/IGNORED_ENDPOINTS.md).
+
+### Excluded Categories Summary
+
+- **User Management (22 endpoints)** - User creation/deletion, password operations, 2FA management, and client credentials pose significant security risks
+- **User Group Membership (3 endpoints)** - Permission escalation risks from AI-driven group membership changes
+- **Security Operations (4 endpoints)** - Password reset workflows require email verification and user interaction
+- **Import/Export (9 endpoints)** - Complex file operations better handled through the Umbraco UI
+- **Package Management (9 endpoints)** - Package creation and migration involve system-wide changes
+- **Cache Operations (3 endpoints)** - Cache rebuild can impact system performance
+- **Telemetry (3 endpoints)** - System telemetry configuration and data collection
+- **Install/Upgrade (5 endpoints)** - One-time system setup and upgrade operations
+- **Preview/Profiling (4 endpoints)** - Frontend-specific debugging functionality
+- **Other (7 endpoints)** - Internal system functionality, oEmbed, dynamic roots, object types
+
+For a comprehensive source code analysis validating these exclusions, see [Endpoint Exclusion Review](./docs/analysis/ENDPOINT_EXCLUSION_REVIEW.md).
+
+### Configuration Environment Variables
+
 `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.
@@ -173,7 +206,7 @@ The allows you to specify collections by name if you wish to include only specif
 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
+### Tool Collections
 
 **Note:** Collection names are shown in brackets for use with `UMBRACO_INCLUDE_TOOL_COLLECTIONS` and `UMBRACO_EXCLUDE_TOOL_COLLECTIONS`.
 

docs/analysis/IGNORED_ENDPOINTS.md

@@ -139,9 +139,6 @@ Security endpoints are excluded because:
 
 Telemetry endpoints are excluded because:
 1. System telemetry data may contain sensitive system information
-2. Telemetry configuration changes could affect system monitoring and analytics
-3. Data collection settings raise privacy concerns and should be managed through the UI
-4. Automated modification of telemetry settings could impact system diagnostics
 
 User Group membership endpoints are excluded because:
 1. These operations present severe permission escalation risks
@@ -153,7 +150,6 @@ PublishedCache endpoints are excluded because:
 1. Cache rebuild operations can significantly impact system performance and should be carefully timed
 2. Cache operations can affect site availability and user experience during execution
 3. Cache rebuild status monitoring could expose sensitive system performance information
-4. These operations require careful consideration of timing and system load and should be managed through the Umbraco UI
 
 Upgrade endpoints are excluded because:
 1. System upgrade operations involve critical system modifications that could break the installation
@@ -182,22 +178,15 @@ Preview endpoints are excluded because:
 1. Content preview functionality is designed for frontend website display and user interface interactions
 2. Preview operations are primarily used for content editors to see how content will appear on the website
 3. These operations are frontend-specific and not relevant for automated data management through MCP
-4. Preview creation and deletion are temporary UI-focused operations that have no use case in the MCP context
 
 Oembed endpoints are excluded because:
-1. oEmbed functionality is used for embedding external media content (videos, social media posts) into web pages
+1. oEmbed functionality is used for embedding external media content (videos, social media posts) into rich text editor
 2. This is primarily a frontend feature for content display and presentation
-3. oEmbed queries are typically used by content editors when creating web content, not for automated data management
-4. This frontend-specific functionality has no relevant use case in the MCP context
 
 Object endpoints are excluded because:
 1. Object type enumeration provides internal system metadata about Umbraco's object structure
 2. This information is primarily used by the Umbraco backend for internal operations and UI generation
-3. Object type data would be confusing and not actionable for AI assistants working with content
-4. This internal system functionality has no practical use case for MCP operations
 
 Dynamic endpoints are excluded because:
 1. Dynamic root functionality is an advanced configuration feature for creating custom content tree structures
-2. These operations involve complex system configuration that requires deep understanding of Umbraco architecture
-3. Dynamic root configuration is typically performed by experienced developers during system setup
-4. This advanced configuration functionality is not suitable for automated AI operations and could cause system instability if misused
+2. These operations are better compled using the UI