Resolved after 3 hours 14 minutes, affecting EastUsa and Ireland, on May 14, 2026.
The fix has fully deployed now seeing service return to normal What happened: A change we shipped to the MCP OAuth flow yesterday introduced a regression in how authentication tokens were handled by MCP tool calls. The OAuth handshake itself succeeded, so connecting to the MCP server worked, but invoking specific tools (like listing models or running queries) returned a “403 Invalid bearer token” error. Who this affected: Customers using MCP integrations that connect through callbacks.omniapp.co (Claude, ChatGPT, etc). Direct connections from CLI clients are not affected.
Affected components
Update timeline
- investigating May 14, 2026, 09:32 AM UTC
We are currently investigating issues with users seeing 403 errors connecting to MCP clients
- monitoring May 14, 2026, 10:15 AM UTC
We have identified the source of the issue, are implementing a patch and monitoring results
- resolved May 14, 2026, 12:46 PM UTC
The fix has fully deployed now seeing service return to normal What happened: A change we shipped to the MCP OAuth flow yesterday introduced a regression in how authentication tokens were handled by MCP tool calls. The OAuth handshake itself succeeded, so connecting to the MCP server worked, but invoking specific tools (like listing models or running queries) returned a “403 Invalid bearer token” error. Who this affected: Customers using MCP integrations that connect through callbacks.omniapp.co (Claude, ChatGPT, etc). Direct connections from CLI clients are not affected.
Your product runs on more than Omni Analytics
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services