Ripul Plugins
Add ripul-plugins when you need Claude Code to control Chrome via MCP and follow WebMCP patterns using navigator.modelContext on live pages.
Overview
ripul-plugins is a plugin marketplace for the Build phase that combines a Chrome-controlling MCP server and a WebMCP skill for navigator.modelContext on live pages.
What is this marketplace?
- 2 plugins: ripul-webmcp (MCP server v0.0.3) and webmcp-skill (v0.0.1)
- MCP server controls Chrome: open tabs, interact with pages, use page tools via navigator.modelContext
- MIT license; keywords include browser, chrome, mcp, automation, tabs, web
- Open-source tooling aligned with the W3C WebMCP proposal (github.com/ripulio/web-mcp)
- Companion skill teaches using navigator.modelContext API in web pages
- 2 plugins in marketplace (ripul-webmcp, webmcp-skill)
- ripul-webmcp version 0.0.3, webmcp-skill version 0.0.1, MIT license
- Repository metadata: https://github.com/ripulio/web-mcp
Community signal: 2 GitHub stars.
What problem does it solve?
Agents cannot reliably exercise or automate real web UIs when they lack MCP access to Chrome and page-exposed modelContext tools.
Who is it for?
Indie builders and agent developers prototyping browser automation, WebMCP integrations, or in-Chrome QA with Claude Code.
Skip if: Backend-only APIs with no browser surface, or teams that cannot run Chrome with MCP for policy reasons.
What do I get? / Deliverables
After installing ripul-plugins, Claude Code can drive Chrome tabs and use page-specific WebMCP tools with documented modelContext patterns.
- Chrome tab control and page interaction through the ripul-webmcp MCP server
- Agent workflows that consume page tools exposed via navigator.modelContext
- Documented usage patterns from the webmcp-skill companion plugin
Plugins in this marketplace
2 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Build is where agents meet external systems; browser control and page-exposed tools belong on integrations because they wire Claude to real web UIs and the W3C WebMCP direction. Integrations covers MCP servers and companion skills that extend the agent runtime; ripul pairs an MCP server with a skill documenting modelContext usage.
How it compares
MCP browser server plus companion skill bundle, not a single static analysis or Jira worklog plugin.
Common Questions / FAQ
Who is Ripul Plugins for?
Ripul Plugins is for developers building AI agents in Claude Code who need Chrome control and WebMCP-style page tools via navigator.modelContext.
When should I use Ripul Plugins?
Use it during Build when integrating or testing web apps that expose modelContext tools or when you need tab-level browser automation from the agent.
How do I add Ripul Plugins to my agent?
Register the ripulio/web-mcp marketplace, enable ripul-webmcp and optionally webmcp-skill, configure the MCP server for Chrome, then follow the skill when interacting with pages.