microsoft / microsoft/DebugMCP

Feature Request: Please add flutter/dart to the fully supported list

Open
#126 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
511
Forks
60
Avg merge
2d 1h
Merged PRs (30d)
18

Description

Right now it appears to work to a certain extent. But I'm not sure it's fully working because the AI has a ton of trouble with it:

  1. AIs can't figure out that a session is already running properly
  2. They can't seem to start a session reliably (because they take a long time to start a head). It's as if they can't get the status of starting the session and because they can't read the debug console in vs code, they can see that it's still starting. (not sure why vs code doesn't allow reading the debug console!).
  3. Once they get into a session they often fail to use the tooling effectively although they confirm that they have access to the mcp and can use the tools.

I'm not sure that 1 and 2 aren't a global improvement to the mcp that couldn't be made to give status and lookup existing sessions and teach them how to do this before they start another debug session, but it sure rears it's head on flutter more than C#. And adding access to the debug console here would be hugely powerful because with flutter, this is where inline errors that don't get trapped on code execution go.

I'm happy to do testing and feedback on this.

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the MCP session lifecycle and the VS Code debug-console integration described in the issue, then check how Flutter sessions and tooling are currently handled. Done means Flutter/Dart sessions can be detected, started, and monitored reliably, with useful debug-console access and effective MCP tooling confirmed through testing.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
devtools, mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.