MCP WordPress Server

# DXT Package Fix Summary **Date**: 2025-10-08 **Version**: 2.10.2 **Status**: ✅ **FIXED AND REBUILT** --- ## Issues Identified ### 1. Outdated Version Number **Problem**: Manifest showed v2.6.3 instead of current v2.10.2 **Impact**: Users saw outdated version information **Status**: ✅ **FIXED** ### 2. Misleading Multi-Site Documentation **Problem**: Manifest described "multi-site support" but DXT only supports single-site **Impact**: Users confused about capabilities **Status**: ✅ **FIXED** ### 3. Multi-Site Management Prompt Included **Problem**: Manifest included `multi_site_management` prompt that doesn't work in DXT mode **Impact**: Users prompted to use unavailable features **Status**: ✅ **FIXED** ### 4. Unclear DXT Entry Logging **Problem**: Entry point logged `MULTI_SITE_MODE` which isn't relevant for DXT **Impact**: Confusing debug output **Status**: ✅ **FIXED** --- ## Changes Made ### File: `dxt/manifest.json` #### Version Update (Line 5) ```diff - "version": "2.6.3", + "version": "2.10.2", ``` #### Description Clarification (Line 6) ```diff - "description": "Comprehensive WordPress management through 59 MCP tools with multi-site support, performance monitoring, and intelligent caching", + "description": "Comprehensive WordPress management through 59 MCP tools with performance monitoring and intelligent caching. Note: DXT installation supports single-site mode. For multi-site support, use NPM installation.", ``` #### Long Description Update (Line 7) Added notice at top: ```markdown **Note**: DXT installation configures a single WordPress site. For managing multiple WordPress sites simultaneously, install via NPM (`npm install -g mcp-wordpress`) and use `mcp-wordpress.config.json`. ``` Updated key features: ```diff - **Multi-Site Support** - Manage multiple WordPress sites from one configuration + **DXT Mode**: Single-site configuration through Claude Desktop UI + **NPM Mode**: Multi-site support via JSON configuration file ``` Updated use cases: ```diff - Multi-site WordPress administration + WordPress site administration ``` #### Removed Multi-Site Prompt (Lines 187-192) ```diff - { - "name": "multi_site_management", - "description": "Multi-site WordPress administration workflow...", - ... - } ``` **Result**: Only 3 prompts remain: - `setup_wordpress` - `content_management` - `performance_optimization` ### File: `src/dxt-entry.ts` #### Updated Debug Logging (Lines 12-19) ```diff - logger.debug("DXT entry point starting..."); + logger.debug("DXT entry point starting (Single-Site Mode)..."); logger.debug(`Current working directory: ${process.cwd()}`); logger.debug(`__dirname equivalent: ${import.meta.url}`); logger.debug("Environment variables passed from DXT:"); - logger.debug(` MULTI_SITE_MODE: ${process.env.MULTI_SITE_MODE ? "SET" : "NOT SET"}`); logger.debug(` WORDPRESS_SITE_URL: ${process.env.WORDPRESS_SITE_URL ? "SET" : "NOT SET"}`); logger.debug(` WORDPRESS_USERNAME: ${process.env.WORDPRESS_USERNAME ? "SET" : "NOT SET"}`); logger.debug(` WORDPRESS_APP_PASSWORD: ${process.env.WORDPRESS_APP_PASSWORD ? "SET" : "NOT SET"}`); + logger.debug("Note: DXT mode supports single-site configuration only. For multi-site, use NPM installation."); ``` --- ## Build Process ### Commands Run ```bash npm run build # Compile TypeScript npm run dxt:package:official # Build and package DXT ``` ### Build Output ``` 🧹 Building clean DXT package... 📦 Copying essential files... 📝 Updated manifest version to 2.10.2 📦 Installing production dependencies... 🎁 Creating DXT package... ✅ Official DXT package created: mcp-wordpress.dxt ``` ### Package Details - **Filename**: `mcp-wordpress.dxt` → `mcp-wordpress-2.10.2.dxt` - **Package Size**: 4.4MB - **Unpacked Size**: 14.0MB - **Total Files**: 2,235 files - **Version**: 2.10.2 (correctly synced) - **SHA**: 8d96b2bf029fa037a93bd3fa8fbe16873dd30282 --- ## Verification ### ✅ Manifest Version ```bash $ unzip -p mcp-wordpress.dxt manifest.json | jq '.version' "2.10.2" ``` ### ✅ Description Updated ```bash $ unzip -p mcp-wordpress.dxt manifest.json | jq '.description' "Comprehensive WordPress management through 59 MCP tools with performance monitoring and intelligent caching. Note: DXT installation supports single-site mode. For multi-site support, use NPM installation." ``` ### ✅ Multi-Site Prompt Removed ```bash $ unzip -p mcp-wordpress.dxt manifest.json | jq '.prompts[].name' "setup_wordpress" "content_management" "performance_optimization" ``` Only 3 prompts remain (was 4 before). ### ✅ DXT Entry Updated Compiled `dist/dxt-entry.js` includes new logging: ```javascript logger.debug("DXT entry point starting (Single-Site Mode)..."); // ... no MULTI_SITE_MODE check logger.debug("Note: DXT mode supports single-site configuration only. For multi-site, use NPM installation."); ``` --- ## What DXT Package Now Supports ### ✅ Single-Site Configuration Users can configure ONE WordPress site through Claude Desktop UI: | Field | Type | Required | Description | |-------|------|----------|-------------| | wordpress_site_url | string | Yes | Full URL (e.g., <https://yoursite.com>) | | wordpress_username | string | Yes | WordPress username | | wordpress_app_password | string | Yes | Application Password | | auth_method | string | No | Auth method (default: app-password) | | debug_mode | boolean | No | Enable debug logging (default: false) | ### ✅ Available Tools All 59 WordPress tools work in single-site mode: - Posts (6 tools) - Pages (6 tools) - Media (5 tools) - Users (6 tools) - Comments (7 tools) - Taxonomies (10 tools) - Site (6 tools) - Auth (3 tools) - Cache (4 tools) - Performance (6 tools) ### ✅ Available Prompts - `setup_wordpress` - Initial site setup and configuration - `content_management` - Content creation workflow - `performance_optimization` - Performance monitoring ### ❌ NOT Supported in DXT - **Multi-site configuration** - Not possible through DXT manifest - **Multiple WordPress sites** - Limited to single site - **Multi-site management prompt** - Removed from manifest --- ## Multi-Site Support (NPM Installation Only) For users who need to manage multiple WordPress sites: ### Installation ```bash npm install -g mcp-wordpress ``` ### Configuration Create `mcp-wordpress.config.json`: ```json { "sites": [ { "id": "site1", "name": "My First Site", "config": { "WORDPRESS_SITE_URL": "https://site1.example.com", "WORDPRESS_USERNAME": "user1", "WORDPRESS_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx" } }, { "id": "site2", "name": "My Second Site", "config": { "WORDPRESS_SITE_URL": "https://site2.example.com", "WORDPRESS_USERNAME": "user2", "WORDPRESS_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx" } } ] } ``` ### Usage ```bash mcp-wordpress ``` Server will load all sites from config file automatically. --- ## Architecture Notes ### How Configuration Loading Works The codebase **already supports multi-site** perfectly: **File**: [src/config/ServerConfiguration.ts](src/config/ServerConfiguration.ts:93) ```typescript public async loadClientConfigurations(mcpConfig?: McpConfigType): Promise<{ clients: Map<string, WordPressClient>; configs: SiteConfig[]; }> { const configPath = path.resolve(this.rootDir, "mcp-wordpress.config.json"); try { await fsPromises.access(configPath); // ✅ Multi-site config found return await this.loadMultiSiteConfig(configPath); } catch (_error) { // ❌ No config file, fall back to single-site mode return this.loadSingleSiteFromEnv(mcpConfig); } } ``` ### Why DXT Can't Do Multi-Site **DXT Limitation**: The DXT manifest `user_config` schema doesn't support: - Arrays of objects - Dynamic number of configuration sets - Multiple sets of credentials **DXT v0.1 Spec**: Only supports: - `string` - `boolean` - `number` **Not supported** (yet): - `array` - `object` (nested) - Dynamic configurations ### Potential Future Enhancement If DXT spec adds array support, we could implement: ```json { "user_config": { "sites": { "type": "array", "items": { "type": "object", "properties": { "site_url": { "type": "string" }, "username": { "type": "string" }, "app_password": { "type": "string", "sensitive": true } } } } } } ``` Until then, **DXT = single-site only**. --- ## Testing Instructions ### 1. Install DXT in Claude Desktop ```bash # Copy new DXT package to Claude Desktop cp mcp-wordpress.dxt /path/to/claude/extensions/ ``` Or use Claude Desktop UI to install the `.dxt` file. ### 2. Configure Single Site When prompted, enter: - **WordPress Site URL**: `https://yoursite.com` - **WordPress Username**: `your_username` - **WordPress Application Password**: `xxxx xxxx xxxx xxxx xxxx xxxx` - **Authentication Method**: `app-password` (default) - **Debug Mode**: `false` (default) ### 3. Verify Prompts Check that Claude Desktop shows: - ✅ `setup_wordpress` - ✅ `content_management` - ✅ `performance_optimization` - ❌ NO `multi_site_management` (should be gone) ### 4. Test Tools Try using WordPress tools: ``` wp_test_auth wp_get_site_settings wp_list_posts ``` All should work with configured site. ### 5. Check Debug Output (if enabled) If `debug_mode: true`, logs should show: ``` DXT entry point starting (Single-Site Mode)... Note: DXT mode supports single-site configuration only. For multi-site, use NPM installation. ``` No mention of `MULTI_SITE_MODE`. --- ## Documentation Updates Needed ### README.md - [ ] Add section explaining DXT vs NPM installation - [ ] Clarify single-site limitation for DXT - [ ] Add multi-site configuration instructions for NPM ### CLAUDE.md - [ ] Update installation instructions - [ ] Document DXT limitations - [ ] Add troubleshooting for multi-site ### GitHub Releases - [ ] Include note in v2.10.2 release notes - [ ] Explain DXT changes - [ ] Link to DXT package --- ## User Communication ### For DXT Users **What changed**: - Version now correctly shows 2.10.2 - Description clarifies single-site support - Removed confusing multi-site prompt **What works**: - All 59 WordPress tools - Single WordPress site management - Full feature set for one site **What doesn't work**: - Managing multiple sites simultaneously - Multi-site administration features **Workaround**: Install via NPM for multi-site support. ### For NPM Users **No changes needed**: - Multi-site configuration works as before - No breaking changes - Same configuration file format --- ## Next Steps ### Waiting for User Log Still waiting for Claude Desktop log file to: 1. Confirm what errors user experienced 2. Verify fixes address actual issues 3. Check for any other problems ### Future Enhancements 1. **Research DXT Spec Updates** - Check if DXT v0.2+ supports arrays - Explore configuration file support in DXT 2. **Add Configuration Helper** - Create interactive setup script - Generate config files 3. **Improve Documentation** - Add DXT vs NPM comparison table - Create multi-site setup guide - Add video tutorials 4. **Consider Hybrid Approach** - Allow DXT to read config file from user directory - Provide UI for managing config file - Auto-generate config from form input --- ## Summary ### Problems Fixed 1. ✅ Version mismatch (2.6.3 → 2.10.2) 2. ✅ Misleading multi-site claims 3. ✅ Removed non-functional multi-site prompt 4. ✅ Updated debug logging for clarity ### Package Status - **Size**: 4.4MB - **Version**: 2.10.2 (synced correctly) - **Files**: 2,235 files - **Status**: ✅ Ready for distribution ### Installation Methods | Method | Sites | Config | Best For | |--------|-------|--------|----------| | **DXT** | 1 | Claude Desktop UI | Single site, easy setup | | **NPM** | Multiple | JSON file | Power users, multi-site | ### Recommendation - **New users**: Install DXT for simplicity - **Advanced users**: Install NPM for flexibility - **Multi-site needs**: Must use NPM --- **Report Generated**: 2025-10-08 **Package Version**: 2.10.2 **Status**: ✅ Fixed and ready for testing **Awaiting**: Claude Desktop log file for final verification