To add to this, looking at my identity provider for the MCP server, I can see that there was a successful token exchange between Quick and the MCP Server.
However, on each subsequent call by Quick, I was getting an error message of Invalid/Missing Token in Authorization. Is it possible that Quick modifies the token?
I have not seen that error type before so I am unsure if the problem is on the Quick side or the MCP side; especially since you stated that you successfully integrated MCP into Quick. My recommendation would be to submit a support ticket, and the support team will be able to further investigate this issue and help get you further insight into your problem. Refer to this resource for how to submit a support ticket (Case management - AWS Support).
Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
Thank you for the update. Since you’re working with the AWS support team on this, I’ll go ahead and treat this inquiry as complete for now. If the support team uncovers any findings from their investigation, it would be very helpful for the community if you could share them here!
If you have any additional questions about this topic, feel free to create a new post in the community and link this discussion for context.
