Troubleshooting
Ordered roughly by how often each one comes up.
Connected, but every answer is empty
The connection is fine; the data is not there yet. Check in this order:
- Is Seller Central connected in Propamp? Open the web app. If the dashboard is empty there too, MCP has nothing to read. See Connecting Sales Channels.
- Has the first sync finished? A freshly connected account takes time to backfill.
- Is the marketplace right? Asking about
DEwhen you only sell inUSreturns nothing, correctly. See Marketplaces & Dates.
401 Unauthorized
The client has no valid token. Either it never completed the sign-in, or the token was revoked.
- Claude — remove the connector and add it again, then complete the browser sign-in.
- Codex — run
codex mcp login propamp.
A 401 on your very first request, before any sign-in, is expected — it is how the server tells the
client where to authenticate.
404 partway through a session
An idle session expired after 60 minutes. Compliant clients start a new one automatically; if yours does not, restart the session or the client. Nothing is wrong with your account.
Signed in, but no tools appear
Two causes, in order of likelihood:
- Seller Central is not connected yet — see above.
- Your plan needs the MCP access add-on. Trial organizations have MCP access included; paid plans need the add-on to connect an outside client. Email [email protected].
To see which organization the session is actually authenticated as, ask your assistant to run
mcp_debug_backend_config. To check the Propamp backend is reachable, mcp_debug_backend_ping. See
Diagnostics.
A billing message where the data should be
External MCP access is not enabled for your organization. The message your client shows comes straight from Propamp billing. Email [email protected].
The connector will not save (Claude)
Custom connectors need a Claude Pro plan or above. They are not available on Free.
The URL is rejected, or the server is not found
Confirm it is exactly this, with no /sse suffix and no trailing slash:
https://mcp.propamp.ai/mcpIf you followed an older guide to https://mcp.propamp.ai/mcp/sse, that is the legacy transport. It
still serves existing connectors, but Codex and several other clients cannot speak it at all — they will
report a connection or SSE error rather than a clear message. Switch to /mcp.
To prove the endpoint is reachable independently of any client, see
verifying the server is reachable. A 401 there
is a healthy result.
Amazon Ads tools are missing
They appear only when an Amazon Ads key is connected in Propamp. Campaign-editing tools are additionally off by default and enabled per organization on request. See Amazon Ads (Beta).
A tool call fails with a validation error
The request reached Propamp but a field was rejected. Almost always a marketplace code or a date format — see Marketplaces & Dates. Tell your assistant the exact error; it can usually correct the call itself.
Nothing here matches
Email [email protected] with:
- your Propamp account email
- which client you are connecting, and its version
- the exact error text, and whether sign-in completed
- roughly when it started
Connection problems are usually resolved the same working day.