Troubleshooting MCP
Having trouble connecting or using ScentSell's MCP tools? Here are solutions to common issues.
"Premium required" error
Problem: Your AI client returns an error saying Premium is required.
Solution: MCP access requires an active ScentSell Premium subscription. Go to scentsell.com.au/subscribe to upgrade or start a free trial.
"Invalid token" or "Unauthorised" error
Problem: The tool call fails with an authentication error.
Solution:
- In your AI client, go to MCP settings and remove the ScentSell server.
- Re-add it with the same server URL.
- Go through the OAuth flow again to get a fresh token.
"No matching fragrance" error
Problem: You ask the AI to log a wear but it says it can't find the fragrance.
Solution:
- Check the fragrance is in your collection. Use
get_my_collectionor open the ScentSell app. - If it's not there, add it first: "Add [fragrance name] to my collection".
- Try the log wear command again.
The AI doesn't seem to have my ScentSell tools
Problem: You've added the MCP server but the AI isn't using ScentSell tools.
Solutions:
- Restart your AI client after adding the server. Claude Desktop requires a restart.
- Ensure the server URL is entered exactly:
https://mcp.scentsell.com.au/api/mcp - Try explicitly asking: "Use your ScentSell tools to list my collection"
OAuth flow fails or browser doesn't open
Problem: The authorisation browser window doesn't open or errors out.
Solutions:
- Ensure your browser is set as the default browser on your system.
- Try opening the authorisation URL manually in a browser.
- Check you're signed in to ScentSell at scentsell.com.au.
Rate limit error (HTTP 429)
Problem: Tool calls return a 429 error.
Solution: ScentSell MCP is rate-limited to 100 calls per minute per user. If you're hitting this limit, slow down. The response includes a retry_after_ms field — wait that long before retrying.
This limit is rarely hit with normal usage. It's designed to prevent runaway automated scripts.
Still stuck?
Contact support@scentsell.com.au with:
- Your AI client name and version
- The exact error message
- What you were trying to do
Next steps: