MCP for WooCommerce

Getting Started

Setup

Connect your WooCommerce store to Claude Code, Claude Desktop, Cursor or VS Code: the endpoint URL and a ready configuration for each client. No token or login needed.

This page covers the plugin's settings and a ready configuration for each common MCP client.

Plugin Settings

Access the plugin settings at Settings > MCP for WooCommerce in your WordPress admin.

Basic Settings

Enable MCP functionality

  • Turns the MCP endpoints on. Nothing else works until it is on.

Access

  • The card below the switch shows your MCP endpoint URL. Copy it into your AI client.
  • The endpoint is public while MCP is on, like the WooCommerce Store API, and it only reads. No token or login is needed.

Tool Configuration

All 31 tools only read data. The Tools tab has a switch for each one; an assistant never sees a tool you have switched off. Leave on only what your use case needs.

Your Endpoint

https://your-site.com/wp-json/wp/v2/wpmcp/streamable

Replace your-site.com with your own domain. The configurations below all use this URL and need no credentials.

Client Configurations

Claude Code

claude mcp add --transport http mcp-for-woocommerce https://your-site.com/wp-json/wp/v2/wpmcp/streamable

Claude Desktop

Add to your Claude Desktop claude_desktop_config.json. It uses mcp-remote, so Node.js must be installed:

{
    "mcpServers": {
        "mcp-for-woocommerce": {
            "command": "npx",
            "args": [ "-y", "mcp-remote", "https://your-site.com/wp-json/wp/v2/wpmcp/streamable" ]
        }
    }
}

Cursor IDE

Add to your Cursor MCP configuration file:

{
    "mcpServers": {
        "mcp-for-woocommerce": {
            "url": "https://your-site.com/wp-json/wp/v2/wpmcp/streamable"
        }
    }
}

VS Code MCP Extension

Add to your VS Code MCP settings:

{
    "servers": {
        "mcp-for-woocommerce": {
            "type": "http",
            "url": "https://your-site.com/wp-json/wp/v2/wpmcp/streamable"
        }
    }
}

MCP Inspector (Development/Testing)

npx @modelcontextprotocol/inspector

Choose Streamable HTTP as the transport and enter your endpoint URL.

Clients That Only Run Local Processes

A client that can only start an MCP server as a local process can use mcp-proxy.php, a standalone bridge in the GitHub repository. It is not part of the plugin ZIP. Download it, then run it with PHP and your endpoint:

php mcp-proxy.php https://your-site.com/wp-json/wp/v2/wpmcp/streamable

Endpoint Details

The plugin has two endpoints. Both are public while MCP is on, and both only read.

Streamable HTTP (recommended)

  • Endpoint: /wp-json/wp/v2/wpmcp/streamable
  • Format: JSON-RPC 2.0
  • Credentials: none

Example Methods:

  • tools/list - List available tools
  • tools/call - Execute a tool
  • resources/list - List available resources
  • resources/read - Read resource content
  • prompts/list - List available prompts
  • prompts/get - Get prompt template

WordPress REST-style

  • Endpoint: /wp-json/wp/v2/wpmcp
  • Format: WordPress-style REST API
  • Credentials: none

Some of the tools:

  • wc_products_search - product search that works for any kind of catalogue
  • wc_get_product_variations - all variations (colours, sizes and so on) of a variable product
  • wc_get_categories - all product categories
  • wordpress_posts_get - one WordPress post by ID
  • wordpress_pages_get - one WordPress page by ID

The tools reference lists all 31.

A client that still sends an Authorization header keeps working; the plugin ignores the header.

Testing the Setup

Basic Connection Test

  1. Open the AI client you connected
  2. Ask: "What products do I have in my WooCommerce store?"
  3. It should call the product search tool and list your products

More Questions to Try

  • "What sizes and colours does [product name] come in?"
  • "Which shipping methods do you offer, and to which countries?"
  • "Which payment methods can customers use?"
  • "Show me the products in the [category name] category"

The plugin only reads, so a request to create or change something will fail. That is expected.

Security Considerations

What the Endpoint Returns

Only storefront data a shop visitor can already see: published, catalog-visible products and their variations, categories, tags, brands, attributes, approved reviews (reviewer name only), shipping zones and enabled methods with their cost, tax classes and rates, the payment methods offered at checkout, and published posts and pages that are not password-protected (author display name only).

It never returns orders, customers, users, e-mail addresses, store settings, or draft, private or password-protected content. The plugin never signs in as a WordPress user.

Stopping Access

  • Switch Enable MCP functionality off to close both endpoints
  • Switch individual tools off on the Tools tab to hide them
  • Keep the plugin updated

Troubleshooting

Common Issues

Connection timeout or 404

  • Check that the site loads in a browser
  • Check that Enable MCP functionality is on
  • Check whether a firewall or security plugin blocks /wp-json/
  • Check that the SSL certificate is valid

A tool is missing

  • It is switched off on the Tools tab. Switch it on and reconnect the client.

Product links are wrong

  • Set Settings > Permalinks in WordPress to "Post name"

Next: AI Assistant → | Tools →

Was this page helpful?