Dart_analyze MCP not responding

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When starting the agent, there are problems with the Dart MCP server. I update Dart, Flutter, Cursor, reload MCP Server in Cursor Settings. I can work with this chat only after stop agent (in this case agent not complete my task in 100%)

Steps to Reproduce

  1. Start agent
  2. Wait for MCP use

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.10.20
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. The screenshot shows the key detail: the analyze_files step is a tool call from your Dart/Flutter MCP server, not Cursor’s built-in error checking. You can tell by the MCP icon and the roots and paths arguments. Cursor is just waiting for that MCP tool to return. When analyze_files doesn’t respond, for example if the Dart analysis server is still warming up or the MCP process is stuck, the card will stay stuck on “analyzing”.

What to try:

  1. Update your Dart/Flutter SDK and the Dart MCP server dart mcp-server to the latest version. analyze_files often hangs while the analysis server is initializing.
  2. Reconnect the MCP server in Settings → MCP: turn the toggle off and back on, after the SDK has finished warming up.
  3. Run the same task with Dart MCP disabled. If the end-of-turn hang goes away, that points to this tool as the cause.

Your Stop → continue workaround makes sense. It cancels the stuck call and lets the agent continue. One important note: MCP calls don’t have a short timeout right now, so if a tool doesn’t respond, Cursor can wait for a long time. This is a known limitation and there’s no ETA yet.

Let me know if disabling Dart MCP helped narrow it down.