Playwriter
Provides browser automation capabilities through a Chrome extension that connects controlled tabs to a local relay server, enabling Playwright code execution with maintained browser, context, and page state between evaluations. Uses a single execute tool that accepts full Playwright API code snippets rather than exposing 12-17+ individual browser action tools, significantly reducing context window consumption. Supports collaborative automation where users can work alongside the agent in the same browser to handle captchas or complex interactions, and enables starting automation on existing pages to replicate bugs exactly as they occur. Built with patchright-core and security controls including explicit tab consent, localhost-only WebSocket connections, and Chrome's automation visibility banner.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- browser-automation
- Source
- PulseMCP
- Author type
- human
- Updated
- 2026-04-29
Use via MCP
Resolve Playwriter from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.