mcp-for-woocommerce

MCP for WooCommerce turns a WordPress/WooCommerce installation into an MCP data source that AI assistants can query. It exposes read-only access to products, categories, reviews, and WordPress content through two transports: a WordPress-style STDIO endpoint and a modern, low-latency Streamable HTTP JSON-RPC endpoint. Clients can use the standard WordPress MCP proxy tooling to connect (via Claude Desktop or compatible MCP clients) and retrieve permalinks for products and variations to present clickable links in AI responses. This setup is designed to keep customer data private while offering rich, browsable catalog information to AI agents and chat interfaces.

Prerequisites:

• WordPress 6.4+ with WooCommerce activated
• PHP 8.0+ on the WordPress host
• Node.js and npm for admin UI build (development)
• Composer for development

Installation options:

1. WordPress Admin (recommended)

• In WordPress, go to Plugins > Add New > Upload, and upload the MCP for WooCommerce plugin ZIP from the releases page.
• Activate the plugin and configure as needed (JWT, tools, etc.).

2. Manual installation

• Upload the plugin ZIP to wp-content/plugins/ and unzip.
• Activate the plugin in the WordPress admin area.

3. Development install (for contributing or testing)

cd wp-content/plugins/
git clone https://github.com/iOSDevSK/mcp-for-woocommerce.git
cd mcp-for-woocommerce
composer install
npm install && npm run build

Configure the MCP client (example with Claude Desktop proxy):

# Use the following in Claude Desktop or your MCP client configuration
{
  "mcpServers": {
    "mcp-for-woocommerce": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://your-site.com",
        "JWT_TOKEN": "YOUR_JWT"
      }
    }
  }
}

Notes:

• The WordPress REST endpoints used are /wp-json/wp/v2/wpmcp (STDIO) and /wp-json/wp/v2/wpmcp/streamable (Streamable HTTP).
• Ensure JWT authentication is configured if you require secured access; you can also enable a local proxy mode when JWT is disabled.

Tips and considerations:

• Use the Streamable endpoint for lower latency and direct integration with modern MCP clients.
• When JWT Authentication is disabled, the plugin can auto-generate a Claude Desktop-friendly proxy script (mcp-proxy.js) to simplify local testing.
• The tools exposed by this MCP server are read-only to protect customer data; always include permalinks in AI responses for product references.
• Manage tokens via WordPress Admin > Settings > MCP for WooCommerce. Rotate tokens regularly and use short expirations in production.
• If you encounter CORS or authentication issues, verify that WP_API_URL and JWT_TOKEN are correctly set in your MCP client configuration and that the WordPress site is reachable from the client environment.