Chrome TabsSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://badge.fury.io/js/@pokutuna%2Fmcp-chrome-tabs)
Model Context Protocol (MCP) server that provides direct access to your browser's open tabs content. No additional fetching or authentication required - simply access what you're already viewing.
Key Features
- Direct browser tab access - No web scraping needed, reads content from already open tabs
- Content optimized for AI - Automatic content extraction and markdown conversion to reduce token usage
- Active tab shortcut - Instant access to currently focused tab without specifying IDs
- MCP listChanged notifications - Follows MCP protocol to notify tab changes (set
--check-intervalto enable)
Requirements
[!IMPORTANT] macOS only - This MCP server uses Apple Events (JXA) and only works on macOS.
- Node.js 22 or newer
- MCP Client such as Claude Desktop, Claude Code, or any MCP-compatible client
- macOS only (uses Apple Events via JXA for browser automation)
Getting Started
First, enable "Allow JavaScript from Apple Events" in Chrome:
- (en) View > Developer > Allow JavaScript from Apple Events
- (ja) 表示 > 開発 / 管理 > Apple Events からの JavaScript を許可
When you first use the MCP server, macOS will prompt you to grant Automation permission to your MCP client (e.g., Claude Desktop, Claude Code). Click OK to allow access to Chrome. If you accidentally dismissed the dialog, you can enable it in System Settings > Privacy & Security > Automation.
When multiple Google Chrome processes exist, JXA generally selects the oldest process, but this is not a guaranteed process-selection API. Start your normal Chrome before starting other Chrome instances when process identity matters.
Standard config works in most MCP clients (e.g., .claude.json, .mcp.json):
{
"mcpServers"bfddea1ba7acOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-chrome-tabs -- npx -y @pokutuna/[email protected]
{
"mcpServers": {
"mcp-chrome-tabs": {
"command": "npx",
"args": [
"-y",
"@pokutuna/[email protected]"
]
}
}
}Exposed tools (3)
3 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
list_tabs | read | |
open_in_new_tab | read | |
read_tab_content | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (4)
.prettierignore
import { getInterface, BrowserInterface } from "../../src/browser/browser.js";@modelcontextprotocol/server, defuddle, zod, @modelcontextprotocol/client, @playwright/test, @types/node, playwright, prettier
- `MCP_CHROME_TABS_EXCLUDE_HOSTS` environment variable, excluded in addition to `--exclude-hosts`, so that the MCP server and command line runs can share the same exclusions
Gates applied: no_behavioural_pass.
bfddea1ba7acfull audit observations/trust-audit/mcp-server/pokutuna__chrome-tabs.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | bfddea1ba7ac | SAFE | B | 89 | first audit |
Questions
What tools does Chrome Tabs expose?
3 in total: 3 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Chrome Tabs safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Chrome Tabs need?
No credential environment variables were found in its source, so it appears to need none.
How does Chrome Tabs run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @pokutuna/mcp-chrome-tabs at 0.8.3.
How current is this page?
The grade is for one exact copy of the source (bfddea1ba7ac), read on 2026-10-08. The repository is watched and re-audited when it changes.