dev-mcp-servers

The MCP servers worth having on by default, pinned and configured.

v0.1.0Source ↗#mcp#playwright#browser#testing

At a glance

Ships
1 skill
Needs
No credentials, accounts or external CLIs
Runs in
Claude Code only — it needs a shell and a checkout

Install

  1. 01Add the marketplace (once)

    /plugin marketplace add https://catylai.com/marketplace.json
  2. 02Install dev-mcp-servers

    /plugin install dev-mcp-servers@catylai

Install it once and the servers listed here start when Claude Code starts. The point is not that these servers are hard to add — it is that the defaults are decided once, in a repository, instead of differently on every machine.

playwright drives a real browser: navigate, read the accessibility tree, click, type, and read console messages and network requests. Three defaults are set deliberately and are worth knowing about.

The version is pinned, not @latest. A floating version means every developer runs whatever happened to be published most recently, and a change in behaviour arrives without a commit to point at. Bumping it is a pull request.

It runs headless and in an isolated profile. Headless works over SSH, in a container and in CI rather than only on a laptop with a display. The isolated profile lives in memory, so no cookies or logins persist between sessions or leak from your own browser into an automated one. Every flag has a PLAYWRIGHT_MCP_* environment variable, and your shell's value wins — so watching it work is one variable away, without editing the plugin.

browser-check is the skill that uses it: drive a page, then report what the console and the network actually said rather than what the screenshot implied.

These are local stdio servers, so Claude Code only — Cowork and claude.ai cannot start local processes. The skill still loads on the web and degrades to working from console output or screenshots you paste in.