by pokutuna
Instantly access and read your open Chrome tabs — direct browser tabs content with no extra fetching or authentication.
Accesses content from your Chrome browser's open tabs without scraping or authentication. Works only on macOS using AppleScript automation.
@pokutuna/mcp-chrome-tabs is a community-built MCP server published by pokutuna that provides AI assistants with tools and capabilities via the Model Context Protocol. Instantly access and read your open Chrome tabs — direct browser tabs content with no extra fetching or authentication. It is categorized under browser automation, developer tools.
You can install @pokutuna/mcp-chrome-tabs in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
@pokutuna/mcp-chrome-tabs is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
Useful MCP listing: @pokutuna/mcp-chrome-tabs is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated @pokutuna/mcp-chrome-tabs against two servers with overlapping tools; this profile had the clearer scope statement.
@pokutuna/mcp-chrome-tabs reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired @pokutuna/mcp-chrome-tabs into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
I recommend @pokutuna/mcp-chrome-tabs for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
According to our notes, @pokutuna/mcp-chrome-tabs benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
@pokutuna/mcp-chrome-tabs is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend @pokutuna/mcp-chrome-tabs for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated @pokutuna/mcp-chrome-tabs against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, @pokutuna/mcp-chrome-tabs benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 41
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.
<img src="./demo/demo.webp" width="600px" />
--check-interval to enable)[!IMPORTANT]
macOS only - This MCP server uses AppleScript and only works on macOS.
First, enable "Allow JavaScript from Apple Events" in Chrome:
When you first use the MCP server, macOS will prompt you to grant AppleScript 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.
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
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
The server accepts optional command line arguments for configuration:
Content Extraction Options
--max-content-chars - Maximum content characters per single read (default: 20000)--extraction-timeout - Timeout for content extraction worker in milliseconds (default: 20000)--exclude-hosts - Comma-separated list of domains to exclude from tab listing and content accessResource Options
--check-interval - Interval in milliseconds to check for tab changes and send listChanged notifications (default: 0 disabled, set to 3000 for 3 seconds)Browser Options
--application-name - Application name to control (default: "Google Chrome")--experimental-browser - Browser implementation to use: "chrome", "safari", or "arc" (default: "chrome")Other Options
--help - Show help message with all available optionsSetting --check-interval to a value greater than 0 enables resource subscription. When enabled, the server monitors tab list changes and sends MCP listChanged notifications to prompt clients to refresh their resource lists. This also makes tab://{windowId}/{tabId} resources available for all open tabs.
In 2025-10, few MCP clients support resource subscriptions. Resource subscription is disabled by default (--check-interval=0). Most users only need the tab://current resource, which is always available.
To enable resource subscription:
{
"mcpServers": {
"chrome-tabs": {
"command": "npx",
"args": [
"-y",
"@pokutuna/mcp-chrome-tabs@latest",
"--check-interval=3000"
]
}
}
}
Note that Safari lacks unique tab IDs, making it sensitive to tab order changes during execution:
npx @pokutuna/mcp-chrome-tabs --application-name=Safari --experimental-browser=safari
npx @pokutuna/mcp-chrome-tabs --application-name=Arc --experimental-browser=arc
List all open tabs in the user's browser with their titles, URLs, and tab references.
Get readable content from a tab in the user's browser.
id (optional): Tab reference from list_tabs output (e.g., ID:12345:67890)id is omitted, uses the currently active tabOpen a URL in a new tab to present content or enable user interaction with webpages.
url (required): URL to open in the browserID:windowId:tabId for immediate access to the new tabResource representing the content of the currently active tab.
tab://currenttext/markdown--check-interval settingResource template for accessing specific tabs.
tab://{windowId}/{tabId}text/markdown--check-interval is set to a value greater than 0Current Tabs (0 tabs exists) is displayedEnsure "Allow JavaScript from Apple Events" is enabled in Chrome (see Getting Started).
If it was working before, try restarting your browser.
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.