Documentación/troubleshooting
Debug mode
FreeEnable verbose logging and stack traces for troubleshooting.
Enable debug mode
StoreMCP → Settings → Advanced → Debug mode → On
While debug mode is on:
- Error responses include stack traces
- Every tool call writes a line to
wp-content/storemcp.log - Request/response bodies are logged (be careful — may contain PII)
Don't leave debug mode on in production
Sensitive data may end up in logs. Turn it off once you've diagnosed the issue.
WordPress debug
For issues that seem to be in WordPress itself, enable WP_DEBUG in wp-config.php:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
Errors go to wp-content/debug.log.
Request tracing
Every StoreMCP request has a unique X-StoreMCP-Request-Id. Include this ID when filing a support ticket — we can look it up immediately in your activity log.
Bug reports
If you've hit a real bug, open an issue: github.com/storemcp/store-mcp/issues. Include:
- StoreMCP version
- WordPress + WooCommerce versions
- PHP version
- The request ID
- Minimal reproduction steps