rea
Reverse engineer anything with agents, from app behavior down to native binaries.
CLI framework and stdio MCP server for Flutter: scaffolding, hot reload, REPL, codegen.
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 Dowel
El autor aún no ha puesto cómo instalarlo en el registro MCP
ChatGPT todavía no puede conectar Dowel
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 Dowel
El autor aún no ha puesto cómo instalarlo en el registro MCP
Cursor todavía no puede conectar Dowel
El autor aún no ha puesto cómo instalarlo en el registro MCP
VS Code todavía no puede conectar Dowel
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-dowel)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.0) 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 Dowel | 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.
Dowel
One binary for your Flutter dev loop and your AI agent.
Start, hot reload and inspect a running app, scaffold code, install plugins transactionally, and hand the same commands to your agent through a built-in MCP server.
Documentation · pub.dev · Issues
| Fact | Value |
|---|---|
| Package | dowel |
| Install | dart pub add dowel, then dart run dowel install |
| Import | package:dowel/dowel.dart |
| Entry points | dart run dowel , ./bin/dowel, runDowel, DowelCommand, DowelServiceProvider, PluginInstaller, ./bin/dowel mcp:serve or dart run :dispatcher mcp:serve (substrate and plugin tools), dart run dowel:mcp (substrate tools only) |
| Platforms | macOS and Linux for the lifecycle commands (start, stop, reload, ...); the rest of the CLI and the MCP server run wherever Dart does |
| Requires | Dart >=3.13, Flutter for the app you drive |
| Dependencies | args, dart_mcp, vm_service, yaml_edit, xml, crypto, path, meta, stream_channel, yaml |
| License | MIT |
dart pub add dowel
dart run dowel install
install writes bin/dispatcher.dart (the entry that calls runDowel), the codegen barrels lib/app/_plugins.g.dart and lib/app/commands/_index.g.dart, and builds the fast wrapper bin/dowel (about 0.2 s to start, against 0.4 to 2.7 s for dart run). Run it again and it skips every file that already exists (--force overwrites them) and keeps the dowel constraint your pubspec already has: install adds dowel: ^ only when the pubspec declares none. It adds only the machine-local cache to .gitignore (.dowel/cli-bundle*, .dowel/build.stamp* and .dowel/.dowel.lock/), so commit .dowel/plugins.json and .dowel/installed/.
Moving an app from fluttersdk_artisan? install stops on the files that package generated and prints what to delete and the commands to run; doctor warns about the same leftovers. The steps are in Migrating from fluttersdk_artisan.
dart run dowel list # every registered command, grouped by namespace
dart run dowel doctor # preflight: Flutter and Dart on PATH, the default port
start launches flutter run detached and records the session per project under ~/.dowel/sessions/ /, so two apps can be driven at once and a command never acts on another project's app.
dart run dowel start --device=chrome
dart run dowel reload # hot reload, Dart state kept dart run dowel hot-restart # hot restart, Dart state dropped dart run dowel logs --follow dart run dowel stop
| Command | Effect |
|---|---|
start, stop, restart | Launch, tear down and relaunch the app; stop reaps the process group |
reload, hot-restart | Send r and R to the detached flutter run through a FIFO |
status, logs | Print the recorded session as JSON; print or follow the captured log |
tinker | A REPL (or --eval) that evaluates Dart in the running app over the VM Service |
A command that dials the running app (tinker among them) exits 75 while the app is still building, so a script can retry; any other non-zero code is a real failure.
make:command Greet scaffolds the class and registers it in the nearest provider. The signature string declares the arguments and flags:
import 'package:dowel/dowel.dart';
final class GreetCommand extends DowelCommand { @override String get signature => 'greet {name} {--shout}';
@override String get description => 'Greet a person by name.';
@override CommandBoot get boot => CommandBoot.none;
@override Future handle(DowelContext context) async { final name = context.input.argument('name') ?? 'world'; final greeting = 'Hello, $name'; context.output.success( context.input.option('shout') == true ? greeting.toUpperCase() : greeting, ); return 0; } }
A command that the signature cannot express overrides configure(ArgParser) instead. Two providers registering the same command name fail at boot with DowelCommandCollisionException.
dart pub add awesome_plugin
dart run dowel plugin:install awesome_plugin --dry-run # preview every operation dart run dowel plugin:install awesome_plugin
A plugin describes its install footprint in an install.yaml manifest, or in code with the PluginInstaller DSL when it needs branching. Either way the installer stages every operation and writes nothing until the commit, writes through a .tmp file and a rename, skips what is already in place, and records each applied operation under .dowel/installed/ .json, so plugin:uninstall can reverse it. The reversal removes the files an install wrote, the dependencies it added and the plugin's registry entry; a dependency the project already declared stays, and edits injected into existing files (InjectImport, InjectAfterPattern) are logged as skipped, so remove those by hand. An install record written by an older dowel is refused until plugin:install --force rewrites it, and plugin:install refuses to run when lib/app/_plugins.g.dart registers providers but .dowel/plugins.json is missing: restore it from version control.
| Piece | Where it lives |
|---|---|
| Manifest: files to copy, provider and config wiring, Android, iOS, macOS and web edits, env vars, prompts | install.yaml in the plugin package |
Procedural escape hatch: writeFile, injectImport, injectProvider, injectAndroidPermission, injectEnvVar, ... | DowelInstallCommand subclass driving PluginInstaller |
| The plugin's commands | A DowelServiceProvider exported from package: /cli.dart |
A plugin without a manifest is registered directly in .dowel/plugins.json and needs the scaffold from dowel install. make:plugin generates a plugin package with all of this wired.
./bin/dowel mcp:install # or: dart run dowel mcp:install
mcp:install writes the dowel entry into .mcp.json; reconnect your client once (Claude Code: /mcp reconnect dowel). The server speaks stdio JSON-RPC and exposes the substrate tools plus whatever the installed plugins contribute:
| Tool | Does |
|---|---|
dowel_start, dowel_stop, dowel_restart | Run the app lifecycle |
dowel_reload, dowel_hot_restart | Apply a code change to the running app |
dowel_status, dowel_logs, dowel_doctor, dowel_list | Read the session, the log (returned in the tool result), the toolchain and the command list |
dowel_tinker | Evaluate a Dart expression in the running app; a blank eval is a usage error |
dowel_start and dowel_restart take every option their CLI commands take. Without a running app the server stays up with the substrate tools and reconnects on the next call that needs the VM Service, after the app restarts too. A filter (.dowel/mcp.json, then DOWEL_MCP_* variables, then mcp:serve flags) allows or denies tools and packages; a deny wins at every layer.
| Namespace | Commands |
|---|---|
| Lifecycle | start, stop, status, logs, restart, reload, hot-restart |
| Scaffolding | install, make:plugin, make:command, make:fast-cli |
| Plugin management | plugin:install, plugin:uninstall, plugins:refresh |
| MCP | mcp:serve, mcp:install, mcp:uninstall |
| Introspection | help, list, doctor, tinker |
| Codegen | commands:refresh, test:bundle |
Rules for an agent working with this package. Each one is a mistake the maintainers already made once.
| Do | Because |
|---|---|
Run dart run dowel install once before plugin:install for a plugin without an install.yaml | The command registers into lib/app/_plugins.g.dart and stops without it |
Preview with plugin:install --dry-run before the real run | File writes swap in through .tmp files after staging, but dependency and injection edits write directly and are not rolled back (a failed install then reports rolledBack: false and leaves a partial record), and a conflict with a user-edited file needs a decision (a dry run returns before the conflict check, so it does not detect conflicts) |
Commit .dowel/plugins.json and .dowel/installed/; ignore only .dowel/cli-bundle*, .dowel/build.stamp* and .dowel/.dowel.lock/ | The registry regenerates lib/app/_plugins.g.dart; without it on a fresh clone plugin:install refuses to run |
Leave *.g.dart barrels alone; regenerate with commands:refresh and plugins:refresh | They are generated, a hand edit is overwritten |
Start the app with dowel start, not flutter run | Reload, restart, logs and tinker find the app through the recorded session |
In a git worktree, run dowel start there (or pass --state= ) before any command that uses the session (reload, stop, tinker, a plugin's :*) | The ownership check passes when the worktree sits inside the project root the main app recorded (an app at the repo root, the worktree under it) and for state with no recorded projectRoot; the command then acts on the main app and reports success. A sibling checkout, or an app in a subdirectory the worktree is not inside, is refused. MCP plugin tools and dowel_tinker run no such check. An MCP server resolves the session from its own working directory and falls back to the shared ~/.dowel/state.json pointer when that project has none, so it can reach the main app; run these from a shell inside the worktree. --state= skips the check, and a missing or unreadable file falls back to that pointer, so confirm the file exists and holds the intended projectRoot |
Reconnect the MCP client after mcp:install or a change to .dowel/mcp.json | Clients do not reload a server entry on their own |
Use ./bin/dowel mcp:serve (or dart run :dispatcher mcp:serve) for plugin tools | dart run dowel:mcp loads only the substrate tools |
Read the exit code: 75 means retry, anything else non-zero is a failure | The app may still be building |
Never treat bin/dowel.dart as a project wrapper | It is this package's own entry point; the wrapper is bin/dispatcher.dart |
dart_mcp for the MCP server, vm_service for the connection to the running app, args for command-line parsing, yaml and yaml_edit for manifests and in-place edits, xml for Android and Apple platform files, crypto for the install-record hashes. Dowel itself is pure Dart; the app you drive needs Flutter.