IP ranges for mcp.atlassian.com

Zheng, Rox

Hi Atlassian team,

Could you please provide the official IP addresses or CIDR ranges for accessing mcp.atlassian.com over HTTPS (TCP port 443)?

We need to allow outbound traffic from our application server through our corporate firewall.

Thank you!

Sami Shaik

@Zheng, Rox there is no separate published range for mcp.atlassian.com, so here is what you can actually give your firewall team.

1. The official source is the machine-readable list, not a fixed set of addresses. Atlassian publishes all of its ranges at https://ip-ranges.atlassian.com (JSON). The feed generated on 27 October 2026 has 173 entries, each tagged with direction (ingress or egress), region, perimeter and product. The product tags are jira, confluence, bitbucket, forge, rovo-crawler, opsgenie, trello, loom, statuspage, email, halp and github-for-jira. There is no mcp tag, and the Remote MCP Server setup page does not list any network or allowlisting guidance either. In other words, Atlassian has not told anyone which CIDRs sit behind mcp.atlassian.com specifically.

2. For your direction of traffic (your server out to Atlassian) the relevant entries are the ones tagged ingress. The IP addresses and domains page says Atlassian apps and sites do not have fixed individual IP addresses, that new addresses appear over time, and that the list is “created for machine consumption” so you can update rules programmatically. It also advises against allowlisting only the ranges of one region. So if your firewall must have CIDRs, take every ingress entry with perimeter: commercial and schedule a job that re-reads the feed; a one-time copy will break on the next change.

3. The approach that survives those changes is a hostname rule on your egress proxy. Allow mcp.atlassian.com on 443, and *.atlassian.com for the OAuth 2.1 sign-in the MCP client performs on first connection (the domains table on the same page lists *.atlassian.com as used by all Atlassian apps). Most enterprise firewalls can do FQDN-based rules for exactly this case, and it removes the maintenance burden entirely.

4. If your security team needs a written statement for mcp.atlassian.com, raise it with Atlassian Support and ask them to confirm which product tag covers the MCP endpoint. That answer would help a lot of people, so if you get it, please post it back here.

References, read today: IP addresses and domains for Atlassian cloud products, Getting started with the Atlassian Remote MCP Server.