Skip to main content
Glama
Sign In
FileForge

FileForge

by mayank1307
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to FileForge

No user-submitted related servers found.

    Related Servers

    • byob

      Pavelj43
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.
      1 npm
      ISC

    • byob

      huseyinzawadzki17371
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's own already-logged-in Chrome — clicking, typing, reading pages, taking screenshots, and inspecting cookies, network, and console through the extension rather than a debug port. All communication stays on the machine, with agent-opened tabs grouped and kept out of focus.
      1 npm
      ISC

    • Browser Runtime MCP

      MakiDevelop
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to monitor and debug browser runtime errors, console logs, and page diagnostics in real time via a Chrome extension and local MCP server.
      4
      MIT

    • MCP Browser Logger

      tao-Lionel
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that captures browser console logs and network requests via the Chrome DevTools Protocol. It allows users to monitor real-time logs, inspect network traffic, and execute JavaScript code directly in the browser context.
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 26 tools

    Disambiguation3/5

    Many tools overlap around browser inspection, auditing, scraping and QA: audit vs a11y/perf/responsive, devtools vs api/eye, coding vs app, and memory vs note/result/search. The descriptions cross-reference each other and help, but an agent still has to make non-obvious choices among several closely related tools.

    Naming Consistency4/5

    All tools use a consistent fileforge_ snake_case prefix, and almost all end in _action. Two tools, fileforge_page_interaction and fileforge_qa_testing, break the suffix pattern, but the overall convention is still predictable.

    Tool Count2/5

    At 26 top-level tools, the surface is heavy for the apparent browser QA/automation scope. Several tools could reasonably be consolidated, especially the audit, devtools/API/monitoring, and extraction/result families, which increases selection burden.

    Completeness4/5

    The set broadly covers browser control, scraping, QA, audits, performance, accessibility, DevTools, files, notes, memory, reports and exports. Minor lifecycle gaps remain, such as notes lacking update/delete, routines only being disabled rather than deleted, and no obvious cleanup for stored results, but agents can mostly work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources