Server data from the Official MCP Registry
Browser DevTools for agents in your signed-in Chrome: cross-tab watching, route sweeps, bug reports.
About
Browser DevTools for agents in your signed-in Chrome: cross-tab watching, route sweeps, bug reports.
Security Report
Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
10 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-mayank1307-fileforge": {
"args": [
"-y",
"fileforge-mcp-server"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
FileForge
Your agent watches your signed-in Chrome across tabs, sweeps your routes, and hands you the bug report.
FileForge is a local MCP server plus a Chrome extension. It works with Claude Code, Claude Desktop, Codex and Cursor. Your client talks to the server over stdio, the server talks to the extension over a WebSocket on 127.0.0.1, and the extension uses Chrome APIs and the DevTools Protocol.
What your agent can do
- Watch several tabs at once. Follow network traffic, console errors, JS exceptions and DOM changes across tabs, and set tripwires such as
status >= 500to check later. - Sweep your routes. One call visits a list of routes and returns console errors, failed API calls, and accessibility and layout issues for each.
- Get coding context for a page. One call returns the framework, selectors, forms, console, network and performance.
- Hand you the evidence. Generate bug reports, PR evidence bundles and debug bundles, or export captured API calls as curl, Postman or MSW mocks.
- Come back to earlier results. Audits, route sweeps and scrapes are saved in SQLite under
~/.fileforge/, where the agent can read them with SQL later. It can also compare two audit runs. Scraped links and tables get their own tables. - Repeat the work. Record a browser workflow and replay it, or schedule a routine.
All of this runs in the Chrome you already use, signed in to your own apps and staging sites.
Try these prompts
Open a page you're working on, then ask your agent:
Use FileForge to show the console errors and failed network requests on my active tab, then find the likely cause in this repo.
Use FileForge to sweep /, /pricing and /settings on http://localhost:3000 and list the console errors and failed API calls for each route.
Use FileForge to watch my open tabs and set a tripwire for status >= 500. I'll click around. When I say done, tell me what fired and which request caused it, then write a bug report.
How it compares
Reaching your signed-in browser is no longer unique to FileForge. These are the differences as of November 2026, from each project's own docs:
| FileForge | Chrome DevTools MCP | Playwright MCP | |
|---|---|---|---|
| Use your signed-in browser | Extension, connected whenever the server runs | --autoConnect, after enabling remote debugging in Chrome | --extension, choosing a tab to connect |
| Install | npm, plus an unpacked extension | npx, no extension | npx, plus a Chrome Web Store extension for your signed-in browser |
| Cross-tab watching and tripwires | Yes | Not in its tool reference | Not in its docs |
| Route sweep in one call | Yes | Not in its tool reference | Not in its docs |
| Bug report and PR evidence bundles | Yes | Not in its tool reference | Not in its docs |
| SQL over saved results | Yes | Not in its tool reference | Not in its docs |
| Heap snapshots and Lighthouse | No | Yes | Not in its docs |
| Browsers | Chrome | Chrome | Chrome, Edge, Firefox, WebKit |
| Maintained by | One independent developer | Google's Chrome DevTools team | Microsoft |
Pick Chrome DevTools MCP for memory leaks, Lighthouse audits or an install with no extension. Pick Playwright MCP to automate other browsers or generate tests. Pick FileForge when an agent should keep an eye on several tabs, check many routes, and produce evidence you can keep. It complements Playwright, Cypress and Vitest; keep those for your test suite.
Context cost: the tool list is about 23,000 tokens (26 tools, roughly 93 KB of schemas), which your client may load at the start of a session. If that matters, compare it with your other servers before leaving it on all the time.
Quickstart
You need Node.js 20 or newer and Google Chrome.
npm install -g fileforge-mcp-server
fileforge-setup
fileforge-setup prints the extension folder and the exact command or config for each client, using your real paths. It changes nothing unless you pass --write. Then:
- Load the extension. Open
chrome://extensions, turn on Developer mode, click Load unpacked and pick the folder it printed. FileForge isn't on the Chrome Web Store. - Connect your client. For Claude Code or Codex, run the command it printed. For Cursor or Claude Desktop, run
fileforge-setup --client cursor --writeorfileforge-setup --client claude-desktop --write, which keeps your other servers and saves the old file as.bak. - Check it. With your client open and Chrome running, run
fileforge-verify, then ask your agent to callfileforge_runtime_actionwithaction: "status".
Prefer a clone? Full instructions for every client and OS are in docs/setup.md.
Tool groups
Every tool takes an action parameter. The full reference, with every action and parameter, is in docs/tools.md.
For a tool specification page, use docs/tools-spec.json. It includes every registered tool and action, features, input schemas, request templates, response conventions, and available capability metadata. Undeclared output schemas are explicitly marked. Regenerate both references with cd mcp-server && npm run docs:tools.
| Tool | What it does |
|---|---|
fileforge_runtime_action | Server health, extension status and version check, request log |
fileforge_browser_action | Open, switch, reload and close tabs; read tab and window state |
fileforge_page_interaction | Read and act on the DOM: text, snapshots, forms, click, fill, assert, debug selectors |
fileforge_scrape_action | Scrape pages, tables, metadata, assets and design tokens; crawl a site |
fileforge_devtools_action | Console, JS errors, network, API responses, WebSockets, evaluate, HAR export |
fileforge_eye_action | Watch several tabs at once for network, console and DOM activity; set tripwires |
fileforge_coding_action | One-call coding context for a page, a route sweep, or a bug |
fileforge_qa_testing | Smoke tests, route checks, clean-console and clean-network checks |
fileforge_audit_action | SEO, accessibility, content, security and policy audits with presets |
fileforge_a11y_action | Accessibility tree, keyboard and contrast checks |
fileforge_responsive_action | Layout scans across widths; overflow and overlap finder |
fileforge_perf_action | Performance audit and metrics |
fileforge_visual_action | Screenshots, baselines, visual diffs, CSS, colors and fonts |
fileforge_api_action | Discover REST and GraphQL calls; export curl, Postman or MSW mocks |
fileforge_app_action | Detect the framework; read routes, client storage, feature flags, Next.js data |
fileforge_extension_action | Inspect a Chrome extension's manifest, storage, service worker and errors |
fileforge_workflow_action | Record and replay browser workflows |
fileforge_task_action | Create, schedule and run multi-step routines |
fileforge_result_action | Fetch, list, search and slice stored results |
fileforge_sql_action | List, describe and query saved results and scraped data with SQL |
fileforge_search_action | Search saved pages, notes, history and bookmarks |
fileforge_memory_action | Save pages, diff them against earlier visits, search memory |
fileforge_note_action | Local notes |
fileforge_file_action | Fetch, parse, convert and decode files and data URIs |
fileforge_report_action | Bug reports, PR evidence and debug bundles |
fileforge_export_action | Export stored results and SQL output to files |
Security and privacy
- The bridge listens on
127.0.0.1:47821only. It rejects connections from web pages and from any extension other than FileForge's pinned ID. - Other local processes need the token in
~/.fileforge/bridge-token, which only your user can read. SetFILEFORGE_REQUIRE_PAIRING=1to require it from the extension too (pairing). - Everything is stored locally in
~/.fileforge/. There is no telemetry, and FileForge makes no outbound requests on its own: everything it fetches is a page or URL a tool was asked to load. - Tools that would return raw secret values are off unless you set
FILEFORGE_ALLOW_SECRET_REVEAL=1. fileforge_file_actionreads local files only from FileForge's output folders and folders you list inFILEFORGE_ALLOWED_READ_PATHS, and fetches local or private addresses only for hosts you list inFILEFORGE_ALLOWED_FETCH_HOSTS. Browser tools can still open those addresses.- The debugger attaches only to the tabs a tool call names (Eye watches every tab only when called with
all: true), and Chrome shows its "started debugging this browser" bar while it does. Every permission is explained in docs/permissions.md.
The threat model and how to report a vulnerability are in SECURITY.md.
More
License
MIT. See LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.