I am trying to connect an AI client (Muse, by Meta) to the Trello MCP server for read-only tracking of my boards in the Trello workspace "Tim Kretschmann's workspace". The OAuth flow (authorization code + PKCE, dynamic client registration, public client) reaches the consent screen at auth.atlassian.com/consent, the workspace is selectable, but the screen shows "Permissions are blocked for these workspaces" and the Accept button stays disabled.
I followed your "Troubleshoot Trello MCP connection errors" page end to end. Verified state of my organization (pageantcast — my only organization), checked by screenshot on Nov 11, 2026:
- Connectors → Atlassian MCP server → Domains: "Allow Atlassian supported domains" is ON; custom domain https://agent.meta.ai/** added (the client's redirect is https://agent.meta.ai/api/hatch/oauth/callback).
- Permissions tab: Read 17/17 Allowed ("Allow all toolsets", new toolsets allowed) — the Read detail list includes read_trello, switched on; Write 17/17 Allowed; Search 4/4 Allowed. (Your doc says changes take effect immediately; the block persisted unchanged for 6+ hours after these were set.)
- Authentication tab: defaults — users connect with OAuth 2.1; API token authentication off; enterprise managed authentication off.
- Directory → Users: Total users 1 (me, organization admin, Active). Managed accounts: 0. My account (pageantcast@gmail.com) is badged "External user" — a gmail address cannot be a domain-claimed managed account.
Client details: authorization server https://auth.atlassian.com/VCeDsk8ZHncYF1g234fKtc4lNipbBhu3 (per the MCP server's protected-resource metadata); registration endpoint …/dcr/register; scopes requested: read:board:trello read:organization:trello read:member:trello offline_access (all present in the server's published scopes_supported). Note: earlier the same day, dynamic registration itself intermittently failed ("The provider rejected the automatic app registration") before succeeding — consent attempts for log correlation: Nov 11, 2026 at ~10:31 AM and ~4:31 PM America/Chicago.
Ask: Please check server-side which permission evaluation blocks this consent. My suspicion is the external/unmanaged status of the account: every documented remedy assumes the org's settings govern the connecting user, but this org has zero managed accounts. What is the correct configuration for an org admin who is an external (gmail) user connecting his own personal Trello workspace — or is this a defect in the consent evaluation?