mcpField
F
FileForge Browser DevTools

FileForge Browser DevTools

Local
github.com/mayank1307Browser Automation1Updated 4d ago
Repository

About FileForge Browser DevTools

FileForge Browser DevTools is an MCP server and Chrome extension for agents working with a signed-in browser. It supports cross-tab monitoring, route sweeps, and bug-report generation.

Key features

  1. 01Watch signed-in Chrome across tabs
  2. 02Sweep application routes
  3. 03Generate bug reports
  4. 04Setup and verify MCP client connections

Use cases

  1. 01Monitor browser behavior across multiple tabs
  2. 02Check application routes and collect bug reports

MCP support

The server provides browser development tools to MCP clients, using its Chrome extension to interact with signed-in Chrome. `fileforge-setup` configures supported clients, and `fileforge-verify` checks the connection.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "mayank1307-fileforge": {
      "command": "npx",
      "args": [
        "-y",
        "fileforge-mcp-server"
      ]
    }
  }
}
Run commandnpx -y fileforge-mcp-server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmfileforge-mcp-server0.2.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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

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

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:

fileforge-setup --client cursor --write

Every client is covered in the setup guide.

Verify

With your MCP client open and Chrome running:

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

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.