Use this guide to resolve common WowShipping MCP connection, authentication, permission and shipping-rule configuration issues.
The Connection Panel Asks You to Save an Access Mode
Navigate to WooCommerce → WowShipping → AI Tools → Access Mode.
Select Read only, Manage or Full access, click Save access mode and check Current Access.
Selecting Off disables MCP connections.
A System Readiness Check Is Not Ready
Check the components identified under System Readiness:
- WordPress 6.9+ and Abilities API.
- WooCommerce.
- WordPress MCP Adapter.
- Pretty permalinks.
Resolve the reported issue and recheck System Readiness before connecting.
Your AI Assistant Cannot Reach Your Website
For remote MCP connections, confirm that:
- Your website is publicly accessible over HTTPS.
- Your WowShipping MCP server address is correct.
- Your hosting provider, firewall, security plugins or website password protection are not blocking the connection.
Remote connectors cannot access localhost. For local websites, use a compatible desktop or CLI application that can reach your website.
Sign-In or Authorization Fails
Sign in using a WordPress administrator account and check the error returned by your AI application.
Confirm that you are using the correct authentication method:
| Connection | Authentication |
|---|---|
| Remote web connector | OAuth with WordPress sign-in and approval |
| Desktop bridge | WordPress application password |
| CLI connection | WordPress application password encoded in Base64 with the username |
If the application was disconnected or MCP access was set to Off, save an enabled access mode and authorize the OAuth connection again.
A Desktop App Cannot Start the Local Bridge
Check that:
- Node.js is installed and
npxis available. - You are using the current configuration from WowShipping.
- Your WordPress username and application password are correct.
OAUTH_ENABLEDis set to"false".
Save the configuration and restart the application.
VS Code requires a separate configuration in .vscode/mcp.json using servers and type: stdio. The generic desktop configuration uses mcpServers.
CLI Authentication Fails
Generate your Base64 credentials using your actual WordPress username and application password.
Check that:
- The encoded value contains no line breaks.
- The Authorization header starts with
Basicfollowed by a space and the encoded value. - Your application password has not been revoked.
- The MCP server address is correct.
Treat Base64 credentials as passwords when sharing diagnostic information.
A Tool Is Disabled or a Request Is Refused
Check Current Access and the Tools table in WowShipping.
| Operation | Required Access |
|---|---|
| Lookups, validation and simulation | Read only or higher |
| Create, update, publish, disable and supported settings changes | Manage or Full access |
| Permanently delete a rule | Full access |
WordPress account permissions, OAuth consent scopes and applicable Pro requirements also apply.
Read the returned error and verify the requested operation, rule ID and other inputs. Not every refusal is caused by insufficient permissions.
Shipping Rule Validation Fails
Ask your AI assistant to retrieve get-rule-options and explain the validation error.
Review the proposed configuration against the supported shipping methods, conditions, operators and value formats.
Correct the reported issue and validate again before saving or publishing.
A Shipping Rule Is Not Producing Expected Rates
New shipping rules are unpublished until you explicitly publish them.
Check the rule’s:
- Current status.
- Shipping zone.
- Rate configuration and conditions.
Simulate the relevant products, quantities and delivery address, then inspect the returned shipping rates.
Successful validation confirms that the configuration is valid. It does not guarantee the expected checkout rates.
A Published Shipping Rule Needs Editing
Disable the published rule before updating it. This returns the rule to draft and stops its live checkout rates.
Retrieve the latest revision, update the draft, validate and simulate the revised configuration, then approve republication.
Follow the Edit a Published Shipping Rule section in What Can You Do with WowShipping MCP? for the required update parameters and array replacement behavior.
No MCP Activity Is Shown
Recent MCP Tool Activity retains up to 100 entries from the last 30 days.
Discovery, OAuth traffic and requests rejected before tool execution are not recorded. Repeated calls with the same user, tool and outcome within one minute are suppressed.
Run the Confirm your AI can read this store prompt and inspect the tool response alongside the activity panel.
An empty activity log does not necessarily mean that no connection attempt occurred.
Contact WowShipping Support
If the issue persists, provide:
- WordPress, WooCommerce, WowShipping and MCP Adapter versions.
- AI application and connection method.
- Current MCP access mode.
- Tool name and exact error message.
- Relevant redacted MCP activity details.
- Rule ID and a reproducible test scenario for shipping-rule issues.
Never share passwords, access tokens, Base64 credentials or unnecessary customer-address information.