
Pokutuna Mcp Chrome Tabs
- 33 repo stars
- Updated July 28, 2026
- pokutuna/mcp-chrome-tabs
pokutuna-mcp-chrome-tabs is a Claude Code plugin that integrates Chrome browser tabs with your agent through MCP.
About
pokutuna-mcp-chrome-tabs is a minimal Claude Code plugin that connects your agent to Chrome tabs via MCP. developers who constantly juggle docs, staging apps, and dashboards in the browser can register it so Claude Code can incorporate tab context instead of relying on manual copy-paste. The repository metadata lists one plugin and keywords chrome, mcp, and tabs—signaling a narrow integration surface rather than a broad skill library. Place it on Skillselion under Build → Integrations because the value is wiring an external tool (Chrome) into the agent loop; it can support validate and ship debugging sessions, but installation is an integration decision during build. Expect intermediate setup comfort with MCP servers and local Chrome. It complements agent skills by supplying live page context; it does not replace structured skills for planning or code review.
- MCP-oriented Claude Code plugin for Chrome tab context
- Focused scope: browser tabs, not full desktop automation
- Single-plugin bundle from pokutuna/mcp-chrome-tabs
- Lets agents ground answers in currently open web pages
- Lightweight integration for web-heavy build and debug loops
Pokutuna Mcp Chrome Tabs by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install pokutuna-mcp-chrome-tabs@pokutuna/mcp-chrome-tabsAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 33 |
|---|---|
| Last updated | July 28, 2026 |
| Repository | pokutuna/mcp-chrome-tabs ↗ |
What it does
Expose live Chrome browser tabs to your coding agent through an MCP plugin so Claude can read and work with what is open in the browser.
Who is it for?
Best when you're doing web app work and want MCP-backed Chrome tab access from Claude Code during implementation and debugging.
Skip if: Headless-only pipelines, non-Chrome browsers without equivalent MCP support, or teams that forbid browser-connected agents.
What you get
After you install the MCP Chrome tabs plugin, your Claude Code workflow can use tab-level browser context as part of agent integrations.
- MCP-linked Chrome tab access inside your Claude Code setup
- Reduced manual copying of page content into agent chats
- A single-plugin integration focused on browser tab context
By the numbers
- 1 plugin in the pokutuna/mcp-chrome-tabs bundle
- 32 GitHub stars on pokutuna/mcp-chrome-tabs
- 3 plugin keywords: chrome, mcp, tabs
Recommended Plugins
How it compares
MCP Chrome tab integration, not a smart-home skill pack or multi-agent marketplace.
FAQ
Who is Pokutuna Mcp Chrome Tabs for?
It is for developers using Claude Code who need MCP access to Chrome tabs while building or debugging web-facing work.
When should I use Pokutuna Mcp Chrome Tabs?
Use it when your agent workflow depends on live browser state—docs, local dev servers, or staging tabs—and you want that wired in during build-time integrations.
How do I add Pokutuna Mcp Chrome Tabs to my agent?
Install the pokutuna/mcp-chrome-tabs Claude Code plugin, configure the MCP Chrome tabs server per the repo instructions, and enable it in your Claude Code MCP settings.