MCP for WooCommerce Plugin 1.2.1

Implemented OAuth 2.0 Authorization Code Flow with PKCE support

ADDED -Full OAuth 2.0 Authorization Code Flow with PKCE (RFC 7636)
ADDED - Dynamic client registration endpoint (RFC 7591)
ADDED - Custom authorization form for seamless OAuth flow without WordPress login
ADDED -OAuth discovery endpoint (/.well-known/oauth-authorization-server)
ADDED - Support for claude.ai web version authentication
ENHANCED - JWT authentication to accept tokens with or without Bearer prefix
IMPROVED - Claude Code compatibility with OAuth-compliant error responses
IMPROVED - Token endpoint returns OAuth-standard response format (access_token, token_type)
ADDED - Activation/deactivation hooks for automatic OAuth discovery file management
CHANGED - SECURITY: PKCE code challenge methods supported (S256, plain)
CHANGED - COMPATIBILITY: Works with Claude Code, Claude.ai web, and any MCP client supporting OAuth 2.0

MCP for WooCommerce Plugin 1.2.0

Generate token - FIXED.

MCP for WooCommerce Plugin 1.1.9

FIXED -Ensure build/ directory included in SVN tag for WordPress.org
FIXED - React admin UI loading correctly after plugin installation
CHANGED VERIFIED: All build files (index.js, index.asset.php, CSS) present in distribution
RESOLVED Empty settings page issue on fresh installations from WordPress.org

MCP for WooCommerce Plugin 1.1.8

🎯 Release Highlights

This release addresses all WordPress.org plugin review requirements and fixes critical boolean settings storage issues that caused authentication inconsistencies.

✅ WordPress.org Compliance Fixes

All requirements from the WordPress.org plugin review team have been implemented:

Naming & Branding

• ✅ Changed text domain from 'wordpress-mcp' to 'mcp-for-woocommerce' across all JavaScript files
• ✅ Updated CSS class prefixes from wordpress-mcp-* to mcpfowo-* for uniqueness
• ✅ Excluded .wordpress-org folder from release ZIP package

Already Compliant (Verified)

• ✅ Requires Plugins: woocommerce header present
• ✅ composer.json included in plugin package
• ✅ File Paths: Using plugin_dir_path(), plugin_dir_url(), wp_upload_dir()
• ✅ Remote Requests: Using wp_remote_get() instead of file_get_contents()
• ✅ Output Escaping: Using wp_json_encode() instead of json_encode()
• ✅ Direct Access Protection: ABSPATH check in main plugin file
• ✅ Unique Constants: MCPFOWO_* prefix used throughout

🔧 Critical Bug Fixes

Boolean Settings Storage (#000024)

Fixed inconsistent boolean value storage that caused authentication to randomly fail:

• Root Cause: WordPress stored boolean settings as mixed types ('', '0', 0, '1', 1, true, false)
• Impact: JWT authentication randomly failed with "invalid token" errors
• Solution: Always store as integers (0 or 1) and use robust boolean conversion when reading

Fixed Settings:

1. Enable MCP functionality - Now reliably stores enabled/disabled state
2. JWT Authentication Required - No more random "invalid token" errors
3. Individual Tools Toggle States - Each tool's enabled/disabled state now consistent

Technical Details:

• Settings.php: Always store as $enabled ? 1 : 0 instead of boolean
• JwtAuth.php: Robust reading handles '', '0', 0 as FALSE and '1', 1 as TRUE
• WpMcp.php: Tool states use same robust boolean conversion
• McpTransportBase.php: MCP enabled check uses same pattern

📦 Installation

Download mcp-for-woocommerce.zip and upload to your WordPress site via:

• Admin Dashboard: Plugins → Add New → Upload Plugin
• FTP: Extract to /wp-content/plugins/mcp-for-woocommerce/

🔄 Upgrade Notes

For Existing Users:

1. Deactivate the old version
2. Delete the old plugin files
3. Install version 1.1.8
4. Reactivate and verify settings in Settings → MCP for WooCommerce

Settings Verification:

• Check "Enable MCP functionality" toggle
• Verify "Require JWT Authentication" setting
• Review individual tool states in Tools tab

All settings should now persist correctly across activation/deactivation cycles.

MCP for WooCommerce Plugin 1.1.7

UPDATED - Plugin description with community plugin disclaimer
UPDATED - Author information to Filip Dvoran only
UPDATED - All repository links to community GitHub repo
ADDED - Community plugin disclaimers throughout documentation
CLARIFIED - Plugin independence in README and plugin headers
UPDATED -Composer and package.json with correct author and repository info

MCP for WooCommerce Plugin 1.1.6

Smart System Requirements Monitoring & Enhanced User Experience

🎯 Key Features:

• Intelligent System Warnings: Admin interface now displays contextual warnings only when actual configuration issues are detected
• REST API Health Check: Automatic detection of WordPress REST API availability with targeted alerts when disabled
• Permalinks Validation: Smart monitoring of permalink structure with warnings when not set to "Post name" (required for product links)
• Enhanced Admin UX: Clean, professional warning system that guides users to fix configuration issues

⚙️ Technical Improvements:

• Added PHP-based system status detection methods (is_rest_api_enabled(), are_permalinks_correct())
• Implemented React components with conditional warning logic for optimal performance
• Enhanced Settings tab with real-time system health monitoring
• Improved user guidance with actionable resolution steps

🔧 Developer Experience:

• Fixed McpProxyGenerator plugin directory path resolution
• Reorganized documentation structure for better maintainability
• Improved build scripts with automatic version detection
• Streamlined repository structure and development workflow

🚀 What's New:

• Warnings appear only when needed - no more unnecessary notifications
• Professional, WordPress-standard warning styling with clear resolution guidance
• Automatic system health monitoring ensures optimal plugin performance
• Enhanced troubleshooting with specific problem identification

This release focuses on providing a smarter, cleaner admin experience while ensuring users have the correct configuration for optimal WooCommerce AI integration.

MCP for WooCommerce Plugin 1.1.5

Fixed critical issues: TypeError in JWT token verification, fatal errors with WordPress functions, and 500 errors from Settings class dependency.
Improved system stability and reliability across authentication processes and transport methods (streamable/stdio).
Added debug logging, JWT option initialization, and Webtalkbot integration notes for better troubleshooting and user guidance.
Enhanced UI: Hid Authentication Tokens tab when JWT is disabled and added a toggle for enabling/disabling JWT authentication.
Streamlined authentication handling, improved error handling, and increased configuration flexibility.