Looking Glass Mcp

io.github.Sahib-Sawhney-WHPublished by GitHub account Sahib-Sawhney-WHv3.1.1Updated Oct 27, 2026

AI-native browser for agents. 71 tools with self-healing, semantic extraction, vault CLI.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

Local MCP server that gives an AI assistant an AI-native browser with 71 tools for semantic extraction, self-healing automation and a credential vault.

What you can do
  • Drive a browser from the assistant through a large tool set (71 tools) for agent-style web interaction.
  • Extract page content semantically rather than by brittle selectors.
  • Rely on self-healing behavior when page structure changes.
  • Manage stored credentials through a separate vault CLI command.
When to use it
Worth adding when an assistant needs to browse and extract information from web pages on the user's own machine, especially where selectors change often and self-healing automation matters. It is a desktop-only local process, so it suits individual workstations rather than hosted setups.
Requirements
Runs as a local stdio process installed from the npm package looking-glass-mcp, so Node.js and a desktop machine are needed. A browser is driven by the server. Configuration uses the environment variables BROWSER_HEADLESS, BROWSER_SECURITY_PROFILE (restricted, local-dev, open or sandbox) and the secret VAULT_ENCRYPTION_KEY (32+ characters) for vault encryption; credentials are stored via the vault CLI. No authentication is declared.
Before you install
The server drives a real browser, so it can act on sites with whatever access the browser has; the BROWSER_SECURITY_PROFILE setting controls how permissive that is, and an open profile is the riskiest. It asks for a VAULT_ENCRYPTION_KEY passphrase and stores credentials in an encrypted vault, so protect that key. Page content and browsing activity go to the sites visited and to the model provider. Tool behavior is not documented in the manifest, so review the tools before enabling writes or…

Installation

In SourceWeft

  1. Open Looking Glass Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v3.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.