mcp-wordpress 2.10.0 → 2.10.2

package/docs/ARCHITECTURE.md

@@ -14,9 +14,9 @@
 
 ## System Overview
 
-The MCP WordPress Server is a TypeScript-based Model Context Protocol (MCP) server that provides AI tools
-with comprehensive WordPress management capabilities. It follows a modular, security-first architecture with
-comprehensive validation and performance optimization.
+The MCP WordPress Server is a TypeScript-based Model Context Protocol (MCP) server that provides AI tools with
+comprehensive WordPress management capabilities. It follows a modular, security-first architecture with comprehensive
+validation and performance optimization.
 
 ### Key Architectural Principles
 
@@ -222,7 +222,7 @@ class MCPWordPressServer {
   private wordpressClients: Map<string, WordPressClient>;
   private toolRegistry: ToolRegistry;
   private connectionTester: ConnectionTester;
-  
+
   // Server lifecycle management
   // Tool registration and routing
   // Multi-site client management
@@ -246,7 +246,7 @@ Manages tool discovery, registration, and request routing:
 class ToolRegistry {
   private tools: Map<string, ToolHandler>;
   private toolClasses: ToolClass[];
-  
+
   // Dynamic tool discovery
   // Tool metadata management
   // Request routing
@@ -270,7 +270,7 @@ Modular HTTP client for WordPress REST API:
 class WordPressClient {
   private authManager: AuthenticationManager;
   private requestManager: RequestManager;
-  
+
   // High-level WordPress operations
   // Manager coordination
   // Configuration management
@@ -307,7 +307,7 @@ class PostTools {
   public getTools(): MCPTool[] {
     // Tool definitions
   }
-  
+
   public async handleListPosts(client: WordPressClient, params: PostQueryParams): Promise<string> {
     // Implementation with validation, processing, and formatting
   }
@@ -734,11 +734,11 @@ class WordPressClient {
   constructor(
     private authManager: AuthenticationManager,
     private requestManager: RequestManager,
-    private cacheManager: CacheManager
+    private cacheManager: CacheManager,
   ) {}
-  
+
   async getPosts(params: PostQueryParams): Promise<Post[]> {
-    return this.requestManager.get('/posts', params);
+    return this.requestManager.get("/posts", params);
   }
 }
 ```
@@ -771,7 +771,7 @@ class ClientFactory {
     const authManager = new AuthenticationManager(config.auth);
     const requestManager = new RequestManager(config.request);
     const cacheManager = new CacheManager(config.cache);
-    
+
     return new WordPressClient(authManager, requestManager, cacheManager);
   }
 }
@@ -782,13 +782,13 @@ class ClientFactory {
 ```typescript
 class PerformanceMonitor {
   private observers: PerformanceObserver[] = [];
-  
+
   subscribe(observer: PerformanceObserver): void {
     this.observers.push(observer);
   }
-  
+
   notify(metric: PerformanceMetric): void {
-    this.observers.forEach(observer => observer.update(metric));
+    this.observers.forEach((observer) => observer.update(metric));
   }
 }
 ```
@@ -802,7 +802,7 @@ abstract class BaseTool {
     const result = await this.executeOperation(client, params);
     return this.formatResponse(result);
   }
-  
+
   protected abstract validateParameters(params: any): void;
   protected abstract executeOperation(client: WordPressClient, params: any): Promise<any>;
   protected abstract formatResponse(result: any): string;
@@ -845,6 +845,6 @@ abstract class BaseTool {
 
 ---
 
-*This architecture documentation is maintained by the development team. Last updated: 2024-01-15*
+_This architecture documentation is maintained by the development team. Last updated: 2024-01-15_
 
-*For architectural questions, visit our [GitHub Discussions](https://github.com/docdyhr/mcp-wordpress/discussions)*
+_For architectural questions, visit our [GitHub Discussions](https://github.com/docdyhr/mcp-wordpress/discussions)_

package/docs/BADGE_UPDATES.md

@@ -8,7 +8,7 @@ The README.md contains dynamic badges showing:
 
 - Test results (passed/total count)
 - Line coverage percentage
-- Branch coverage percentage  
+- Branch coverage percentage
 - Function coverage percentage
 
 These badges should be updated when test counts or coverage metrics change significantly.
@@ -32,7 +32,7 @@ Replace the badge URLs in README.md with the new ones from the script output.
 **Badge Sections to Update:**
 
 - Line 19: `[![Line Coverage](...)]`
-- Line 20: `[![Branch Coverage](...)]`  
+- Line 20: `[![Branch Coverage](...)]`
 - Line 21: `[![Function Coverage](...)]`
 - Line 22: `[![Test Results](...)]`
 
@@ -40,13 +40,13 @@ Replace the badge URLs in README.md with the new ones from the script output.
 
 The script automatically applies colors based on coverage levels:
 
-| Coverage % | Color | Badge Color Code |
-|-----------|-------|------------------|
-| ≥ 70% | Bright Green | `brightgreen` |
-| ≥ 50% | Green | `green` |
-| ≥ 30% | Yellow | `yellow` |
-| ≥ 20% | Orange | `orange` |
-| < 20% | Red | `red` |
+| Coverage % | Color        | Badge Color Code |
+| ---------- | ------------ | ---------------- |
+| ≥ 70%      | Bright Green | `brightgreen`    |
+| ≥ 50%      | Green        | `green`          |
+| ≥ 30%      | Yellow       | `yellow`         |
+| ≥ 20%      | Orange       | `orange`         |
+| < 20%      | Red          | `red`            |
 
 **Test Results:**
 
@@ -79,7 +79,7 @@ The extraction script:
 Future improvements will include:
 
 1. **Automated Badge Updates**: GitHub Actions workflow to update badges after successful CI runs
-2. **Coverage Reporting**: Enhanced coverage collection from TypeScript sources  
+2. **Coverage Reporting**: Enhanced coverage collection from TypeScript sources
 3. **Historical Tracking**: Track coverage trends over time
 4. **PR Integration**: Show coverage diff in pull requests
 
@@ -125,7 +125,7 @@ Test badge rendering by visiting the URLs directly:
 # Test line coverage badge
 curl -I "https://img.shields.io/badge/lines%20coverage-30.97%25-yellow?logo=jest&logoColor=white"
 
-# Test test results badge  
+# Test test results badge
 curl -I "https://img.shields.io/badge/tests-399%2F404%20passing-yellow?logo=checkmarx&logoColor=white"
 ```
 

package/docs/CACHING.md

@@ -285,10 +285,12 @@ wp_cache_clear --site="site2" --pattern="posts"  # Clear site2 posts only
 ### **Poor Cache Performance**
 
 1. **Monitor hit rates:**
+
    - Good: >60% hit rate after warm-up
    - Poor: <30% hit rate indicates issues
 
 2. **Check TTL settings:**
+
    - Too short: Frequent cache misses
    - Too long: Stale data issues
 

package/docs/CI_CD_IMPROVEMENTS.md

@@ -2,8 +2,8 @@
 
 ## 🎯 Overview
 
-This document outlines the comprehensive improvements made to the CI/CD pipeline for the MCP WordPress project.
-These changes enhance reliability, security, performance, and maintainability.
+This document outlines the comprehensive improvements made to the CI/CD pipeline for the MCP WordPress project. These
+changes enhance reliability, security, performance, and maintainability.
 
 ## ✅ Improvements Implemented
 
@@ -96,7 +96,7 @@ npm run check:ci
 **Includes:**
 
 - TypeScript type checking
-- ESLint code linting  
+- ESLint code linting
 - Test coverage analysis
 
 ### 3. **CI/CD Health Check Workflow**
@@ -147,21 +147,25 @@ npm run test:coverage
 ## 🎯 Key Benefits
 
 1. **🛡️ Increased Reliability**
+
    - Better error handling prevents cascading failures
    - Timeouts prevent hanging builds
    - Improved retry logic for transient failures
 
 2. **⚡ Enhanced Performance**
+
    - Intelligent caching reduces build times
    - Parallel execution optimized
    - Artifact management streamlined
 
 3. **🔒 Improved Security**
+
    - Updated security scanners
    - Better secret handling validation
    - Enhanced security monitoring
 
 4. **📈 Better Monitoring**
+
    - Automated health checks
    - Comprehensive validation scripts
    - Actionable insights and recommendations
@@ -187,5 +191,4 @@ npm run test:coverage
 
 ---
 
-**Last Updated**: August 8, 2025  
-**Status**: ✅ Complete - Ready for Production
+**Last Updated**: August 8, 2025 **Status**: ✅ Complete - Ready for Production

package/docs/CONFIGURATION.md

@@ -6,12 +6,12 @@ Complete configuration reference for MCP WordPress Server supporting single-site
 
 The MCP WordPress Server supports flexible configuration through multiple methods:
 
-| Method | Best For | Configuration File |
-|--------|----------|--------------------|
-| **Environment Variables** | Single site, development | `.env` |
-| **Multi-Site JSON** | Multiple sites, production | `mcp-wordpress.config.json` |
-| **Claude Desktop** | Desktop integration | `claude_desktop_config.json` |
-| **DXT Extension** | Easy desktop setup | Built-in UI |
+| Method                    | Best For                   | Configuration File           |
+| ------------------------- | -------------------------- | ---------------------------- |
+| **Environment Variables** | Single site, development   | `.env`                       |
+| **Multi-Site JSON**       | Multiple sites, production | `mcp-wordpress.config.json`  |
+| **Claude Desktop**        | Desktop integration        | `claude_desktop_config.json` |
+| **DXT Extension**         | Easy desktop setup         | Built-in UI                  |
 
 ## 🌐 Single-Site Configuration
 
@@ -47,33 +47,33 @@ RATE_LIMIT_WINDOW=60000
 
 #### Required Variables
 
-| Variable | Required | Description | Example |
-|----------|----------|-------------|---------|
-| `WORDPRESS_SITE_URL` | Yes | Full WordPress site URL | `https://blog.example.com` |
-| `WORDPRESS_USERNAME` | Yes | WordPress username | `admin` |
-| `WORDPRESS_APP_PASSWORD` | Yes | WordPress application password | `AbCd EfGh IjKl MnOp QrSt UvWx` |
+| Variable                 | Required | Description                    | Example                         |
+| ------------------------ | -------- | ------------------------------ | ------------------------------- |
+| `WORDPRESS_SITE_URL`     | Yes      | Full WordPress site URL        | `https://blog.example.com`      |
+| `WORDPRESS_USERNAME`     | Yes      | WordPress username             | `admin`                         |
+| `WORDPRESS_APP_PASSWORD` | Yes      | WordPress application password | `AbCd EfGh IjKl MnOp QrSt UvWx` |
 
 #### Authentication Variables
 
-| Variable | Default | Description | Options |
-|----------|---------|-------------|---------|
+| Variable                | Default        | Description           | Options                                   |
+| ----------------------- | -------------- | --------------------- | ----------------------------------------- |
 | `WORDPRESS_AUTH_METHOD` | `app-password` | Authentication method | `app-password`, `jwt`, `basic`, `api-key` |
 
 #### Runtime Variables
 
-| Variable | Default | Description | Options |
-|----------|---------|-------------|---------|
-| `NODE_ENV` | `production` | Runtime environment | `development`, `production`, `test`, `dxt` |
-| `DEBUG` | `false` | Enable debug logging | `true`, `false` |
-| `LOG_LEVEL` | `info` | Logging verbosity | `error`, `warn`, `info`, `debug` |
+| Variable    | Default      | Description          | Options                                    |
+| ----------- | ------------ | -------------------- | ------------------------------------------ |
+| `NODE_ENV`  | `production` | Runtime environment  | `development`, `production`, `test`, `dxt` |
+| `DEBUG`     | `false`      | Enable debug logging | `true`, `false`                            |
+| `LOG_LEVEL` | `info`       | Logging verbosity    | `error`, `warn`, `info`, `debug`           |
 
 #### Performance Variables
 
-| Variable | Default | Description | Range |
-|----------|---------|-------------|-------|
-| `DISABLE_CACHE` | `false` | Disable caching system | `true`, `false` |
-| `CACHE_TTL` | `300` | Cache time-to-live (seconds) | `60-3600` |
-| `MAX_CACHE_SIZE` | `1000` | Maximum cache entries | `100-10000` |
+| Variable         | Default | Description                  | Range           |
+| ---------------- | ------- | ---------------------------- | --------------- |
+| `DISABLE_CACHE`  | `false` | Disable caching system       | `true`, `false` |
+| `CACHE_TTL`      | `300`   | Cache time-to-live (seconds) | `60-3600`       |
+| `MAX_CACHE_SIZE` | `1000`  | Maximum cache entries        | `100-10000`     |
 
 ## 🏢 Multi-Site Configuration
 
@@ -86,7 +86,7 @@ Create `mcp-wordpress.config.json` in your project root:
   "sites": [
     {
       "id": "main-site",
-      "name": "Main WordPress Site", 
+      "name": "Main WordPress Site",
       "config": {
         "WORDPRESS_SITE_URL": "https://main-site.com",
         "WORDPRESS_USERNAME": "admin",
@@ -98,7 +98,7 @@ Create `mcp-wordpress.config.json` in your project root:
       "id": "client-blog",
       "name": "Client Blog",
       "config": {
-        "WORDPRESS_SITE_URL": "https://client-blog.com", 
+        "WORDPRESS_SITE_URL": "https://client-blog.com",
         "WORDPRESS_USERNAME": "editor",
         "WORDPRESS_APP_PASSWORD": "yyyy yyyy yyyy yyyy yyyy yyyy",
         "WORDPRESS_AUTH_METHOD": "jwt"
@@ -121,14 +121,17 @@ Create `mcp-wordpress.config.json` in your project root:
 ### Multi-Site Configuration Rules
 
 #### Site Identification
+
 - **`id`**: Unique identifier (alphanumeric, hyphens, underscores only)
 - **`name`**: Human-readable name for documentation
 - **Maximum sites**: 50 sites per configuration
 
 #### Uniqueness Requirements
+
 All of these must be unique across all sites:
+
 - Site IDs
-- Site names  
+- Site names
 - WordPress site URLs
 
 #### Site-Specific Usage
@@ -146,6 +149,7 @@ wp_get_site_settings --site="dev-site"
 ### Multi-Site Example Configurations
 
 #### Agency Setup
+
 ```json
 {
   "sites": [
@@ -159,7 +163,7 @@ wp_get_site_settings --site="dev-site"
       }
     },
     {
-      "id": "client-a", 
+      "id": "client-a",
       "name": "Client A Blog",
       "config": {
         "WORDPRESS_SITE_URL": "https://clienta.com/blog",
@@ -172,7 +176,7 @@ wp_get_site_settings --site="dev-site"
       "name": "Client B E-commerce",
       "config": {
         "WORDPRESS_SITE_URL": "https://clientb-shop.com",
-        "WORDPRESS_USERNAME": "shop_manager", 
+        "WORDPRESS_USERNAME": "shop_manager",
         "WORDPRESS_APP_PASSWORD": "zzzz zzzz zzzz zzzz zzzz zzzz"
       }
     }
@@ -181,6 +185,7 @@ wp_get_site_settings --site="dev-site"
 ```
 
 #### Development Workflow
+
 ```json
 {
   "sites": [
@@ -195,7 +200,7 @@ wp_get_site_settings --site="dev-site"
     },
     {
       "id": "staging",
-      "name": "Staging Environment", 
+      "name": "Staging Environment",
       "config": {
         "WORDPRESS_SITE_URL": "https://staging.mysite.com",
         "WORDPRESS_USERNAME": "admin",
@@ -221,33 +226,38 @@ wp_get_site_settings --site="dev-site"
 ### Application Passwords (Recommended)
 
 **WordPress Setup:**
+
 1. **Enable Application Passwords** (WordPress 5.6+)
 2. **Generate Password**: Users → Profile → Application Passwords
 3. **Copy Password**: Exact format with spaces
 
 **Configuration:**
+
 ```json
 {
   "WORDPRESS_AUTH_METHOD": "app-password",
-  "WORDPRESS_USERNAME": "your-username", 
+  "WORDPRESS_USERNAME": "your-username",
   "WORDPRESS_APP_PASSWORD": "AbCd EfGh IjKl MnOp QrSt UvWx"
 }
 ```
 
 **Security Benefits:**
+
 - ✅ Revocable without changing main password
-- ✅ Scoped permissions 
+- ✅ Scoped permissions
 - ✅ Audit trail
 - ✅ WordPress native support
 
 ### JWT Authentication
 
 **WordPress Setup:**
+
 1. **Install JWT Plugin**: JWT Authentication for WP-API
 2. **Configure JWT Secret** in wp-config.php
 3. **Get JWT Token** via login endpoint
 
 **Configuration:**
+
 ```json
 {
   "WORDPRESS_AUTH_METHOD": "jwt",
@@ -257,6 +267,7 @@ wp_get_site_settings --site="dev-site"
 ```
 
 **WordPress JWT Setup:**
+
 ```php
 // wp-config.php
 define('JWT_AUTH_SECRET_KEY', 'your-secret-key');
@@ -268,6 +279,7 @@ define('JWT_AUTH_CORS_ENABLE', true);
 **⚠️ Development Only - Not recommended for production**
 
 **Configuration:**
+
 ```json
 {
   "WORDPRESS_AUTH_METHOD": "basic",
@@ -279,15 +291,17 @@ define('JWT_AUTH_CORS_ENABLE', true);
 ### API Key Authentication
 
 **WordPress Setup:**
-1. **Install API Key Plugin** 
+
+1. **Install API Key Plugin**
 2. **Generate API Key** in WordPress admin
 3. **Configure Key Permissions**
 
 **Configuration:**
+
 ```json
 {
   "WORDPRESS_AUTH_METHOD": "api-key",
-  "WORDPRESS_USERNAME": "your-username", 
+  "WORDPRESS_USERNAME": "your-username",
   "WORDPRESS_APP_PASSWORD": "your-api-key"
 }
 ```
@@ -306,7 +320,7 @@ Add to `claude_desktop_config.json`:
       "args": ["-y", "mcp-wordpress"],
       "env": {
         "WORDPRESS_SITE_URL": "https://your-site.com",
-        "WORDPRESS_USERNAME": "your-username", 
+        "WORDPRESS_USERNAME": "your-username",
         "WORDPRESS_APP_PASSWORD": "your-app-password",
         "WORDPRESS_AUTH_METHOD": "app-password"
       }
@@ -340,7 +354,7 @@ For multi-site setups, create a configuration file and reference it:
 {
   "mcpServers": {
     "mcp-wordpress": {
-      "command": "npx", 
+      "command": "npx",
       "args": ["-y", "mcp-wordpress"],
       "cwd": "/path/to/your/config/directory"
     }
@@ -365,7 +379,7 @@ docker run -d \
 ### Docker Compose
 
 ```yaml
-version: '3.8'
+version: "3.8"
 services:
   mcp-wordpress:
     image: docdyhr/mcp-wordpress:latest
@@ -383,7 +397,7 @@ services:
 ### Multi-Site with Docker
 
 ```yaml
-version: '3.8'
+version: "3.8"
 services:
   mcp-wordpress:
     image: docdyhr/mcp-wordpress:latest
@@ -397,6 +411,7 @@ services:
 ### Performance Tuning
 
 #### Cache Configuration
+
 ```bash
 # Optimize for high-traffic sites
 CACHE_TTL=600              # 10 minutes
@@ -404,18 +419,19 @@ MAX_CACHE_SIZE=5000        # 5000 entries
 CACHE_CLEANUP_INTERVAL=300 # 5 minutes
 
 # Optimize for low-memory environments
-CACHE_TTL=120              # 2 minutes  
+CACHE_TTL=120              # 2 minutes
 MAX_CACHE_SIZE=100         # 100 entries
 DISABLE_CACHE=false        # Keep basic caching
 ```
 
 #### Rate Limiting
+
 ```bash
 # Conservative limits
 RATE_LIMIT_REQUESTS=100    # 100 requests
 RATE_LIMIT_WINDOW=60000    # per minute
 
-# Aggressive limits  
+# Aggressive limits
 RATE_LIMIT_REQUESTS=1000   # 1000 requests
 RATE_LIMIT_WINDOW=60000    # per minute
 ```
@@ -423,6 +439,7 @@ RATE_LIMIT_WINDOW=60000    # per minute
 ### Security Hardening
 
 #### Network Security
+
 ```bash
 # Bind to specific interface (Docker/production)
 BIND_ADDRESS=127.0.0.1
@@ -435,6 +452,7 @@ FORCE_HTTPS=true
 ```
 
 #### Authentication Security
+
 ```bash
 # Strengthen authentication
 AUTH_TIMEOUT=300           # 5 minute auth timeout
@@ -445,6 +463,7 @@ AUTH_LOCKOUT_DURATION=900  # 15 minute lockout
 ### Monitoring Configuration
 
 #### Logging
+
 ```bash
 # Development logging
 NODE_ENV=development
@@ -452,13 +471,14 @@ DEBUG=true
 LOG_LEVEL=debug
 
 # Production logging
-NODE_ENV=production  
+NODE_ENV=production
 DEBUG=false
 LOG_LEVEL=warn
 LOG_FILE=/var/log/mcp-wordpress.log
 ```
 
 #### Performance Monitoring
+
 ```bash
 # Enable performance tracking
 ENABLE_PERFORMANCE_MONITORING=true
@@ -487,19 +507,21 @@ npm run config:show
 ### Common Validation Errors
 
 #### 1. Invalid URL Format
+
 ```bash
 # ❌ Common mistakes
 WORDPRESS_SITE_URL=mysite.com           # Missing protocol
 WORDPRESS_SITE_URL=https://mysite.com/  # Trailing slash
 WORDPRESS_SITE_URL=http://localhost     # Missing port for local
 
-# ✅ Correct formats  
+# ✅ Correct formats
 WORDPRESS_SITE_URL=https://mysite.com
 WORDPRESS_SITE_URL=http://localhost:8080
 WORDPRESS_SITE_URL=https://blog.mysite.com
 ```
 
 #### 2. Invalid Authentication Method
+
 ```bash
 # ❌ Invalid
 WORDPRESS_AUTH_METHOD=password          # Not supported
@@ -512,18 +534,19 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
 ```
 
 #### 3. Multi-Site Configuration Errors
+
 ```bash
 # ❌ Duplicate site IDs
 {"id": "site1", ...}
 {"id": "site1", ...}  # Error: duplicate ID
 
-# ❌ Invalid site ID characters  
+# ❌ Invalid site ID characters
 {"id": "site 1", ...}      # Spaces not allowed
 {"id": "site@1", ...}      # Special chars not allowed
 
 # ✅ Valid site IDs
 {"id": "site-1", ...}      # Hyphens OK
-{"id": "site_1", ...}      # Underscores OK  
+{"id": "site_1", ...}      # Underscores OK
 {"id": "site1", ...}       # Alphanumeric OK
 ```
 
@@ -532,11 +555,13 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
 ### From Single-Site to Multi-Site
 
 1. **Backup Current Configuration**
+
    ```bash
    cp .env .env.backup
    ```
 
 2. **Create Multi-Site Config**
+
    ```json
    {
      "sites": [
@@ -545,7 +570,7 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
          "name": "Main Site",
          "config": {
            "WORDPRESS_SITE_URL": "your-current-url",
-           "WORDPRESS_USERNAME": "your-current-username", 
+           "WORDPRESS_USERNAME": "your-current-username",
            "WORDPRESS_APP_PASSWORD": "your-current-password"
          }
        }
@@ -570,6 +595,7 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
 
 1. **Choose Primary Site** from multi-site config
 2. **Extract Configuration**
+
    ```bash
    # From mcp-wordpress.config.json site
    WORDPRESS_SITE_URL=https://primary-site.com
@@ -584,6 +610,7 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
 ### Credential Management
 
 1. **Never commit credentials** to version control
+
    ```bash
    # Add to .gitignore
    .env
@@ -599,6 +626,7 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
 ### Configuration Security
 
 1. **File Permissions**
+
    ```bash
    # Secure configuration files
    chmod 600 .env
@@ -606,10 +634,11 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
    ```
 
 2. **Environment Isolation**
+
    ```bash
    # Separate configs for different environments
    .env.development
-   .env.staging  
+   .env.staging
    .env.production
    ```
 
@@ -624,6 +653,7 @@ WORDPRESS_AUTH_METHOD=api-key           # With plugin
 ### Example Templates
 
 Complete configuration examples are available in:
+
 - **[Single-Site Template](../examples/basic-setup/.env.example)**
 - **[Multi-Site Template](../examples/multi-site/mcp-wordpress.config.json.example)**
 - **[Docker Template](../examples/docker/docker-compose.yml)**
@@ -657,4 +687,4 @@ CACHE_TTL=60
 ---
 
 **Need help with configuration?** Check the [Troubleshooting Guide](TROUBLESHOOTING.md) or
-[open an issue](https://github.com/docdyhr/mcp-wordpress/issues/new) for assistance.
+[open an issue](https://github.com/docdyhr/mcp-wordpress/issues/new) for assistance.