Model Context Protocol (MCP) 서버는 브라우저의 열린 탭 콘텐츠에 직접 액세스를 제공합니다. 추가 fetching 또는 인증 필요 없음 - 단순히 당신이 이미 보는 것을 접근.

키 기능

• ** 직접 브라우저 탭 액세스 ** - 필요 없음 웹 스크랩, 이미 열린 탭에서 콘텐츠를 읽으십시오
• ** AI에 최적화 된 콘텐츠 ** - 토큰 사용을 줄이기 위해 자동 콘텐츠 추출 및 Markdown 변환
• **Active 탭 단축키 ** - ID를 지정하지 않고 현재 집중된 탭에 즉시 액세스
• MCP listChanged notifications - MCP 프로토콜을 따라 탭 변경 ([T0]]을 활성화합니다)

요구 사항

[! 중요] **macOS 만 ** - 이 MCP 서버는 Apple Events (JXA)를 사용하고 macOS에서만 작동합니다.

• Node.js 22 이상
• **MCP 클라이언트 ** Claude Desktop, Claude Code, 또는 MCP 호환 클라이언트와 같은 -macOS만 (브라우저 자동화를 위한 JXA를 통해 Apple Events 사용)

시작하기

먼저 Chrome에서 Apple Events에서 "Allow JavaScript"를 활성화하십시오.

• (en) **** > 개발자 > Apple Events의 모든 JavaScript
• (ja) **웨어 ** > ** **Apple 이벤트 からの JavaScript を **

@pokutuna/mcp-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-interval to 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": {
    "chrome-tabs": {
      "command": "npx",
      "args": ["-y", "@pokutuna/mcp-chrome-tabs@latest"]
    }
  }
}

Or for Claude Code:

claude mcp add -s user chrome-tabs -- npx -y @pokutuna/mcp-chrome-tabs@latest

Claude Code Plugin

You can also install this as a Claude Code plugin:

# Add the marketplace
/plugin marketplace add pokutuna/mcp-chrome-tabs

# Install the plugin
/plugin install mcp-chrome-tabs@mcp-chrome-tabs

Command Line Options

The package also provides read-only commands for accessing the same tab data as the MCP tools:

# List open tabs as: [INDEX] ID TITLE DOMAIN (* marks the active tab)
npx @pokutuna/mcp-chrome-tabs list

# Show the full URL in place of the domain
npx @pokutuna/mcp-chrome-tabs list --include-url

# Read the active tab
npx @pokutuna/mcp-chrome-tabs read --active

# Read a specific tab from an ID returned by list
npx @pokutuna/mcp-chrome-tabs read ID:12345:67890

# Read by INDEX from the list instead