TechFixSignal
Cursor

Cursor Unable to Reach the Model Provider

When Cursor shows Unable to reach the model provider, disable MCP servers in Tools & MCP first. This is not the Connection failed HTTP/1.1 path.

Reviewed by TechFixSignal EditorialSee how this guide is verified

Last checked
Sep 7, 2026
Applies to
Windows, Mac, Desktop
Fix status
Community Confirmed
Fastest useful check

Quick answer

Match the title Unable to reach the model provider, often with We're having trouble connecting to the model provider. This might be temporary - please try again in a moment. Open Cursor Settings → Tools & MCP and turn off every MCP server, then start a new chat and retry the same model. If chat works with MCP off, re-enable servers one at a time to find the conflict. Do not start with HTTP Compatibility Mode HTTP/1.1 — that leftover belongs to the separate Connection failed banner.

On this page

What we're seeing

  • The exact title is Unable to reach the model provider. The detail line is often We're having trouble connecting to the model provider. This might be temporary - please try again in a moment.
  • Independent December 2025–January 2026 first-hand reports on the Cursor forum quote that title while a specific model or Agent mode fails and other models still work.
  • In those threads, turning off MCP servers under Tools & MCP restored the model, including cases where only Gemini, only non-Composer modes, or only Agent mode failed.
  • A different banner such as Connection failed. Please try again, or contact support is a different fingerprint. That path uses Network HTTP/1.1 leftovers, not MCP disable.
  • A pure usage-limit or rate-limit message is out of scope for this guide.

Start here

Try these first

Fix 1

Confirm Unable to reach the model provider

Community Confirmed

Match the provider title before changing MCP or network settings. Nearby Cursor connection banners need different leftovers.

  1. Read the error card. This guide is for Unable to reach the model provider, usually with the temporary try-again detail line.
  2. If the banner instead says Connection failed. Please try again, or contact support, stop here and use that separate TechFixSignal guide.
  3. Note which model and mode failed, and whether another model still works in the same window.
  4. Note whether any MCP servers are enabled under Tools & MCP.

Applies to Windows, Mac, Desktop

Fix 2

Disable MCP servers in Tools & MCP

Community Confirmed

Forum first-hand reports and Cursor staff replies for this exact title point to Tools & MCP first: turn MCP servers off, then retry in a new chat. That leftover is independent of HTTP Compatibility Mode.

  1. Open Cursor Settings → Tools & MCP.
  2. Turn off every enabled MCP server for this test.
  3. Start a new chat. Do not reuse a long stuck thread.
  4. Retry the same model and mode that failed.
  5. If the model answers with MCP off, keep MCP disabled as the working leftover for now.

Applies to Windows, Mac, Desktop

Fix 3

Re-enable MCP servers one at a time

Community Confirmed

First-hand reports often clear the banner after removing one conflicting MCP server such as Perplexity, Postman, Craft, or a local stdio server, while other servers can stay on.

  1. With chat working and all MCP off, turn on one MCP server.
  2. Open a new chat and retry the failing model.
  3. If the provider error returns, turn that server back off. That server is the conflict for this leftover.
  4. If chat stays healthy, enable the next server and repeat.

Applies to Windows, Mac, Desktop

Fix 4

Rule out the Connection failed twin

Community Confirmed

HTTP/1.1 and Disable HTTP/2 are the leftovers for Connection failed, not for this provider title. Use them only after MCP disable already failed and the banner text still matches Unable to reach the model provider with no MCP left to turn off.

  1. Confirm every MCP server is still off.
  2. If the provider title remains with MCP empty, compare a second network such as a phone hotspot.
  3. Only then consider network diagnostics as a separate branch. Do not treat HTTP Compatibility Mode HTTP/1.1 as the first leftover for this fingerprint.

Applies to Windows, Mac, Desktop

Device notes

Windows
Tools & MCP is under Cursor Settings on Windows. Prefer a new chat after disabling MCP, not Reload Window alone.
Mac
Same Tools & MCP leftover on macOS. Staff replies for Gemini and Perplexity MCP conflicts match this title.
Desktop
Agent mode and specific-model chat both appear in the first-hand reports. Composer-only success with MCP on is still this fingerprint.

Official information

Checked on 7 September 2026, Cursor staff replies on forum threads that quote Unable to reach the model provider tell people to turn off MCP servers under Tools & MCP, and first-hand reports confirm specific MCP servers as the conflict. Cursor does not publish a Help Center article that names this exact title as an MCP-conflict known issue. HTTP Compatibility Mode HTTP/1.1 belongs to the separate Connection failed banner, not this leftover.

Sources

Keep troubleshooting

Related problems