Troubleshoot Trello MCP connection errors
Trello MCP enables AI tools, like Claude or ChatGPT, and other MCP-compatible tools to securely connect to your Trello workspace. Here's how Trello MCP works:
Trello data is only available through Trello MCP for now - it is not accessible through the Atlassian Rovo MCP server
Each MCP connection currently supports only one Trello workspace at a time.
Admin controls for Trello MCP, including domain restrictions and permissions, are managed under the Atlassian Rovo MCP server settings in Atlassian Administration
Even though the settings page refers to "Atlassian Rovo MCP server," these controls also apply to Trello MCP connections. Changes made there will impact both.
"Access to the domain is restricted"
This error occurs when a user attempts to connect an AI tool to Trello MCP, but the tool's domain has been blocked by the organization administrator. Contact your organization admin and request that the MCP client's redirect domain be allowed.
To allow Atlassian-supported domains:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Rovo > Rovo MCP server.
Select Allow Atlassian supported domains.
To add a custom domain:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Rovo > Rovo MCP server.
Select Add domain.
"Permissions are blocked for this workspace"
This error appears when a specific permission type (Read, or Write) has been blocked for the MCP server.
To update permissions:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Rovo > Rovo MCP server.
Select the Permissions tab.
Use the checkboxes to set the relevant permissions to Allowed:
Permission | What it controls |
|---|---|
Read | Whether the server can view and read data |
Write | Whether the server can create and modify data |
To configure permissions per app (for example, allow Read for Trello but block Write), select Edit details on the permission row. Changes take effect immediately.
"You don't have permission to connect from this IP address"
This error appears when the user's IP address is not included in the organization's IP allowlist.
IP allowlisting is managed in Atlassian Administration, not in the Rovo MCP server settings.
To update your IP allowlist:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Security > Device security > IP allowlists.
Add the user's IP address or range.
For more details, see here.
Things to know about IP allowlisting and MCP:
For a tool call to succeed, the request must come from an allowed domain and from an allowed IP address
Some AI tools set their own outbound IP addresses - those IP ranges may also need to be added to the allowlist
The user's network must be able to reach
*.atlassian.netfor interactive widgets to render.
"Access denied: Your organization admin has not authorized the [permission name] permission"
This error appears when a user tries to perform an action (read, or write) that the org admin has specifically blocked.
To resolve this, follow the steps under "Permissions are blocked for this workspace" above.
"We are having trouble verifying your organization permissions"
This error appears when the system cannot determine which organization the user belongs to.
To troubleshoot:
Verify you're signed in with the correct account - Open your Atlassian account profile and confirm the email address shown matches the one managed by your organization. If you're signed into the wrong account, sign out and sign back in with the correct email.
Check the user is accessing Trello with the correct email address (the one managed by the org).
If the issue persists, contact Trello support.
For Organization Admins: In the Atlassian Administration hub, navigate to Directory > User accounts and confirm the user's account is listed and managed under your organization. .
"No Trello workspaces found"
This error appears when the account you're signed into doesn't belong to any Trello workspace.
To resolve this:
Confirm you're signed in with the correct Atlassian account - the one that has Trello access.
Try signing in with a different account using the link on the error screen.
If you don't have a workspace yet, create or join one at trello.com.
"No workspace available" - Inbox and Planner only
This appears when your account has Trello access but isn't a member of any workspace. The Accept button is disabled for workspace-level access, but you can still connect Inbox and Planner.
To get full access:
Join or create a Trello workspace at trello.com.
Retry the MCP authorisation flow.
"You no longer have access to this workspace"
This error appears when your membership to the selected workspace has been revoked.
To resolve this:
Use the "Authorize access for" dropdown to select a different workspace you still have access to.
If you need access to the original workspace, contact the workspace admin to be re-added.
"Inbox and Planner permissions are disabled" (info banner)
This is an informational notice, not an error. It appears when the selected workspace is not owned by your organization. You can still proceed with the connection - boards, cards, and lists will work normally. Inbox and Planner features are only available for workspaces managed by your organization.
"Something went wrong" - permissions failed to load on the consent screen
When authorising an MCP connection, the consent screen at auth.atlassian.com/consent may display an error in the Permissions section. When this error appears, the Accept button is disabled, and the authorisation cannot be completed.
This error occurs when the consent screen fails to load the permission scopes for the MCP client - usually due to a temporary service issue or a misconfiguration in the MCP client's OAuth registration.
To resolve this:
Refresh the page : In most cases, a page refresh resolves the issue. Close the consent screen and retry the authorisation flow from your MCP client.
Try a different browser or incognito window : Browser extensions or cached session data can sometimes interfere with the consent screen loading correctly.
Check your MCP client configuration : Ensure the redirect URL and client credentials in your MCP client's config file are correct and up to date.
If the error persists across multiple attempts, contact Trello support.
Need help? Contact Trello Support or visit the getting started guide.
Was this helpful?