Pokutuna Mcp Chrome Tabs
pokutuna-mcp-chrome-tabs is a Claude Code plugin for the Build phase that integrates Chrome browser tabs with your agent through MCP.
by pokutuna · github.com/pokutuna/mcp-chrome-tabs
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.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install pokutuna-mcp-chrome-tabs@pokutuna/mcp-chrome-tabsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:pokutuna/mcp-chrome-tabs") and the paste-ready config with skillselion.get_install_config("plugin:pokutuna/mcp-chrome-tabs").
What it does
pokutuna-mcp-chrome-tabs is a minimal Claude Code plugin that connects your agent to Chrome tabs via MCP. Solo builders 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.
Highlights
- 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
Why builders use it
Agents lack visibility into what you already have open in Chrome, so you keep pasting URLs and page content into the chat.
After you install the MCP Chrome tabs plugin, your Claude Code workflow can use tab-level browser context as part of agent integrations.
At a glance
- Type - Plugin in LLM Integration.
- Adoption - 0 installs, 32 stars, 0 votes.
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.
Comments
Share how you use pokutuna-mcp-chrome-tabs, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.