qutebrowser-mcp

qutebrowser-mcp

MCP server for automating qutebrowser browser via CDP and IPC. Enables tab management, navigation, screenshots, JavaScript execution, and authenticated HTTP requests through the browser's session.

Category
Visit Server

README

qutebrowser-mcp

MCP (Model Context Protocol) server for qutebrowser browser automation.

Control qutebrowser from Claude Code or any MCP-compatible client.

Note: Linux only. Uses Unix domain sockets and XDG paths.

Features

  • CDP-First Design - Most tools operate on specific tabs via Chrome DevTools Protocol without changing focus
  • Tab Management - List, open, close, focus, and move tabs
  • Navigation - Go to URLs, back/forward, reload — all targetable to specific tabs
  • Screenshots - Capture any tab without switching to it
  • JavaScript Execution - Run JS in any tab and get return values
  • Authenticated Fetch - Make HTTP requests through the browser's logged-in sessions (cookies or Bearer tokens)
  • Bookmarks & History - Access bookmarks, quickmarks, and browsing history

CDP Setup (Recommended)

Most tools use Chrome DevTools Protocol to operate on tabs without changing focus. Enable remote debugging via environment variable:

QTWEBENGINE_REMOTE_DEBUGGING=9222 qutebrowser

Without CDP, tools fall back to IPC which operates on the currently focused tab and may cause tab switches.

Installation

npm install
npm run build

Usage

With Claude Code

Add to your ~/.claude.json:

{
  "mcpServers": {
    "qutebrowser": {
      "command": "node",
      "args": ["/path/to/qutebrowser-mcp/dist/index.js"]
    }
  }
}

Run Directly

npm start

Available Tools

CDP-Enabled Tools

These accept an optional tab parameter (URL or title substring) to target a specific tab via CDP without changing focus. Without tab, they fall back to IPC on the focused tab.

Tool Description
list_tabs List all tabs with indices, URLs, titles, active state (session file + CDP enrichment)
close_tab Close a tab by URL/title match (CDP) or by index (IPC)
navigate Navigate a tab to a URL
go_back Navigate back in history
go_forward Navigate forward in history
reload_page Reload a page
screenshot Capture a page as PNG
execute_js Run JavaScript and return the result (CDP) or fire-and-forget (IPC)

IPC-Only Tools

These use qutebrowser's Unix domain socket for features CDP can't provide.

Tool Description
open_tab Open a new background tab
focus_tab Switch focus to a tab by index (intentionally changes focus)
move_tab Move the current tab to a new position
get_bookmarks List bookmarks
get_quickmarks List quickmarks
search_history Search browsing history

CDP-Only Tools

These always require CDP and a tab parameter.

Tool Description
browser_fetch fetch() inside a page context, inheriting cookies/session
browser_fetch_auth Capture auth headers from network traffic, make server-side requests

browser_fetch vs browser_fetch_auth

  • browser_fetch runs fetch() inside the tab's page context. Best for cookie-based auth (same-origin requests).
  • browser_fetch_auth intercepts Bearer tokens from the tab's network traffic, then makes the request server-side. Best for token-based auth (e.g. Outlook, which uses MSAuth tokens injected by JavaScript).

How It Works

The server communicates with qutebrowser through two channels:

  1. CDP (Chrome DevTools Protocol WebSocket) - Primary channel. Bidirectional communication for JS evaluation, navigation, screenshots, tab close, reload, and network interception. Operates on specific tabs without changing focus.
  2. IPC (Unix domain socket) - Secondary channel. Fire-and-forget commands for qutebrowser-specific features (tab open, focus, move, bookmarks, session save).

State is read from:

  • Session file (~/.local/share/qutebrowser/sessions/_autosave.yml) - Tab indices, active state, pinned state
  • CDP targets - Fresh tab titles and URLs
  • SQLite database (~/.local/share/qutebrowser/history.sqlite) - Browsing history
  • Config files (~/.config/qutebrowser/) - Bookmarks and quickmarks

Requirements

  • Linux (uses Unix domain sockets for IPC)
  • Node.js 18+
  • qutebrowser running with IPC enabled (default)
  • Recommended: qutebrowser started with QTWEBENGINE_REMOTE_DEBUGGING=9222 for CDP support

Respects XDG environment variables (XDG_DATA_HOME, XDG_CONFIG_HOME, XDG_RUNTIME_DIR) with standard fallbacks, so it should work across most Linux distributions.

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured