Design and validate WebMCP tools using Chrome DevTools MCP.
npx skills add https://github.com/WebMCP-org/npm-packages --skill webmcp-setup
Please help me install this Agent Skill. Skill: webmcp-setup Source: https://github.com/WebMCP-org/npm-packages/tree/main/skills/webmcp-setup Command: npx skills add https://github.com/WebMCP-org/npm-packages --skill webmcp-setup
This Skill provides strategic guidance for building WebMCP-enabled applications, helping teams design robust tools, enforce safety patterns, and adopt a tested workflow without diving into boilerplate code.
Understand your app and plan tools by category; implement a three-phase approach (read-only, read-write, destructive); test tools with Chrome DevTools MCP; iterate based on feedback.
High-intent search queries and answers about installing and using this skill.
WebMCP tools are designed safely using a three-category taxonomy: read-only, read-write, and destructive. This classification structures LLM interactions and enforces safety patterns like the two-tool form pattern to prevent unintended side effects.
The two-tool form pattern in WebMCP separates form generation from submission to enable user review before action. This ensures structured outputs and prevents destructive tools from executing without explicit validation.
Validate WebMCP tools by dogfooding them with Chrome DevTools MCP to test behavior in a real browser context. This approach lets you iterate on read-only, read-write, and destructive tool implementations based on actual feedback.
Yes, node-fetch is a required dependency for implementing WebMCP tools. The Skill provides phased guidance to build read-write and destructive tools, ensuring safe tool design aligned with WebMCP documentation and installation references.
Structure WebMCP tool implementation through a three-phase approach: Read, Write, and Act. This phased guidance helps teams plan tools by category and adopt a tested workflow for building robust web applications.
Use destructive tools in WebMCP when actions permanently alter data, requiring the two-tool form pattern for user review. The three-category taxonomy ensures destructive tools are implemented with strict safety patterns and phased validation.
anybackup-aiAutomate client deployment, configuration, and log retrieval via foundation-cli.
etylsarinAutomate browser-based UI testing with Chrome DevTools MCP.
CygnusfearControl Chrome DevTools Protocol to automate browser interactions and capture console, network, and screenshots.
aboul3ataGenerates cross-pollination design brainstorms from unrelated categories and writes an HTML report.
