100+ plugins. ~2,000 tools.
Each one talks to the real web app through your authenticated session.
Plus built-in browser tools for any tab.
And 90+ more — messaging, DevOps, finance, shopping, streaming, and beyond. Browse all plugins
How it works
OpenTabs is a Chrome extension and MCP server. Your AI agent sends a tool call, it gets routed to the right browser tab, and the action happens on the real web app.
Your AI sends a tool call
Claude, Cursor, or any MCP client calls a tool like discord_send_message — just a normal MCP tool call.
OpenTabs routes it to the right tab
The MCP server finds the matching browser tab and dispatches the call through the Chrome extension.
It runs on the real web app
The plugin adapter executes the action in the page using your logged-in session. Results flow back to the agent.
Two ways to get plugins
Let your AI build it
Point your AI at any website. It analyzes the page, discovers the APIs, scaffolds a plugin, writes the tools, and registers it. Every line of code is yours to review.
Fun fact: many of the plugins in this repo were built by AI in minutes. The MCP server ships with site analysis tools, the SDK handles the boilerplate, and a self-improving skill teaches AI agents the entire process. Every time an agent builds a plugin, it writes what it learned back into the skill — so the system gets better with every plugin built.
I think this is actually safer than installing someone else's code — your agent wrote it, you can read every line, and it runs in your browser.
Learn moreInstall pre-built
100+ plugins ready to go. Install globally and they're auto-discovered by the server. Or build your own by hand with the Plugin SDK and publish to npm.
Security, for real
I know you're the kind of person who sets DANGEROUSLY_SKIP_PERMISSIONS=1 the moment something asks for confirmation. I respect that. But your browser sessions are precious, so I wanted the defaults to be thoughtful — even for the fearless.
Everything starts off
Every plugin's tools are disabled by default — even the ones I ship. What if my account gets compromised? You shouldn't have to trust me blindly either.
AI-assisted code review
When you enable a plugin, your AI can review the adapter source code first. You see the findings and decide.
Version-aware
When a plugin updates, permissions reset. New code, new review.
Full audit log
Every tool call is logged — what ran, when, whether it succeeded. On disk and in memory.
Everything runs locally. No cloud. No telemetry. The code is open source — read it.
Questions you're probably thinking
Why not just use the official MCP server for Slack / GitHub / etc.?
If an official MCP server works well for you, absolutely use it. I started building OpenTabs for apps that don't ship official MCP support — Discord, Figma, Linear, and many others had nothing when I began. And some probably never will — I'm not holding my breath for a Domino's MCP server. Along the way, I noticed that setting up separate API keys for each service adds up when you use ten of them, and the web app often has access to more features than the public API exposes. I see OpenTabs and official servers as complementary — use whatever works best, or mix and match.
How is this different from browser automation tools?
Tools like Playwright MCP, Stagehand, and Browser-Use are great — they work on any site out of the box by navigating the page visually. The difference is that whatever the AI figures out during a session is gone afterward. There's no way to share or reuse that knowledge. OpenTabs plugins call internal APIs directly, so once a plugin is built, it's a structured, typed package anyone can install. The knowledge accumulates — every plugin built makes the platform more useful for everyone.
What about Chrome's WebMCP?
WebMCP is a proposal where websites expose structured MCP tools natively. I think it's a great idea — it's how the web should probably work long-term. The timeline depends on adoption, though. OpenTabs works right now, in about five minutes. When WebMCP is widespread, OpenTabs plugins can evolve to use it.
Can I build a plugin for Google Docs?
I'll be honest: I burned a lot of tokens trying and couldn't crack it. Google did a genuinely impressive job obscuring their internal APIs — hats off to them. If you manage to figure it out and want to contribute a Google Workspace plugin back, you'd be my hero.