Store MCP Troubleshooting
Start with the symptom, preserve the activity ID and change only the setting the evidence identifies.
MCP connection or authorization failed
Confirm the exact https://store-mcp.com/mcp endpoint and follow the client’s canonical guide. Check whether your account and organization allow custom remote MCP connections. A saved URL alone is not a working connection.
Complete browser sign-in and consent, then test stores.list. If authorization expired or was revoked, reconnect the client with the intended store scope. For a provider reauthorization issue, reconnect the store in Stores. These are separate credentials. Never send tokens, cookies or callback query strings to support.
Permission, approval or plan errors
FORBIDDEN: inspect client permission and selected stores. PLAN_REQUIRED: check the paid write entitlement. SUBSCRIPTION_REQUIRED: repair billing. CAPABILITY_UNAVAILABLE: inspect stores.get and provider limits. Do not assume paying more enables an unsupported operation.
APPROVAL_REQUIRED: the owner must review the exact supported request in Store MCP before the client resubmits unchanged arguments and key with approvalId. A client’s verbal confirmation is not enough. Ordinary listing and stock writes have different requirements from sensitive actions.
Listing publish failed
Read the draft and listingRequirements.get. Check category, required attributes, policies, inventory location, image readiness and seller eligibility. eBay business-policy failures can occur on a healthy connection. WooCommerce create/update is simple-product only. Square has no Store MCP publish operation.
Use a fresh read after resolving requirements. If the provider outcome is unknown, inspect the original receipt before another publication attempt; do not duplicate a listing or change the idempotency key merely to bypass uncertainty.
Inventory conflicts
Check that inventoryId belongs to the intended variation and location. Read the latest quantity, compare with your expectedQuantity and ask whether the desired absolute count still makes sense. Never force an overwrite to silence a conflict.
Provider concurrency guarantees differ: eBay and WooCommerce read/check/update can race, and Square physical counts are not Shopify compare-and-swap. Stop for unknown outcomes and verify provider stock before any new intent.
Missing notifications
Check ingestion first: eBay, Square and WooCommerce do not emit Store MCP commerce events. A synthetic test is not an order event. Shopify/Etsy require their separately configured provider subscriptions and applicable access.
Then check event type and store filters, enabled state, destination health and plan entitlement. Test the endpoint. Redirects are refused; timeout, 429 and server failures may retry and duplicate. There is no historical backfill when you add a destination.
Escalate safely
Send support the expected result, approximate time, platform and activity ID. Exclude buyer data, raw provider responses, tokens, destination URLs and credentials. For urgent commerce work, use the provider’s own administration tools while the integration issue is investigated.