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.
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_fetchrunsfetch()inside the tab's page context. Best for cookie-based auth (same-origin requests).browser_fetch_authintercepts 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:
- 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.
- 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=9222for 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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。