https://mcp.atlassian.com/v2/mcp) with your Atlassian account, so the agent acts in Atlassian as you.
An admin of your Atlassian organization must allow Aether before anyone in it can connect. Atlassian blocks Aether until they do. See Allow Aether in Atlassian.
Allow Aether in Atlassian
Atlassian lets an organization admin decide which apps may connect to its MCP server. By default it allows only the apps on Atlassian’s own list, and Aether is not on it. Until an admin allows Aether, connecting stops on an Atlassian page that reads:Access to this domain is restricted. Your admin has blocked this domain “https://app.runaether.dev/settings/integrations/mcp/callback” in your organization’s settings.An Atlassian organization admin allows Aether once, for the whole organization:
- Open Atlassian Administration and select the organization that owns your Jira or Confluence site.
- Go to Connectors → Atlassian MCP server. Some organizations have it under Rovo → Rovo MCP server → Domain settings.
- Select Add domain and enter
https://app.runaether.dev/**. - Save, then connect again from Aether.
If Atlassian still blocks the connection
- Add the entry again. Delete
https://app.runaether.dev/**, add the same entry, and save. Atlassian describes entries that show in the list before they apply. - Check the organization. An admin of several Atlassian organizations has one list per organization. The entry belongs in the organization that owns the site you are connecting.
- Turn off “Allow Atlassian supported domains”, then add the entry again. This cleared the block for an admin whose entry was otherwise ignored, and an open Atlassian issue describes the same block with the option on. With the option off, the apps on Atlassian’s own list can no longer connect to your organization, so decide that with your team.