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_actA

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_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_screenshotB

Screenshot of a tab. Only when the visual layout matters: snapshots are much cheaper.

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.4/5.0

Scored across 16 tools

Disambiguation4/5

Most tools have clearly distinct purposes (open vs act vs snapshot vs extract vs network vs screenshot). There is minor overlap between fl_snapshot and fl_extract for reading page data, but the descriptions clarify when to use each.

Naming Consistency5/5

All tools use a consistent fl_ prefix with snake_case names that follow a verb/noun or resource/action pattern. Variations like fl_flow_set_var and fl_run_many remain predictable and readable.

Tool Count4/5

16 tools is slightly above the typical 3-15 sweet spot, but each covers a distinct browser-automation or flow-management capability with little redundancy. The set feels purposeful rather than bloated.

Completeness4/5

Core lifecycle is covered: opening, acting, snapshotting, extracting, recording, and replaying flows. Minor gaps exist—no explicit flow deletion (beyond save=false), no tab focus/selection, and no dedicated navigation steps—but agents can work around these via close/reopen and fl_act.

Maintenance

ActivityMaintained
ResponsivenessNo issues