FileForge Browser DevTools

io.github.mayank1307Published by GitHub account mayank1307v0.2.2Updated Nov 5, 2026

Browser DevTools for agents in your signed-in Chrome: cross-tab watching, route sweeps, bug reports.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server plus Chrome extension that lets an agent watch your signed-in browser across tabs, sweep routes, and produce bug reports.

What you can do
  • Control browser tabs, read page state, and interact with the DOM (click, fill, assert)
  • Scrape pages, extract tables and metadata, and search saved pages, results, notes, history and bookmarks
  • Run QA smoke tests, accessibility, responsive and performance audits, and capture or compare visual artifacts
  • Inspect DevTools sessions, network and API calls, app framework state, and Chrome extension details
  • Record and run browser workflow recipes, routines and scheduled tasks
  • Generate bug reports, PR evidence bundles, and export results, HAR files or SQL query output
When to use it
Useful when an agent needs to work inside a real, already signed-in Chrome session: reproducing and documenting bugs, sweeping site routes for QA, accessibility or responsive issues, and packaging evidence for reports or pull requests.
Requirements
Node.js 20 or newer and Google Chrome on the same desktop machine. Install the npm package globally (not via npx) so the bundled Chrome extension folder stays in place, load it unpacked in developer mode, and register the server with your MCP client. Optional pairing mode uses the FILEFORGE_REQUIRE_PAIRING environment variable and a bridge token from the pairing command.
Before you install
The agent acts inside your signed-in Chrome profile, so it can reach whatever those sessions can reach, including authenticated pages and stored data. It can click, fill and navigate pages, run and delete workflow recipes, and write local notes, memory and stored results. Pairing is optional and off unless enabled, so consider turning it on. Desktop only; no web-hosted version.

Installation

In SourceWeft

  1. Open FileForge Browser DevTools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

fileforge-mcp-server

The MCP server for FileForge. Your agent watches your signed-in Chrome across tabs, sweeps your routes, and hands you the bug report. This package also contains the FileForge Chrome extension, which you load unpacked from the package folder.

You need Node.js 20 or newer and Google Chrome.

Install

bash
npm install -g fileforge-mcp-server

Install it globally, not with npx: Chrome loads the extension from the package folder, so the folder must stay put.

Set it up

bash
fileforge-setup

This prints the extension folder and the exact command or config for each MCP client, using your real paths. It changes nothing unless you pass --write.

Open chrome://extensions, turn on Developer mode, click Load unpacked and pick the folder it printed. The card should show ID nlcebipkdgecilmgfpobamljieanadpn.

Then connect your client. For Claude Code or Codex, run the command it printed. For Cursor or Claude Desktop, let it edit the config file; it keeps your other servers and saves the old file as .bak:

bash
fileforge-setup --client cursor --write

Every client is covered in the setup guide.

Verify

With your MCP client open and Chrome running:

bash
fileforge-verify

Then ask your agent to call fileforge_runtime_action with action: "status".

Pairing

Optional: with FILEFORGE_REQUIRE_PAIRING=1 in the server's environment, the extension must present the bridge token. fileforge-pair prints it, and you paste it into the side panel's Settings tab. See the setup guide.

Updating

bash
npm install -g fileforge-mcp-server@latest

Then click the reload icon on the FileForge card at chrome://extensions and restart your MCP client. fileforge-verify warns when Chrome is still running the old extension code.

More

MIT license.

Source: mcp-server/README.md at commit 648f8d2

Tools

26

fileforge_runtime_action

Runtime health, status, capabilities, and request log actions.

ParameterslimitactionrequiredfailuresOnlyincludeDetails

fileforge_result_action

Retrieve, list, search, and slice stored FileForge results.

Parametersreflimitqueryactionrequiredoffsetproject

fileforge_browser_action

Control browser tabs and read browser state. Use query_context to read state; navigate/history/wait for tab control.

ParametersurlquerystoretabIduntilactionrequiredactivedryRunidleMsnewTabpresetproject+14 more

fileforge_page_interaction

Interact with the DOM, extract page info, run QA checks, and debug failures (click, fill, assert, smoke_test, debug_clickability, capture_debug_bundle, etc.)

ParametersmodedepthstoretabIdvalueactionrequiredamountchecksincludeprojectfallbackselector+20 more

fileforge_scrape_action

Scrape and extract content via the GraphQL-style query_scrape action, plus legacy actions (scrape_page, extract_tables, extract_metadata, …).

ParametersurlurlsquerystoretabIdactionrequiredpresetsourcetabIdsprojectmaxPagessections+2 more

fileforge_sql_action

List, describe, query, and export SQL-backed FileForge data.

Parametersreflimitquerytableactionrequiredformatoffsetfilename

fileforge_search_action

Search across saved pages, results, notes, browser history, and bookmarks.

Parametersreflimitqueryactionrequired

fileforge_devtools_action

Unified DevTools tool. Primary action: query_devtools (GraphQL-feel modules + presets). Plus session lifecycle, evaluate, replay_request, export_har, and legacy get_* read actions.

ParametersquerystoretabIdactionrequireddryRunfilterlevelspresetfilenameoperationoverridesrequestId+7 more

fileforge_perf_action

Run performance audits and collect metrics.

ParametersurlrequiredstoreactionrequiredprojectsettleMstimeoutMsviewportsnetworkIdleMsincludeScreenshotnetworkIdleTimeoutMs

fileforge_qa_testing

Run QA checks, smoke tests, element watches, and route tests.

ParametersurlstoretabIdactionrequiredchecksroutesbaseUrlprojectwatchIdselectortimeoutMsviewports

fileforge_audit_action

Unified audit tool. Primary action: query_audit (GraphQL-feel modules + presets). Also: compare_audit_snapshots, plus legacy route/content/policy/security/recommendation/comparison/export/summary actions.

ParameterskeyrefurltextquerystoretabIdtitleactionrequiredissuespresetroutes+16 more

fileforge_visual_action

Capture, compare, inspect, and export visual browser artifacts.

ParametersxyrefrunurlnamestoretabIdwidthactionrequiredactiveformat+21 more

fileforge_a11y_action

Run accessibility audits and checks.

ParametersstoretabIdactionrequiredstandard

fileforge_responsive_action

Scan layout and find responsive issues across widths.

ParametersurlstoretabIdactionrequiredcheckswidths

fileforge_api_action

Discover and export REST and GraphQL API calls.

ParametersstoretabIdactionrequiredexportfiltergroupByfilenameincludeBodies

fileforge_coding_action

Capture coding-focused page, route, bug, and article context bundles.

ParametersurlstoretabIdtitleactionrequiredreloadroutesbaseUrlprojectdomDepthkeepOpensettleMs+7 more

fileforge_workflow_action

Record, list, run, export, and delete browser workflow recipes.

ParametersnamestepsstoretabIdactionrequiredformatinputscaptureassertions

fileforge_task_action

Create, run, schedule, plan, inspect, validate, dry-run, and export FileForge routines (and legacy task pipelines).

ParametersurlmodenametaskhintslimitpatchqueryrunIdsincestepsstore+56 more

fileforge_memory_action

Manage local page memory, diffing, and result slicing.

ParametersrefurllimitquerystoretabIdactionrequiredoffsetprojectquestion

fileforge_app_action

Inspect app framework, routing, client storage, feature flags, and framework-specific state.

ParameterstabIdactionrequiredincludeStateHints

fileforge_file_action

Fetch, parse, convert, inspect, and decode files and Data URIs.

ParameterstorunurlfromnamelimitstoretabIdactionrequiredformatdataUriproject+3 more

fileforge_note_action

Create, list, and search local notes.

Parameterstagurlbodytagslimitquerytitleactionrequiredoffset

fileforge_report_action

Generate bug reports, PR evidence bundles, and full debug bundles.

ParametersurlstabIdtitleactionrequiredformatinclude

fileforge_export_action

Export stored results and SQL query output.

Parametersrefqueryactionrequiredformatfilename

fileforge_extension_action

Inspect and test Chrome extension manifest, permissions, storage, service worker, injection, and errors.

ParameterskeyareastoretabIdactionrequiredprojectselectors

fileforge_eye_action

God's Eye — cross-tab browser monitoring. Watch chosen tabs, or every open tab with all: true: live network traffic, console errors, JS exceptions, DOM mutations, WebSocket frames. Lock onto a target tab for enhanced capture (auto-screenshots on errors). Plant tripwires that fire silently when conditions hit any tab.

ParametersallurltabsurlsclearlimittabIdactionrequiredfilterenabledfocusedidentity+3 more

Version history

1
  1. v0.2.2LatestNov 5, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts