Installation guide
How to install WooCommerce MCP integration
In Claude Desktop, ChatGPT, Cursor and Claude Code, with what to check before you start and the first prompts to run.
The WooCommerce MCP integration is an official feature built on the WordPress Abilities API. It exposes store operations to AI clients. The listing says it can run in both remote and local forms, but the documentation page we were given is only a blog index with no setup details, so we do not state an endpoint, command or setting here. Take every exact value from the current developer documentation. The feature is developer-oriented and still evolving.
A developer or technical store owner with administrator access to a staging copy of the store should do this. Do not connect with an administrator account for day-to-day use. Create a dedicated user with the minimum role needed, and start with read-only tasks. Allow write actions only for supervised work, after testing on staging.
Before you start
- A staging copy of your WooCommerce store, so you can test before touching the live shop.
- A WooCommerce version that includes the MCP integration, confirmed against the current developer documentation at developer.woocommerce.com.
- Administrator access to the staging site to enable the feature and review which abilities (actions) are exposed.
- A dedicated WordPress user or credential with the minimum role needed, not an administrator account.
- An MCP client that supports the connection method described in the vendor docs (remote URL or local command).
- How it runs
- Remote or local
- Access
- Varies by tool
- Server address
- Copy it from the vendor documentation
WooCommerce MCP integration in Claude Desktop
- The documentation text we reviewed does not cover Claude Desktop, so use the client's standard way of adding an MCP server and take the exact values from the WooCommerce docs.
- On your staging site, update WooCommerce, enable the MCP feature as the docs describe, and review which abilities are exposed.
- Create a dedicated user or credential with the minimum role needed, and note how the docs say it should be supplied.
- If the docs give a remote server URL, open the connectors or integrations settings in Claude Desktop and add it as a custom remote server, then complete any sign-in.
- If the docs describe a local server, add it as a command in Claude Desktop's MCP configuration, using the command and settings exactly as the vendor documents them.
- Restart Claude Desktop if needed, then run the read-only prompts below against staging.
WooCommerce MCP integration in ChatGPT
- The documentation text we reviewed does not cover ChatGPT, so use ChatGPT's standard way of adding a remote MCP server by URL. Availability depends on your plan and workspace settings.
- On your staging site, enable the WooCommerce MCP feature as the docs describe and review the exposed abilities.
- Create a dedicated minimum-role user or credential for this connection.
- Open the connectors or integrations settings in ChatGPT, and add a custom connector using the remote URL from the WooCommerce documentation. If the docs only describe a local server, ChatGPT cannot use it directly.
- Complete the sign-in or authorization the docs describe, using the dedicated account.
- Start a new chat, enable the connector, and run the read-only prompts below.
WooCommerce MCP integration in Cursor
- The documentation text we reviewed does not cover Cursor, so use Cursor's standard way of adding an MCP server and take the exact values from the WooCommerce docs.
- On your staging site, update WooCommerce, enable the MCP feature, and review which abilities are exposed.
- Create a dedicated user or credential with the minimum role needed.
- Open Cursor's settings and find the MCP servers section.
- Add the server either as a remote URL or as a local command in Cursor's MCP config, matching what the vendor docs specify. Do not guess keys or flags.
- Confirm the server shows as connected with its tools listed, then run the read-only prompts below.
WooCommerce MCP integration in Claude Code
- The documentation text we reviewed does not cover Claude Code, so use Claude Code's standard way of adding an MCP server and take the exact values from the WooCommerce docs.
- On your staging site, enable the WooCommerce MCP feature as described and review the exposed abilities.
- Create a dedicated user or credential with the minimum role needed.
- Use Claude Code's MCP add command, as described in its own documentation, to register either the remote URL or the local command from the WooCommerce docs.
- Choose a scope (just you, or shared with the project) deliberately. Avoid committing credentials into a shared project file.
- Start a session, check that the server and its tools are listed, then run the read-only prompts below.
Check that it works
Start with questions that only read data. If these answer from your real account, the connection is good.
- List the abilities or tools this WooCommerce connection exposes, and say which ones can change data.
- Show the five most recent orders on the staging store with their status and total. Do not change anything.
- List the first ten products on the staging store with name, price and stock status. Read only.
Troubleshooting
+The client does not list the server or any tools. What should I check?
Confirm the MCP feature is enabled on the WooCommerce site as the vendor documentation describes, and that your WooCommerce version includes it. Then check that the URL or command was copied exactly from the docs, and restart the client. The feature is evolving, so requirements may have changed since this guide was written.
+I get an authentication or permission error. What now?
Check that the credential belongs to the dedicated user and that the user's role allows the action. Read-only tasks usually need fewer permissions than edits. Confirm the credential type and how to supply it in the vendor docs, and regenerate it if unsure. Avoid fixing this by switching to an administrator account.
+An action I expected is missing. Why?
The integration exposes a defined set of abilities, and what is available can vary by tool and by version. Review the list of exposed abilities in the site settings or docs, and check whether a plugin registers the one you need. Confirm your user role may use it, and retest on staging after any update.
Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.