Ship mcp-tools 0.1.0 with one command-only skill, fix-playwright-mcp, registered in the marketplace, documented like every other plugin, and covered by a test that runs under tests/run-all.sh.
Read and implement all steps in the plan at docs/plans/add-mcp-tools-plugin.md — Add the mcp-tools plugin. Verify against the plan's Tests, Verification, and Acceptance Criteria before reporting done. If everything passed, mark completion in docs/plans/add-mcp-tools-plugin.md — tick each step's [x] marker and each criterion's - [x], set status: completed — and re-render the HTML from the spec. If any check failed, leave status: in-progress and say which.
More ways to run this plan — goal & workflow prompts, file path
/goal Add the mcp-tools plugin. The plan at docs/plans/add-mcp-tools-plugin.md describes one approach — use it as reference, but optimize for the outcome. Verify against the plan's Tests, Verification, and Acceptance Criteria before reporting done. If everything passed, mark completion in docs/plans/add-mcp-tools-plugin.md — tick each step's [x] marker and each criterion's - [x], set status: completed — and re-render the HTML from the spec. If any check failed, leave status: in-progress and say which. This goal is met in either of two end states: every check passed and the plan is marked completed, or the only checks left are blocked on something the user must do (a permission, a decision, an external system, a failure that predates this plan), the plan stays in-progress, and each blocker is named.
add-mcp-tools-plugin.html
docs/plans/add-mcp-tools-plugin.html
docs/plans/add-mcp-tools-plugin.md
Context
The story behind this plan — what prompted the work and why it matters now.
The official Playwright plugin starts its MCP server with npx @playwright/mcp@latest. Each
release of @playwright/mcp is built on a different Playwright version, and each Playwright
version drives one specific Chromium build. When a new release ships, the server wants a browser
build that is not installed: every session prompts to download Chromium, ~/.npm/_npx accumulates
one cached copy per release (about 30 on this machine, spanning builds 1155–1247), and the server
can fail to connect at session start. The durable fix is a user-scope server pinned to one version
and pointed at the system Chrome, which updates itself.
The user asked for a plugin skill that detects and fixes this, chose a new mcp-tools plugin
(domain-container name, matching artifact-tools/content-tools), named-command activation
(disable-model-invocation: true), and a Playwright-specific scope.
Steps
The step-by-step work, in order — each step says what to do, why it matters, and how to check it worked.
kit/plugins/mcp-tools/ with .claude-plugin/plugin.json, README.md, CHANGELOG.md, and skills/fix-playwright-mcp/SKILL.md carrying the plan-mode guard, a worked diagnosis example, and a backup-and-restore verification path.
~/.claude/settings.json and user-scope MCP config, so the repo's guard and verification-gate rules apply.node tests/plugins/test-mcp-tools.mjs passes and the guard test's Check 3 still passes..claude-plugin/marketplace.json at 0.1.0 with no version in plugin.json.
BASE_REF=main node scripts/check-plugin-versions.mjs passes.tests/plugins/test-mcp-tools.mjs covering marketplace wiring, the missing manifest version, command-only activation, and the guard; add the skill to WRITE_HEAVY in tests/plugins/test-exitplanmode-guard.sh.
node tests/plugins/test-mcp-tools.mjs and bash tests/plugins/test-exitplanmode-guard.sh pass.README.md counts, tree, install list, enabledPlugins example, Plugins section and How-To table, regenerate the Plugin Reference Table with node scripts/build-readme-table.mjs, and add the plugin to .claude/settings.json enabledPlugins.
node scripts/build-readme-table.mjs --check exits 0 and no count still reads 13 plugins or 67 skills.docs/guides/how-to/mcp-tools.md, its row and total in docs/guides/how-to/README.md, and an Unreleased entry in the root CHANGELOG.md.
Tests
The tests that prove the change does what it promises.
tests/plugins/test-mcp-tools.mjsmcp-tools with an X.Y.Z version and a source path that holds skills/fix-playwright-mcp/SKILL.md, plugin.json has no version, the skill is command-only (disable-model-invocation: true), and it carries the plan-mode guard verbatim.node tests/plugins/test-mcp-tools.mjsDefinition of done
The plan counts as done when every statement below is true — check each one off as you verify it.
Final check
One last pass to confirm the whole change works end to end.
Run bash scripts/verify.sh from the repo root and confirm every stage passes or reports a named
skip. Then load the plugin with claude --plugin-dir ./kit/plugins/mcp-tools and confirm/mcp-tools:fix-playwright-mcp is listed as a command.
Wrapping up
Three gates that must all pass before this plan is marked completed.
Completion Report
No items to report — all requirements met.