TrelloMCP consent "Permissions are blocked for these workspaces" despite all org MCP permissions all

Eric Poatty

I'm the organization admin (and only user) of my Atlassian organization, and I'm trying to authorize an OAuth client ("Muse") for Trello's official MCP server (https://mcp.trello.com/v1). At the workspace consent step, selecting my Trello workspace shows "Permissions are blocked for these workspaces — Contact your organization admin to request access" and the Accept button stays disabled. The same thing happens for both of my workspaces.

Everything support documentation and the support AI pointed to has been checked:

• Atlassian MCP server settings → Domains: the client's callback domain (https://agent.meta.ai/api/hatch/oauth/callback) is allowlisted. I also removed and re-added it and saved, with no change.
• MCP server → Permissions: Read 16/16, Write 16/16, Search 4/4 all allowed, including the read_trello and write_trello toolsets. (Delete and Manage are blocked, which I understand is expected.)
• Data security policy: the "Atlassian MCP server" control is set to Allowed with 0 overrides.
• I captured the consent URL and decoded it: the request sent only the scopes "offline_access read:board:trello write:board:trello" for resource https://mcp.trello.com/v1 — no account-level Inbox/Planner scopes and no organization scopes.
• Update: I have since verified and claimed my domain in Atlassian Admin, so my account is now a claimed, managed account (this was not the case during the earlier checks). A fresh consent retry after that, signed out and back in (~06:22 UTC, Oct 30), still shows the same blocked banner.

So every documented control is set to allow, and the block persists. It looks like the back-end organization/workspace permission evaluation disagrees with what the admin UI shows. Has anyone else hit this with the Trello MCP server, or can an Atlassian team member check the evaluation for my organization? I can provide the organization ID, the full consent URL, and screenshots (blocked consent screen, permissions pages, data policy) privately.

Note: I've tried twice to file this through the support contact form as well; the form itself failed both times at the submission stage, which is why I'm posting here.

Ciro

Hi!

That exact wording ("these workspaces", plural) isn't on Atlassian's Trello MCP troubleshooting page. The closest documented message, "Permissions are blocked for this workspace", is tied only to Read or Write being blocked for the MCP server, and you've already ruled that out. So I'd split the problem in two:

1. Run the same consent from a client on Atlassian's supported domain list, like Claude or ChatGPT, with the same workspace. agent.meta.ai isn't on that list, so it only gets in through your custom domain entry. If Claude or ChatGPT gets past the consent screen, the block is tied to the client. If they hit the same banner, it's on the account or workspace side.
2. Check which organization owns the workspace. The Trello MCP docs say permissions can be disabled when you pick a workspace your organization doesn't own. They only name Inbox and Planner there, and boards and cards should still connect, but it's the one documented case where ownership changes the result.

Someone reported the same plural message with a different custom client two weeks ago (this thread), and it went unresolved. If step 1 fails with Claude or ChatGPT too, say so in the ticket: it points away from your settings.