Skip to main content
Glama
davidwlindholm

local-web-mcp

by davidwlindholm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to local-web-mcp

No user-submitted related servers found.

    Related Servers

    • chrome-bridge

      bbauersjt
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides a direct bridge between Claude and an authenticated Chrome session, enabling fetch requests with session cookies and JavaScript execution within live web pages.
      -

    • Proxy Browser MCP Server

      nullsection
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to browse the web and make GET/POST/PUT requests with a real Chrome TLS/HTTP2 fingerprint to avoid anti-bot detection, supporting persistent cookie sessions and optional proxies.
      -

    • open-browser-control

      smankoo
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to control the user's Chrome or Firefox browser, leveraging existing sessions for tasks requiring authentication and user handoff.
      18
      44 npm
      17
      MIT

    • auth-fetch-mcp

      ymw0407
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to access content from authenticated web pages by opening a real browser for manual login and session capture. It saves browser profiles locally so users only need to log in once per service for future automated access.
      4
      47 npm
      36
      MIT

    • MCPBrowser

      cherchyk
      A
      license
      Not graded
      quality
      A
      maintenance
      Fetches content from authenticated web pages by driving your signed-in Chrome/Edge browser via DevTools Protocol, automatically handling login redirects and reusing sessions across domains.
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusing it with another tool. Its purpose is clearly described and scoped.

    Naming Consistency5/5

    The single tool name follows a clear, descriptive snake_case convention. With only one tool, there are no inconsistent patterns to evaluate.

    Tool Count3/5

    A single tool is borderline for a server, but it may be justified for a narrowly-focused fallback fetch utility. It feels thin compared to broader MCP servers, but not absurdly so.

    Completeness4/5

    The tool completely covers its stated purpose of fetching pages locally and returning readable text. Minor gaps exist around request customization or response metadata, but no core workflow dead ends are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources