Hey, thanks for the report. This looks like a known issue where certain MCP servers can conflict with specific models.
There’s a similar case that was fixed by removing a problematic extension: Unable to Reach Model Provider for All Models Except Composer1
To help diagnose, could you try:
- Test in a clean profile:
cursor --user-data-dir="CursorData/Test"
Open your project, then try Gemini, Grok, and Sonnet with the Perplexity MCP enabled. Does it work?
- If it works in the test profile, check extensions:
- Help > Toggle Developer Tools > Console, and look for errors when you send a request
- Try disabling extensions one by one and re-test
- Collect diagnostics:
- The Request ID from a failed request with Gemini, Grok, or Sonnet
- A screenshot from Developer Tools > Console when the error happens
Let me know the results, especially from the clean profile test. That will help confirm whether this is an extension conflict or an issue in the Perplexity MCP server itself.