Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FLINTRAIL_HOMENoDirectory for flows, profile and token.~/.flintrail
FLINTRAIL_MODENoBrowser mode: `attach`, `launch` or `extension`.attach
FLINTRAIL_PORTNoDebugging port used when Flintrail starts Chrome for Testing.9222
FLINTRAIL_TOKENNoHTTP bearer token and extension token. Generated once and stored in ~/.flintrail/token if not provided.generated
FLINTRAIL_CHROMENoBrowser executable.auto
FLINTRAIL_CDP_URLNoBrowser to attach to.http://127.0.0.1:9222
FLINTRAIL_HEADLESSNoSet to `0` to see the window in launch mode.1
FLINTRAIL_DOWNLOADSNoWhere downloads land.~/Downloads/Flintrail
FLINTRAIL_RELAY_PORTNoLocal port the extension connects to.8932
FLINTRAIL_ALLOW_ANY_BROWSERNoSet to `1` to allow attaching to a personal browser (Brave, Edge, Opera, or on macOS anything that is not Chrome for Testing) in attach mode.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
fl_openA

Open a URL in a background tab of the dedicated browser (logged-in sessions kept). Returns a compact snapshot whose [eN] refs can be used directly in fl_act.

fl_adoptA

Take control of a tab the user already has open in the browser (first match on a URL substring), e.g. a site they just signed in to by hand. Returns its snapshot.

fl_actB

Run SEVERAL actions in one call (fill a whole form, click, submit, wait, extract) and get one fresh snapshot back. Always batch as many actions as possible: one call beats ten.

fl_loginA

Sign in on the open sign-in form with the user's saved password: from the browser's own password manager, or from a password manager CLI the user configured (1Password, Bitwarden, custom command). Flintrail fills username, password and one-time code itself; the secrets never reach you. A CLI login is only filled when the page domain matches its website. On a multi-step sign-in (e-mail page, then password page), call it on each step. While recording, the flow stores the source and login ID, never a secret.

fl_snapshotC

Re-read a tab: interactive elements with refs, headings and the start of the text.

fl_extractB

Run JavaScript in the page and return the result. Fastest way to pull tables, lists or links.

fl_networkB

List the API calls (fetch/XHR) the site made, with method, status, timing, body and a JSON sample. Use it to replace UI clicks with a direct {do:"request"} step: the fastest possible replay.

fl_consoleC

Console errors and uncaught exceptions of a tab (level "all" adds warnings and logs). fl_act and fl_snapshot already say when new errors appeared.

fl_screenshotA

Screenshot of a tab, or of one element with ref / selector. Only when the visual layout matters: snapshots are much cheaper. Pixels are CSS pixels, usable as x / y for {do:"mouse"}.

fl_tabsB

List tabs opened by Flintrail.

fl_closeC

Close a Flintrail tab.

fl_record_startA

Start recording a flow. Every fl_open / fl_act after this is captured with robust element fingerprints so fl_run can replay it without an LLM. repairFrom keeps steps before that index and replaces the rest.

fl_record_stopA

Stop recording and save the flow (save=false to discard).

fl_runB

Replay a recorded flow at browser speed, no LLM. On failure (site changed) it stops at the failing step and returns the page so the flow can be repaired.

fl_run_manyB

Replay the same flow for many variable sets in parallel, each in its own background tab.

fl_flowsB

List recorded flows with their variables and last timing.

fl_flowB

Show a flow with all its steps and element fingerprints.

fl_flow_set_varC

Turn the literal value of one step into a variable {{var}}, e.g. after recording by demonstration.

fl_extensionB

Status of the Flintrail browser extension (extension mode).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 19 tools

Disambiguation4/5

Most tools have clearly distinct purposes: recording (record_start/stop), replay (run/run_many), inspection (snapshot/network/console/screenshot), and action batching (act/extract). A few pairs are close—fl_run vs fl_run_many, fl_flows vs fl_flow, and fl_open vs fl_snapshot both returning snapshots—but the descriptions disambiguate them adequately.

Naming Consistency4/5

All names share a consistent fl_ prefix and snake_case formatting, which is highly predictable. There is mild inconsistency between verb-style (fl_open, fl_run, fl_extract) and noun-style (fl_tabs, fl_flows, fl_console) names, but this mirrors the common list-vs-action distinction and remains readable.

Tool Count4/5

19 tools is on the heavier side but justified by a genuinely multi-faceted domain: browser control, flow recording, replay, login, and debugging. Each tool maps to a concrete capability rather than redundant surface area.

Completeness4/5

The surface covers the full lifecycle of record→save→replay→repair, plus inspection, auth, and parallel execution. Minor gaps exist—no explicit flow delete/rename or dedicated tab-switch/navigation tool—but agents can work around these via fl_act or re-opening.

Maintenance

ActivityNo data
ResponsivenessOutdated data