rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Read a running Flutter app's HTTP, logs, exceptions, dumps and frames over MCP. Debug builds only.
Skills que enseñan a la IA este tipo de trabajo; funcionan junto a este
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 6/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 12/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 0/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 18/100 |
Calidad: Pasó 3/3 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Elige la app de IA que usas y copia la configuración.
Pasó 3/3 revisiones · Funciona en tu computadora
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Claude todavía no puede conectar Crumbs
El autor aún no ha puesto cómo instalarlo en el registro MCP
ChatGPT todavía no puede conectar Crumbs
El autor aún no ha puesto cómo instalarlo en el registro MCP
B · Otros en Herramientas para desarrolladores que funcionan con ChatGPT
Elegidos entre los más usados de la misma categoría, solo los que se conectan con una dirección y sin clave
Claude Code todavía no puede conectar Crumbs
El autor aún no ha puesto cómo instalarlo en el registro MCP
Cursor todavía no puede conectar Crumbs
El autor aún no ha puesto cómo instalarlo en el registro MCP
VS Code todavía no puede conectar Crumbs
El autor aún no ha puesto cómo instalarlo en el registro MCP
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
La configuración JSON está en “Para desarrolladores”, abajo
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 19 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub anilcancakir, dueña del repo
Último cambio de código: ayer
Usa MIT
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/anilcancakir-crumbs)Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez ayer, y la última versión (1.1.1) llegó al registro ayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code.
En la misma categoría: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| Este Crumbs | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | En la nube o instalado en tu equipo |
| Necesita clave | No | No | No | No | No | No |
| Se añade con + en Claude | No | No | No | Sí | No | No |
| Revisiones básicas | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| Licencia | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Crumbs
Let your AI agent read what your Flutter app just did.
HTTP traffic, logs, uncaught exceptions, debug prints, events, gate checks, DB queries and cache operations, captured in memory while the app runs and read from one CLI and one MCP server. No stack traces pasted into the chat, no proxy, no SaaS account.
Documentation · pub.dev · Issues
crumbs is a passive inspector: it records what the app does and drives nothing. Watchers hook package:logging, FlutterError.onError, debugPrint and the frame scheduler, and call any handler set before them; the log watcher also turns on hierarchical logging and sets Logger.root.level to Level.ALL, so every log record reaches the buffer. HTTP adapters and the Magic watchers feed the rest. Every record lands in a ring buffer inside the app, and ext.crumbs.* VM Service extensions serve those buffers to crumbs:* commands and crumbs_* MCP tools on dowel. Its sibling tapir drives the app; crumbs reads what the app captured. crumbs is inspired by Laravel Telescope, which records the requests, exceptions, logs, queries, cache hits and events of a Laravel app into a queryable timeline; crumbs serves the same kind of timeline to a terminal and an AI agent instead of a web dashboard.
| Fact | Value |
|---|---|
| Package | crumbs |
| Install | flutter pub add crumbs, then dart run crumbs crumbs:install |
| Import | package:crumbs/crumbs.dart (CrumbsPlugin.install(), behind if (!kReleaseMode)) |
| Entry points | dart run crumbs , ./bin/dowel , CrumbsPlugin.install(), CrumbsPlugin.registerWatcher(), CrumbsPlugin.registerHttpAdapter(), CrumbsStore, CrumbsRedaction, CrumbsFileSink, CrumbsDowelProvider (package:crumbs/cli.dart), dart run crumbs mcp:serve |
| Platforms | Any Flutter target that exposes a VM Service in a debug or profile build: Android, iOS, macOS, Windows, Linux, and web for everything except the file sink: CrumbsFileSink imports dart:io with no conditional import, so the timeline on disk needs a native target and pub.dev shows no Web tag. On a Windows host mcp:install writes a dart run entry, never ./bin/dowel |
| Requires | Dart 3.13, Flutter 3.47; a plugin of dowel (^1.0.0) |
| Dependencies | dowel, logging, meta, the Flutter SDK |
| License | MIT |
flutter pub add crumbs
dart run crumbs crumbs:install dart run crumbs start --device=macos # dowel records the session every crumbs:* command dials dart run crumbs crumbs:tail
crumbs:install scaffolds the dowel harness when bin/dispatcher.dart is missing (including the fast ./bin/dowel launcher), registers crumbs as a dowel plugin, and patches lib/main.dart: the imports, WidgetsFlutterBinding.ensureInitialized() when missing, and an !kReleaseMode block that installs crumbs with the exception and dump watchers, placed before await Magic.init( on a Magic app and before runApp( otherwise. Re-running it changes nothing. Wired by hand, main.dart looks like this:
import 'package:crumbs/crumbs.dart';
import 'package:flutter/foundation.dart'; import 'package:flutter/widgets.dart';
void main() { WidgetsFlutterBinding.ensureInitialized(); if (!kReleaseMode) { CrumbsPlugin.install(); CrumbsPlugin.registerWatcher(ExceptionWatcher()); CrumbsPlugin.registerWatcher(DumpWatcher()); } runApp(const MyApp()); // MyApp is the host app's root widget. }
The guard belongs to the call site: crumbs installs none of its own. !kReleaseMode is what the installer writes: it keeps crumbs in debug and profile builds, and a frame measurement needs a profile build. A release build tree-shakes crumbs. Without a guard crumbs ships in release, and anyone who reaches that app's VM Service can read every buffer. --dart-define=CRUMBS_DISABLE=1 makes CrumbsPlugin.install(), registerWatcher() and registerHttpAdapter() return without installing anything, in a build that must not expose the extensions. The example/ app wires the core watchers and routes Dio traffic into the HTTP buffer.
On a Magic app, MagicCrumbsIntegration.install() from package:magic_devtools/crumbs.dart, called after Magic.init(), registers the Magic HTTP adapter, the model, cache, event, gate and query watchers, and, from magic_devtools 1.1.0, MagicLogWatcher for Magic's Log calls. A magic_devtools release built on crumbs ships the Magic integration (package:magic_devtools/crumbs.dart); the installer wires it when the resolved magic_devtools has that library, and otherwise warns and skips the Magic wiring, so Magic's buffers stay empty until you upgrade. An older release installs without MagicLogWatcher and the installer does not warn, so Magic's Log calls stay out of crumbs:tail.
| Record | Captured by | CLI | MCP tool |
|---|---|---|---|
package:logging records | LogWatcher, installed by CrumbsPlugin.install() | crumbs:tail | crumbs_tail |
Magic Log calls | MagicLogWatcher (magic_devtools 1.1.0 or later) | crumbs:tail | crumbs_tail |
| Uncaught exceptions | ExceptionWatcher (FlutterError.onError and PlatformDispatcher.onError, chained to any handler already set, such as Sentry's) | crumbs:exceptions | crumbs_exceptions |
debugPrint output | DumpWatcher (debug builds only unless allowInRelease is set) | crumbs:dumps | crumbs_dumps |
| Frame timings and build attribution | FramePerfWatcher | crumbs:frames | crumbs_frames |
| HTTP requests | The app's own interceptor (Dio, package:http) calling CrumbsStore.recordHttp, or a CrumbsHttpAdapter; on Magic, MagicHttpFacadeAdapter | crumbs:requests | crumbs_requests |
| In-app events | MagicEventWatcher | crumbs:events | crumbs_events |
| Gate checks | MagicGateWatcher | crumbs:gates | crumbs_gates |
| DB queries | MagicQueryWatcher | crumbs:queries | crumbs_queries |
| Cache operations | MagicCacheWatcher | crumbs:caches | crumbs_caches |
| Model lifecycle | MagicModelWatcher | none (CrumbsStore.recentModels() in the app) | none |
crumbs:clear and crumbs_clear empty every buffer, which turns the next read into the output of one action. Each buffer keeps the newest 500 records by default and the frame buffer 3600; CrumbsStore.setCapacity() changes one or all of them. A read returns records oldest first. crumbs:tail and crumbs:events take --since, --json and --follow to stream a buffer from a cursor.
| Surface | Behaviour |
|---|---|
| Credential masking | Records are masked by key before they are buffered, with no setup: Authorization, Cookie, X-Api-Key and similar headers, password, token style keys in a JSON or form request or response body, credential-named parameters in the URL query (access_token, api_key, the X-Amz-* signature of a presigned URL), and the same keys inside the Map elements of a query's bindings and a gate check's arguments, read ******** (a positional binding has no key, so only a text redactor can mask it, and it sees the bare value). Extend the lists with CrumbsRedaction.hideRequestHeaders(), hideRequestParameters() and hideResponseParameters() |
| Text redactor | CrumbsRedaction.redactor, a String Function(String) you set, runs at insert over the free text of a log, event, exception and HTTP record, a dump's message, a query's SQL and bindings, and a gate's arguments and user id. Without one, a credential written into a log line, a debugPrint or a SQL literal is buffered as written; model attributes and cache records are never masked. A redactor that throws drops the record rather than let it through unmasked; the log, event, exception and HTTP records carry a read-only redacted flag |
| File sink | CrumbsFileSink.start(directory: ...) writes a rotating JSONL timeline of log, event and exception records, and writes only records whose redacted flag is true. Read it back with crumbs:files |
CrumbsRedaction.redactor = (String text) => text.replaceAll(RegExp(r'\b\d{13,19}\b'), '[card]');
await CrumbsFileSink.start(directory: '${supportDir.path}/crumbs'); // supportDir is the host's choice.
The crumbs_* tools ride on the dowel MCP server, so the client config key is dowel. dart run crumbs mcp:install writes the entry into .mcp.json: ./bin/dowel mcp:serve when the fast launcher exists on a POSIX host, and dart run crumbs mcp:serve otherwise. Standard config for any client that reads .mcp.json:
{ "mcpServers": { "dowel": { "command": "./bin/dowel", "args": ["mcp:serve"], "cwd": "." } } }
| Client | Install |
|---|---|
| Claude Code | claude mcp add dowel -- ./bin/dowel mcp:serve, then /mcp reconnect dowel after a change |
| Cursor | .cursor/mcp.json (project) or ~/.cursor/mcp.json (user) |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Claude Desktop | claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\) |
A typical agent session, the app started with dowel_start and driven by hand or by tapir:
crumbs_clear {}
crumbs_requests {"limit": 20} crumbs_exceptions {} crumbs_tail {"level": "WARNING"} crumbs_queries {}
| Without crumbs | With crumbs |
|---|---|
| A stack trace scrolls past in the console; you copy it into the chat, then the agent asks for the HTTP response that caused it. | The agent calls crumbs_exceptions and crumbs_requests and reads both itself. |
You add print calls, hot reload and retry to see what the app sent. | The agent calls crumbs_clear, the action runs again, and the next read holds only its records. |
| Do | Because |
|---|---|
Install crumbs only behind if (!kReleaseMode) | Anyone who reaches the VM Service of a build that carries crumbs can read every buffer |
Start the app with dart run crumbs start or ./bin/dowel start, not flutter run | Every crumbs:* command and crumbs_* tool dials the session dowel records |
Call crumbs_clear before a repro | A buffer holds the whole run, so an old record reads like a new one |
Register ExceptionWatcher (and DumpWatcher) when wiring by hand | CrumbsPlugin.install() installs only LogWatcher; an empty exception buffer otherwise proves nothing |
| Read livenessCounter with an empty crumbs_frames answer | A counter that does not