Flintrail
Drive a real Chrome live, record a flow once, replay it in milliseconds without an LLM.
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
https://github.com/Soflutionltd/flintrail/releases/download/v1.2.0/flintrail.mcpbالتوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
المحتويات
The fastest browser for AI agents.
Drive a real Chrome live. Record a task once. Replay it in milliseconds, with no LLM in the loop.
Or skip the page entirely and replay the site's own API calls with your session.
Why
Browser MCP servers today make the model do everything, every time: read the page, pick one element, click, read the page again. Each click is a tool call, and each tool call is a model turn that costs seconds. Do the same task tomorrow and the agent pays the full price again.
Flintrail treats the browser like a JIT compiler treats code:
- Live, the agent drives the page, but batches a whole sequence of actions into one call and gets back a compact snapshot with clickable refs.
- Record, the same calls are captured with multi-clue element fingerprints and
{{variables}}. - Replay, the flow runs at browser speed with no model between steps. When a site changes, the run stops at the exact failing step and hands the page back so the agent repairs only that part.
- API replay, Flintrail sees the site's own fetch/XHR calls and can replay them from inside the page, with the same cookies and session. No rendering, no clicking.
Benchmark
Same 5-step task (fill a field, tick a box, change page, click a client-rendered button that calls an API, wait for the result), median of 10 runs, headless Chromium. The numbers are tool-side wall time only. In a real agent every tool call also costs a model turn, so going from 7 calls to 2 saves several more seconds on top.
The hatched bar is the floor: the same clicks as a raw Playwright script, with no MCP and no agent. Any tool that clicks through the UI is bounded by it, which is why the per-call ratios stay modest. Flintrail adds about 50 ms per call on top of that floor, Playwright MCP about 260 ms. The only way under the floor is to stop clicking, which is what API replay does.
Reproduce it: npm run bench (installs nothing global; Playwright MCP is a dependency of bench/ only).
Architecture
Install
git clone https://github.com/Soflutionltd/flintrail.git
cd flintrail && npm install && npm run build
Claude Desktop, Claude Code, Cursor (stdio)
{
"mcpServers": {
"flintrail": {
"command": "node",
"args": ["/absolute/path/to/flintrail/dist/cli.js"]
}
}
}
Claude Code: claude mcp add flintrail -- node /absolute/path/to/flintrail/dist/cli.js
Any agent, any machine (HTTP)
node dist/cli.js --http --host 127.0.0.1 --port 8931
# token is generated once in ~/.flintrail/token (or pass --token / FLINTRAIL_TOKEN)
Clients connect to http://host:8931/mcp with Authorization: Bearer <token>. Put it behind a tunnel or reverse proxy with TLS if it leaves the machine.
Browser modes
| Mode | When | How |
|---|---|---|
attach (default) | Your desktop. Keep your logged-in sessions. | Connects over CDP to a dedicated Chrome for Testing. On macOS Flintrail finds it, restarts it with a local debugging port if needed (tabs are restored) and opens its own tabs in the background. |
launch | Servers, CI, Docker. | FLINTRAIL_MODE=launch starts Chromium with a persistent profile in ~/.flintrail/profile, headless by default. |
extension | Anyone, any Chromium browser, no debugging port. | FLINTRAIL_MODE=extension and the Flintrail extension installed. See below. |
Flintrail refuses to attach to a personal browser (Brave, Edge, Opera, or on macOS anything that is not Chrome for Testing) unless FLINTRAIL_ALLOW_ANY_BROWSER=1. Your everyday browser stays yours.
Browser extension
The extension is the easiest way in: no command-line flags, no debugging port, works in Chrome, Edge, Brave, Arc or any Chromium 125+.
- Install. Download
flintrail-extension-<version>.zipfrom the latest release, unzip it, openchrome://extensions, enable Developer mode, click Load unpacked and pick the folder. (Chrome Web Store listing in progress.) - Run Flintrail in extension mode, for example in Claude Desktop:
{ "mcpServers": { "flintrail": { "command": "npx", "args": ["-y", "github:Soflutionltd/flintrail"], "env": { "FLINTRAIL_MODE": "extension" } } } } - Connect. Click the Flintrail icon, paste the token from
~/.flintrail/token, click Connect. The extension reconnects by itself afterwards.
How it works: Flintrail starts a relay on 127.0.0.1:8932. The extension connects to it with the token and executes CDP commands with chrome.debugger, one tab at a time. Playwright sees an ordinary CDP browser, so every tool, recording and replay works unchanged. The agent only sees tabs it opened itself or tabs you share with Share with agent. Chrome shows its "started debugging this browser" bar while a tab is driven, by design.
Teach by demonstration
You do not have to explain a task to the agent. Type a flow name in the popup, click Start recording, do the task yourself in the tab, click Stop and save. The extension records clicks, typing, selects, checkboxes and Enter with the same element fingerprints the engine uses, and never records password fields. Then:
fl_flow_set_var("paybyphone-renew", 0, "plate") # turn the typed plate into {{plate}}
fl_run("paybyphone-renew", { "plate": "AB-123-CD" })
The flow now runs without you, without the LLM, in milliseconds per step.
Limits in extension mode: browser-level CDP (download folder, permissions, window size) is not available to extensions, so download saves through the browser's normal download flow. Chrome dismisses dialogs of background tabs driven by chrome.debugger before anyone can answer, so in this mode {do:"dialog"} answers the next alert / confirm / prompt from inside the page instead.
Tools
| Tool | What it does |
|---|---|
fl_open | Open a URL in a background tab, return a compact snapshot with [eN] refs. |
fl_act | Run many actions in one call: click, dblclick, hover, fill, type, select, check, press, upload, download, goto, back, wait, scroll, mouse, dialog, resize, eval, request. |
fl_snapshot | Re-read a page: interactive elements, headings, text excerpt, same-origin frames. |
fl_extract | Run JavaScript in the page and return the result. |
fl_network | List the site's own API calls with timing, body and a JSON sample. |
fl_screenshot | JPEG screenshot of the tab, or of one element (ref / selector), in CSS pixels usable by mouse. |
fl_console | Console errors and uncaught exceptions of a tab (level: "all" adds warnings and logs). fl_act says when new ones appear. |
fl_record_start / fl_record_stop | Record a flow; repairFrom keeps the good steps and re-records the rest. |
fl_run | Replay a flow with variables, no LLM. |
fl_run_many | Replay a flow for many variable sets in parallel tabs. |
fl_flows / fl_flow | List flows, inspect one. |
fl_flow_set_var | Turn a recorded value into a {{variable}}, for flows taught by demonstration. |
fl_extension | Extension connection status. |
fl_adopt | Take control of a tab you already opened yourself, for example right after signing in by hand. |
fl_tabs / fl_close | Manage tabs. |
Example
// one call, five actions
{ "tool": "fl_act", "tab": "t1", "actions": [
{ "do": "fill", "ref": "e1", "value": "AA-111-AA", "var": "plate" },
{ "do": "check", "ref": "e3" },
{ "do": "click", "role": "button", "name": "Continue" },
{ "do": "click", "selector": "[data-testid=confirm]" },
{ "do": "wait", "text": "active" }
]}
Then fl_run("permit", { "plate": "ZZ-999-ZZ" }) repeats it in under a second.
// files, native dialogs, coordinates, mobile width
{ "tool": "fl_act", "tab": "t1", "actions": [
{ "do": "upload", "ref": "e4", "files": ["/Users/me/statement.csv"], "var": "statement" },
{ "do": "dialog", "accept": true },
{ "do": "click", "role": "button", "name": "Delete" },
{ "do": "mouse", "x": 640, "y": 380 },
{ "do": "resize", "width": 390, "height": 844 }
]}
upload works on a file input, even a hidden one, and on a button or drop zone that opens the file chooser. Dialogs are dismissed by default and every one is reported in the result, as are new console errors.
How replay finds elements again
Each recorded step stores a fingerprint, not a fragile selector: test id, stable id, name attribute, ARIA role and accessible name, placeholder, link target, visible text and a short CSS path. At replay time Flintrail tries them from most to least stable and takes the first that matches exactly one element, waiting only for that element, never for the network to go idle.
Security
- No password is ever written to a flow. Password fields are skipped during recording; keep the session logged in instead.
- Flows are plain JSON in
~/.flintrail/flows, easy to review and version. - The HTTP transport requires a bearer token (constant-time comparison) and binds to
127.0.0.1by default. evalandrequestrun inside the page with the page's own privileges, nothing more.
Configuration
| Variable | Default | |
|---|---|---|
FLINTRAIL_MODE | attach | attach, launch or extension |
FLINTRAIL_RELAY_PORT | 8932 | Local port the extension connects to |
FLINTRAIL_CDP_URL | http://127.0.0.1:9222 | Browser to attach to |
FLINTRAIL_PORT | 9222 | Debugging port used when Flintrail starts Chrome for Testing |
FLINTRAIL_CHROME | auto | Browser executable |
FLINTRAIL_HEADLESS | 1 | 0 to see the window in launch mode |
FLINTRAIL_HOME | ~/.flintrail | Flows, profile, token |
FLINTRAIL_DOWNLOADS | ~/Downloads/Flintrail | Where downloads land |
FLINTRAIL_TOKEN | generated | HTTP bearer token and extension token |
Develop
npm install
npx playwright-core install chromium # once, for tests
npm test # build + 19 end-to-end tests over real MCP, extension included
npm run pack:extension # flintrail-extension-<version>.zip
npm run bench # benchmark vs Playwright MCP
Roadmap
- Chrome Web Store and Edge Add-ons listings for the extension.
- Automatic promotion of recorded UI steps to API steps when the captured call is replay-safe.
- Shared flow library for common sites.
- Visual diff on replay failure.
En français
Flintrail est un serveur MCP de navigation pour agents IA. Il pilote un vrai Chrome dédié (jamais votre navigateur personnel), enchaîne plusieurs actions en un seul appel, enregistre une tâche la première fois puis la rejoue seul, sans IA, en quelques centaines de millisecondes, ou en rejouant directement les appels API du site avec votre session. Sur notre banc d'essai, la même tâche prend 2,4 s avec Playwright MCP et 0,11 s avec Flintrail en mode API.
L'extension Chrome rend tout cela accessible à tout le monde : on l'installe, on colle le jeton, et l'agent pilote le navigateur. Mieux, on peut lui apprendre une tâche en la faisant soi-même une fois (bouton Start recording), Flintrail la rejoue ensuite seul. Les mots de passe ne sont jamais enregistrés.
License
MIT © 2026 Soflution Ltd
الأسئلة الشائعة
ما هو Flintrail؟
Drive a real Chrome live, record a flow once, replay it in milliseconds without an LLM.
كيف أثبّت Flintrail؟
اتبع خطوات التثبيت في توثيقه المعروض في هذه الصفحة وفي مستودعه.
هل يحتاج Flintrail إلى مفتاح API؟
لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.
هل Flintrail مفتوح المصدر؟
نعم. شيفرته متاحة على GitHub بترخيص MIT.
من يصون Flintrail؟
ينشره Soflutionltd. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.