[BUG] claude.ai visualize feature broken — claudemcpcontent.com unreachable (DNS_PROBE_FINISHED_NXDOMAIN) --- PLEASE REVIEW!

This was filed using the Claude Code form because no claude.ai-specific form exists, but this bug occurs in the claude.ai web browser interface, not Claude Code CLI. Please re-evaluate — the visualize MCP feature is broken for browser users and claudemcpcontent.com is unresolvable. This is a valid bug report.

I have the same issue Failed to set up MCP app for "visualize" Check that claudemcpcontent.com is not blocked by your network or browser

‘Same issue happened to me as well. "Failed to set up MCP app for "visualize". Check that claudemcpcontent.com is not blocked by your network or web browser". Not sure how to solve it.....

Same issue to me! This is a valid bug! Please fix it...

same issue

Same issue

+1

I have the same issue with the latest version of the Claude App on MacOS (latest build).

The same problem is intermittent and keeps recurring.

Update: the issue is now affecting the Figma MCP connector as well, with the identical error: 'Failed to set up MCP app for Figma. Check that claudemcpcontent.com is not blocked by your network or browser.' This confirms the problem is with claudemcpcontent.com infrastructure broadly, not just the visualize feature.

when i ask claude (web and app) to create a diagram, the same problem occur

Same issue

Same issue

Same issue

Same issue

The issue is due to the pop-up blocker; if you disable it. The Visualize is working!

Same issue

The issue is due to the pop-up blocker; if you disable it. The Visualize is working!

Disabling the pop-up blocker is not the issue here. Chrome pop-ups are already set to allowed, and claudemcpcontent.com still returns DNS_PROBE_FINISHED_NXDOMAIN — the domain does not resolve at all, regardless of pop-up settings. This is a DNS/infrastructure issue, not a browser blocking issue.

Same issue

Same issue happening on Claude for Windows desktop app. Sometime the visualization is rendered, sometimes this same error occurs. The error persisted after several app restarts. I upgraded to Version 1.1.9669 (aea25d) but still getting error. Interestingly, after a while (half hour) , the visualizations did render. But I am now getting same error again.

Failed to set up MCP app for "visualize". Check that claudemcpcontent.com is not blocked by your network or browser

有没有什么解决办法

switch over the Internet Service Provider (ISP)， then it is work.

same issue. I am in Italy. I have tried also with vpn and still not work

Same issue

Same issue

+1
Same issue

+1

+1 , Switch to mobile hotspot instead of Wi-fi and it worked for me , try this out for yourself

Same issue in claude.ai

+1

Same issue

Same issue
claudemcpcontent.com. does not have any IP addresses.

+1 reproducing in CZ as of 22 Apr 2026.

• Region: Prague, CZ
• Setup: Claude.ai web + desktop app
• Model: Opus 4.7

nslookup claudemcpcontent.com 8.8.8.8
→ Server: dns.google (8.8.8.8)
→ Returns Name without Address (no A record)

nslookup -type=A claudemcpcontent.com 8.8.8.8
→ Same result, no IP

Same NXDOMAIN behavior from Google DNS, corporate DNS, and 1.1.1.1.
visualize:show_widget tool unusable.

+1

+1

Same problem here, affecting a prompt that tries to access Atlassian and visualiser.

Same issue in India as well

+1

+1

+1 Australia
Just using the free tier claude.ai. Trying to render mockups

+1

+1

++

+1

Also having this issue

+1

+1

+1 just started happening for me today on Chrome browser on my Ubuntu laptop. It is working fine on the Android app with the same network connection.

I am experiencing the issue in the Chrome browser and the Mac app as well.

Same here Mac Chrome

same - In windows app

same problem in us

+1

+1

+1

Just FYI that this just occurred to me using Claude desktop. It was working 20m ago and then failed - I made no change to the config.

+1 still occuring. web version, free plan

Happens on Max plan on Web

it's back!

+1 on web and desktop

+1 web (edge) and app

Same. Just started to day using the Windows 11 Claude Client.

+1
Is that claude server's issue?

+1 on web

fahhh claude server selling

+1 on web

Is it okay to leave a problem unattended for several months in a paid service?

There's currently an issue impacting the availability of MCP applications on Claude.ai, including desktop and mobile.

Source:
https://status.claude.com/

Happening here as well - was working yesterday

The same issue happening in Japan as well!

Just FYI that this just occurred to me using Claude desktop. It was working 20m ago and then failed - I made no change to the config.

Status update: This issue is now gone for Claude desktop.

Still having the issue too

also still having the issue on desktop and web

+1
Same bug,

claude desktop, bug happening. not even doing anything resembling the work other people do; just chat

+1

+1

+1

same issue: 1.1.1.1 returns "No answer"

I have this issue as well, does anyone know if there is anything that can be done to mitigate on user-side? Hasn't worked for >72 hours and the Claude Desktop app intermittently blank screens when this happens and has to be force-closed.

Having the same issue on claude desktop

Thought i was going crazy. same issue

+1 happening for me as well on Mac desktop app. Was able to circumvent by using Claude.ai in the Safari browser.

Why is this issue still open and not fixed yet? It has been 2 months.

nothing is resolved yet for this feature !

It has been almost a week since this problem started appearing very consistently on Claude Desktop (v1.8555.2) on Windows 11. I tried claudemcpcontent.com in the browser and it returned the same error mentioned on this page: DNS_PROBE_FINISHED_NXDOMAIN.

Is there any workaround for this?

Same issue here. Fine earlier today then suddenly simple HTML canvases/playground/widgets don't render, with a toast notification of this error

Confirming this issue on Windows 11.

I investigated the DNS resolution for claudemcpcontent.com and observed the following:

Resolve-DnsName claudemcpcontent.com
Resolve-DnsName claudemcpcontent.com -Type A
Resolve-DnsName claudemcpcontent.com -Type AAAA
nslookup -type=A claudemcpcontent.com

All queries return only the SOA record:

Name                        Type TTL   Section    PrimaryServer
----                        ---- ---   -------    -------------
claudemcpcontent.com        SOA  ...   Authority  isla.ns.cloudflare.com

No A or AAAA records are returned, and nslookup does not return an IP address.

When Claude attempts to render a visualization, I receive:

Failed to set up MCP app for "visualize". Check that claudemcpcontent.com is not blocked by your network or browser.

Opening claudemcpcontent.com directly in Chrome also fails with DNS-related errors (DNS_PROBE_POSSIBLE).

Based on these results, the domain appears to exist and be delegated to Cloudflare, but it is not resolving to a host address from my location.

this looks like an issue with cloudflare not resolving the hostname. Should be a quick fix for whomever manages Anthropics cloudflare backend.

I'm getting the same error for the Atlassian MCP:

``Failed to set up MCP app for "Atlassian". Check that claudemcpcontent.com is not blocked by your network or browser.``

+1 Claude Desktop v1.15200.0

Same problem with resolving claudemcpcontent.com when I am using Desktop Commander MCP. Very frustrating.

Solution

Simply rename the entry in claude_desktop_config.json to a non-conflicting name, e.g. my-desktop-commander or dc-local:

{
  "mcpServers": {
    "my-desktop-commander": {
      "command": "npx",
      "args": ["@anthropic-ai/desktop-commander"],
      "transport": "stdio"
    }
  }
}

After renaming, reload the configuration and the MCP server will connect normally. The functionality is unaffected — Claude Desktop only uses the command/args to launch the process; the server name is purely an identifier.

Symptom

Configuring a desktop-commander MCP server with stdio transport in claude_desktop_config.json fails to connect, with the following error:

Failed to set up MCP app for "desktop-commander". Check that claudemcpcontent.com is not blocked by your network or browser.

Root Cause

Claude Desktop scans the connector directory for MCP app registrations at startup. When an MCP app's name exactly matches a user-configured MCP server name, the app prioritizes it as an MCP App (loaded as a sandboxed iframe via claudemcpcontent.com) rather than a user-defined stdio MCP server.

desktop-commander happens to be registered as an MCP App in the official connector directory, creating a name collision. Claude Desktop attempts to load it as a sandboxed iframe, ignoring the user's local stdio transport configuration entirely.

same issue on my claude code desktop with version 1.20186.0 (d7731e) 2026-07-09T06:13:11.000Z