Authorization with MCP server failed - Monday.com connector in Cowork (ofid_d849998b677788b3, ofid_e6c58f663a38985e)

[sergiocc77-hub]

MCP server URL or name

https://mcp.monday.com/mcp

How are you connecting to this server?

From a custom connector URL I entered manually

Where does the issue occur?

When pressing the Connect button

When did you last reproduce this?

2026-06-14 4:00 PM CLT

Browser and OS

Safari on macOS

Describe the issue

I tried to connect the Monday.com connector from the Cowork desktop app. The OAuth flow opens in the browser, I authenticate successfully with my Monday.com account, but after redirecting back to Cowork the error "Authorization with the MCP server failed" appears. I have disconnected and reconnected twice with the same result. Monday.com is not behind any firewall. All systems on status.monday.com show operational.

Error details

"Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support."

Reference codes:
- ofid_d849998b677788b3
- ofid_e6c58f663a38985e

Expected behavior

Successful OAuth connection to Monday.com via Cowork.

Additional context

This same issue is documented in #327 with 20+ identical reports. The OAuth flow completes successfully but the post-token authenticated callback fails on Anthropic's broker side. I have already contacted support via email 3 times and only received automated responses that did not review the ofid_ codes.

I am connecting from the Cowork desktop app (not Claude.ai web).

[sergiocc77-hub]

Update: tried again after disabling AdBlock in Safari — same error persists.

New reference code: ofid_cfeaf46176e38168

This confirms the issue is not related to browser extensions or client-side configuration. Three failed attempts with three different ofid_ codes:

• ofid_d849998b677788b3
• ofid_e6c58f663a38985e
• ofid_cfeaf46176e38168

Awaiting review from engineering.

[localden]

Thank you for taking the time to report this.

We traced the reference IDs you shared (2026-06-14, ~19:47 to ~20:26 UTC). Signing in to monday.com succeeds, and monday.com issues a valid access token. The failure happens on the next step, when Claude uses that token to open the connection to the monday.com MCP server: the server responds with HTTP 403 Forbidden. This is an account-level permission check on the monday.com side rather than a problem with the sign-in flow.

Things worth checking in your monday.com workspace:

• whether an admin needs to enable AI features or API access for your user
• whether your monday.com plan includes access to their hosted MCP server
• whether your user role (for example viewer or guest) has API permission

If those all look correct, monday.com support should be able to tell you why the server is returning 403 for your account. There is nothing to change on the Claude side for this one.

If the situation changes and you still see a failure, please reopen with a fresh reference ID and we will re-trace.