Hexforge Gateway

Communauté Productivité

APK reverse engineering workspace that orchestrates jadx, apktool, adb and Frida through a workflow engine, on Termux (Android) or PC.

Installation

Les étapes d'installation sont dans la documentation ci-dessous. Documentation

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. HexForge Gateway
  2. Getting started
  3. Stack
  4. Documentation

HexForge Gateway

= 20">

AI-assisted APK reverse-engineering workspace API. Dispatches tasks to MCP agents (jadx, apktool, adb, frida, filesystem, MT Manager's APK MCP, AI providers) and streams updates over WebSocket. Runs entirely on-device (Termux + MT Manager on Android) or on a normal PC - no cloud required.

Flow: Workspace -> Workflow -> Jobs -> Tasks -> MCP Agents, with modules talking through an Event Bus. MIT licensed. Contributing: run npm run typecheck && npm run build && ./scripts/smoke-test.sh before a PR - see CONTRIBUTING.md.

Getting started

npm install
cp .env.example .env
npm run dev

The Gateway starts on http://localhost:8080 and prints a banner with your workspaces and copy-pasteable commands. GET / returns the same as JSON - the quickest way to see what's here.

Core endpoints (request/response shapes are in the linked docs):

  • GET / - live cheat sheet - GET /health - service + config status
  • POST /workspaces / GET /workspaces[/:id] / PUT /workspaces/by-name/:name (idempotent get-or-create)
  • POST /workspaces/:id/tasks - dispatch to an MCP agent, fire-and-forget; poll or watch /ws (AGENTS)
  • POST /workspaces/:id/jobs / /workflows / /knowledge (ARCHITECTURE)
  • GET /workspaces/:id/inbox - APKs dropped into APK_INBOX_DIR, if configured, and auto-claimed into this workspace (INBOX)
  • POST|GET /workspaces/:id/chat (AI)
  • GET /plugins (PLUGINS)
  • GET /capabilities - what the Gateway can do and which agents provide it (AGENTS)
  • GET /workspaces/:id/artifacts / GET /artifacts/:id - directories and files finished tasks produced, with the run that made them (ARCHITECTURE)
  • POST/GET /workspaces/:id/findings (filter by status or a cited entityId), GET/PATCH /findings/:id, GET /findings/:id/verification - claims with evidence checked against real artifacts and graph entities, and re-checked against the cited files (ARCHITECTURE)
  • POST/GET /workspaces/:id/graph/entities, GET /graph/entities/:id, POST/GET /workspaces/:id/graph/edges - typed entities and relationships observed about the target (ARCHITECTURE)
  • WS /ws - real-time task:update, job:update, workflow:update, knowledge:entry_created, workspace:status_changed for every workspace
  • WS /ws/workspaces/:id - same events, filtered to one workspace

Stack

Node.js 22+ / TypeScript, Fastify (+ @fastify/websocket), Zod. Storage is local files by default; Supabase is opt-in (STORAGE_BACKEND=supabase). Auth is an opt-in API key check, off by default (AUTH_ENABLED=false). npm test runs the Vitest unit suite (retry/failure-path logic, no live instance needed); scripts/smoke-test.sh covers end-to-end happy paths against a running Gateway - see tests/README.md for the split.

Documentation

DocCovers
docs/SETUP.mdRequirements, auth, storage backend, running on PC and Android/Termux
docs/ARCHITECTURE.mdEvent Bus, Job Engine, Workflow Engine, Knowledge Engine
docs/AGENTS.mdEvery MCP agent - operations and examples
docs/AI.mdThe AI provider layer (9 providers), the ai agent, Terminal chat
docs/MCP_SERVER.mdRegistering HexForge's agents as native tools in Claude Desktop/Code/Cursor
docs/PLUGINS.mdThe Plugin System - contract, loader, reference plugins
docs/CLI.mdthe hf CLI (scripts/hf.sh) and scripts/smoke-test.sh
docs/MT_MANAGER.mdMT Manager's APK MCP setup, with screenshots and troubleshooting
docs/PROJECT_STRUCTURE.mdRepo layout and how the pieces talk
docs/ROADMAP.mdWhat's done and what's still open

Questions fréquentes

Qu'est-ce que Hexforge Gateway ?

APK reverse engineering workspace that orchestrates jadx, apktool, adb and Frida through a workflow engine, on Termux (Android) or PC.

Comment installer Hexforge Gateway ?

Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.

Hexforge Gateway est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Hexforge Gateway ?

Il est publié par boy-offi9-inc. AI.tn le référence sans le maintenir ni le recommander.

Issu des listes communautaires awesome-mcp-servers et du dépôt GitHub du projet. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.