When connecting the Claude (Anthropic) MCP connector to Trello, the OAuth consent screen at auth.atlassian.com/consent loads with the Accept button permanently greyed out/disabled, so authorization can never be completed. Clicking Cancel works fine, but Accept never becomes clickable no matter how long I wait or how many times I retry.
Inspecting the page, there is a hidden required field (selectedToolsets) that stays empty because no toolset/resource picker UI ever renders for the user to fill it in - so the button's disabled condition never clears.
This looks similar to another recent report here in the community, "Atlassian Claude Connector failing to connect" (July 15, 2026), which described a related failure in the Claude-Atlassian OAuth flow. Has anyone found a fix, or is this a known bug being tracked?
Hi @Rafa Muñoz ,
Welcome to the community!
The root cause is that the Atlassian account being used to authorize the Claude (Anthropic) MCP connector does not have a Trello account linked to it. When this happens, the OAuth consent screen at auth.atlassian.com/consent fails to load properly, resulting in the Accept button remaining greyed out/disabled.
Our engineering team is also working on a fix to properly display an error message in this scenario so that it's clear what's happening, rather than showing a non-functional consent screen.
Please let us know if creating a Trello account resolves the issue for you, or if you continue to experience trouble after doing so.
Estoy teniendo el mismo problema. Al intentar conectar el conector de Trello MCP con Claude, la pantalla de consentimiento en auth.atlassian.com/consent muestra "No workspace available" y "0 out of 0 permissions selected", con el botón Accept deshabilitado. Confirmo que soy admin del workspace, tengo Trello funcionando normalmente en el navegador, probé en incógnito y con distintas cuentas, y el error persiste. ¿Hay novedades sobre el fix?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Arrayanes Group ,
Welcome to the community!
It's also possible that the Atlassian account being used in the OAuth flow isn't the same one linked to your Trello workspace. Even if Trello works normally in your browser, the consent screen authenticates separately and may pick up a different session. Can you please try from a private browser?
Also, please refer to this article: troubleshoot-trello-mcp-connection-errors
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Rafa Muñoz , Welcome to the Community!
As announced here, the official Trello MCP server just launched today.
You can now visit https://trello.com/mcp to re-attempt connecting with Claude.
Hope it helps 🙌
Liam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.