Server facts
blowback MCP Server
Project
- Author
- ESnark
- Repository
- github.com/ESnark/blowback
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 23
- Last commit
- Data as of
Overview
Frontend debugging with Blowback centers on a browser connected to a development server. Assistants can create browser contexts, list active instances, inspect context details and usage statistics, and close individual instances. Inspection tools expose element state, styles, geometry, and HTML, while network monitoring records requests over a chosen interval. Browser interactions include navigation, typing, clicking, scrolling, and other predefined actions. A separate evaluation tool runs JavaScript against the page or element handles. Console output and recent hot-reload events provide additional evidence when investigating application behavior.
Checkpoints organize observations around named browser states. Logs produced while a checkpoint is active carry its identifier, allowing developers to query output associated with that state. Screenshots can cover the page or an individual element, with images kept in the project and metadata maintained in SQLite. Screenshot resources support listing captures and looking them up by URL path; responses use file references by default, with base64 image output available through configuration. HMR monitoring begins when the browser launches, but an HMR connection is optional.
blowback setup notes
- blowback records stdio only; confirm a network transport upstream before planning remote access.
- blowback has no recorded license; confirm reuse terms in its repository.