SSyncDev

Crumbs MCP Server

Lets an AI agent read a running Flutter app's HTTP traffic, logs, exceptions, debug prints and frame timings.

Local server

What is the Crumbs MCP Server?

Debugging a Flutter feature with an assistant tends to go the same way: a stack trace scrolls by, you paste it into chat, and the agent immediately asks what the server returned. Crumbs removes that relay. It records what the app does while it runs and lets the agent read it directly. The Crumbs MCP server is not a separate process; its crumbs_* tools ride on the dowel server, so your client entry is keyed dowel.

Crumbs only observes. It never taps, navigates or changes state, which is the job of its sibling, tapir.

What gets recorded

Watchers hook into package:logging, FlutterError.onError, debugPrint and the frame scheduler, chaining to any handler already installed (Sentry's, for instance). Each record goes into an in-memory ring buffer inside the app.

Buffer Agent tool
Log records crumbs_tail
Uncaught exceptions crumbs_exceptions
debugPrint output crumbs_dumps
Frame timings crumbs_frames
HTTP requests you route in crumbs_requests
Magic events, gates, queries, caches crumbs_events, crumbs_gates, crumbs_queries, crumbs_caches

Buffers keep the newest 500 records (3,600 for frames) by default. Calling crumbs_clear before reproducing a bug means the next read contains only that attempt.

Wiring it in

Add the package with flutter pub add crumbs, then run dart run crumbs crumbs:install. The installer patches lib/main.dart behind an !kReleaseMode guard and sets up the dowel harness. Start the app through dart run crumbs start rather than plain flutter run, because every tool dials the session dowel records. dart run crumbs mcp:install then writes the .mcp.json entry. Reconnect your client afterwards; it will not reload on its own.

HTTP capture is not automatic in the Crumbs MCP server setup. You call CrumbsStore.recordHttp from your own Dio or package:http interceptor. Requirements are Dart 3.13 and Flutter 3.47.

Secrets and sharp edges

  • Authorization headers, cookies, password and token fields are masked before buffering. Free text in logs is not, unless you set CrumbsRedaction.redactor.
  • Ship it behind the release guard. Anyone who reaches the VM Service of a build carrying crumbs can read every buffer.
  • An empty exception buffer proves nothing if you wired by hand and skipped ExceptionWatcher.
  • The on-disk file sink needs a native target, not web.

For neighbouring tools, see Flutter Inspector, Xcode Diagnostics, or the full list of mobile development servers.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
crumbs_tailRead package:logging records; supports since and logger filters with a cursor.
crumbs_exceptionsRead uncaught Flutter and platform exceptions.
crumbs_dumpsRead debugPrint output.
crumbs_framesRead frame timings and build attribution.
crumbs_requestsRead recorded HTTP requests.
crumbs_eventsRead in-app events (Magic apps); supports since and type.
crumbs_gatesRead gate checks (Magic apps).
crumbs_queriesRead DB queries (Magic apps).
crumbs_cachesRead cache operations (Magic apps).
crumbs_clearEmpty every buffer so the next read covers a single action.

How to install the Crumbs MCP Server

{
  "mcpServers": {
    "dowel": {
      "command": "./bin/dowel",
      "args": [
        "mcp:serve"
      ],
      "cwd": "."
    }
  }
}

The crumbs tools are served by dowel. The launcher path is relative to your Flutter project; run dart run crumbs mcp:install first. Without the ./bin/dowel launcher (or on Windows) the entry is dart run crumbs mcp:serve.

Frequently asked questions

No. Records are captured in memory inside your app and read over the VM Service; there is no proxy and no SaaS account.