Allows AI agents to monitor signed-in Chrome tabs, perform route sweeps, and generate bug reports via a Chrome extension.
Also known as mayank1307/fileforge, fileforge, fileforge-mcp-server
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.2
- Last commit
- Nov 5, 2026
- License
- MIT
What is FileForge MCP?
FileForge allows AI agents to monitor signed-in Chrome tabs, perform route sweeps, and generate bug reports via a Chrome extension.
Summary generated from the project's README
About FileForge MCP server
FileForge Browser DevTools provides a bridge between AI agents and your active Google Chrome sessions. By using a dedicated Chrome extension loaded in developer mode, this server allows an agent to monitor signed-in tabs and perform route sweeps to identify issues. It is designed for developers who want their AI clients to interact directly with their live browser environment to find and report bugs.
Setup requires Node.js 20 or newer and involves installing the package globally via npm. Users must load the unpacked extension folder into Chrome and then configure their specific MCP client, such as Claude Desktop, Cursor, or Claude Code. The fileforge-setup command automates the configuration process by providing the necessary paths and commands for different clients. For added security, you can enable a pairing mode that requires a bridge token generated by the fileforge-pair command.
What you can do with it
- 1Monitor active browser tabsAsk your AI agent to check the status of your currently open Chrome tabs.
- 2Automated route sweepingInstruct the agent to scan through your application routes to find errors.
- 3Bug report generationHave the AI agent analyze browser data and create a formal report of discovered bugs.
Written from the project's README. Every use case is checked against a quote from it.
How to install FileForge MCP
Formats verified 10 Nov 2026Install FileForge MCP in Claude Code
$ claude mcp add fileforge -- npx -y fileforge-mcp-serverInstall FileForge MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"fileforge": {
"command": "npx",
"args": [
"-y",
"fileforge-mcp-server"
]
}
}
}Install FileForge MCP in VS Code
.vscode/mcp.json
{
"servers": {
"fileforge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"fileforge-mcp-server"
]
}
}
}Install FileForge MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"fileforge": {
"command": "npx",
"args": [
"-y",
"fileforge-mcp-server"
]
}
}
}Install FileForge MCP in Codex
~/.codex/config.toml
[mcp_servers.fileforge] command = "npx" args = ["-y", "fileforge-mcp-server"]
Install FileForge MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"fileforge": {
"command": "npx",
"args": [
"-y",
"fileforge-mcp-server"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablemayank1307/fileforge is public and reachablegithub.com/mayank1307/fileforge ↗Pass
- Package names this repository as its sourcefileforge-mcp-server names mayank1307/fileforge as sourcenpmjs.com/package/fileforge-mcp-server ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-05github.com/mayank1307/fileforge ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from fileforge-mcp-serverPass
- No critical advisory in the package or its dependencies137 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubfileforge-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.
FileForge MCP questions
How do I add FileForge MCP to Claude Code?
Run claude mcp add fileforge -- npx -y fileforge-mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add FileForge MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I install the FileForge MCP server?
Install it globally using npm: npm install -g fileforge-mcp-server.
Is pairing required?
Pairing is optional and can be enabled by setting FILEFORGE_REQUIRE_PAIRING=1 in the server's environment, which requires a bridge token.