AI & MemoryMCP Registrymcpb16 toolsB · 71

Flintrail MCP server

com.soflution · Updated today

Drive a real Chrome live, record a flow once, replay it in milliseconds without an LLM.

At a glance

Flintrail is an MCP server in the AI & Memory category. It runs locally over stdio via `npx -y https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb`, and declares no required credentials. It exposes 16 tools, including fl_open, fl_act and fl_snapshot. It scores B (71/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 1

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Flintrail in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Flintrail in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add flintrail -- npx -y https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes (e.g. fl_open, fl_act, fl_snapshot). It discovers them automatically.

How to install Flintrail in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "flintrail": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb"
      ]
    }
  }
}

Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install Flintrail in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "flintrail": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb"
      ]
    }
  }
}

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install Flintrail in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.flintrail]
command = "npx"
args = ["-y", "https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb"]

Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install Flintrail in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "flintrail": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb"
      ]
    }
  }
}

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install Flintrail in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "flintrail": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb"
      ]
    }
  }
}

How to install Flintrail in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "flintrail": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Soflutionltd/flintrail/releases/download/v1.3.0/flintrail.mcpb"
      ]
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does Flintrail expose? (16)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

fl_openOpen a URL in a background tab, return a compact snapshot with `[eN]` refs.
fl_actRun 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_snapshotRe-read a page: interactive elements, headings, text excerpt, same-origin frames.
fl_extractRun JavaScript in the page and return the result.
fl_networkList the site's own API calls with timing, body and a JSON sample.
fl_screenshotJPEG screenshot of the tab, or of one element (`ref` / `selector`), in CSS pixels usable by `mouse`.
fl_consoleConsole errors and uncaught exceptions of a tab (`level: "all"` adds warnings and logs). `fl_act` says when new ones appear.
fl_record_startRecord a flow; `repairFrom` keeps the good steps and re-records the rest.
fl_runReplay a flow with variables, no LLM.
fl_run_manyReplay a flow for many variable sets in parallel tabs.
fl_flowsList flows, inspect one.
fl_flow_set_varTurn a recorded value into a `{{variable}}`, for flows taught by demonstration.
fl_extensionExtension connection status.
fl_adoptTake control of a tab you already opened yourself, for example right after signing in by hand.
fl_loginSign in with your saved password (browser password manager, 1Password, Bitwarden or your own command). Flintrail fills it, the agent never sees it. See Sign in.
fl_tabsManage tabs.

What the code can do

The published package could not be downloaded or read for analysis.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit today — Actively maintained.
Repository created 3 days ago — Very new project with little track record yet.
1 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 71

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 0 days ago.
Adoption20%9%
1 stars.
Transparency20%100%
4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.
Provenance15%75%
Links to its own repository; package linkage unverified.
Packaging15%50%
No pinned version — installs resolve to whatever is latest at launch.

Documentation

Full README

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

Claude Desktop: download `flintrail.mcpb` and double-click it.

Excerpt — the full document is on GitHub.

Alternatives to Flintrail

Agent360 Browser MCPA · 92Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.

Maintain Flintrail? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![Flintrail on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-soflution-flintrail)](https://mcp-skills-hub.vercel.app/mcps/com-soflution-flintrail)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.