Server facts
msw-mcp
Project
- Author
- JasonBoy
- Repository
- github.com/JasonBoy/msw-mcp
- Website
- msw-mcp-docs.vercel.app
- License
- MIT
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 81
- Last commit
- Data as of
Tags
- api mock
- mock
- msw
- test
Overview
Mock Service Worker network mocks can be adjusted during an active browser session with msw-mcp, giving AI assistants and developers control over request handlers without a page reload. Its MCP tools accept JavaScript handler definitions for execution in the browser, remove handlers using URL patterns with optional HTTP method filters, and replace matching handlers atomically. Resetting offers two distinct paths: discard runtime additions while retaining the initial handlers, or supply a replacement handler set. A status tool reports the connection, service worker state, and active handlers.
The project connects MCP and command-line control to the browser through a WebSocket bridge. A client package applies incoming changes to the local MSW configuration, while a core daemon handles communication and sessions. Setup can be scaffolded through the companion CLI or an MCP prompt, with manual setup also documented. The CLI supports terminal and scripted workflows alongside assistant-driven operation. Configuration covers ports, persistence, and client targeting. The MCP server runs on Node, communicates over stdio, and is distributed under the MIT license.
msw-mcp setup notes
- msw-mcp records stdio only; confirm a network transport upstream before planning remote access.