openwork-docker-chrome-mcp
Best for QA automation engineersWorks with GitHub
⌘source
- author
@different-ai- language
- TypeScript
★14kstars
1.3kforks
Apr 19, 2026
✦overview.md
Key Features
- ·Starts OpenWork development stack via Docker
- ·Verifies real user flows through Chrome MCP automation
- ·Provides complete URLs and authentication tokens
- ·Includes commands to stop the Docker stack
- ·Uses Chrome DevTools Protocol for UI testing
Use Cases
- →Automated smoke testing of the OpenWork UI after deployment
- →Verifying end-to-end user chat flows work correctly
- →Testing the development environment setup process
- →Creating automated UI validation for CI/CD pipelines
Best for
- ✓QA automation engineers
- ✓DevOps teams
- ✓Release validation
Not ideal for
- !Manual testing only
- !Non-OpenWork projects
- !Production environment testing
FAQs
name
openwork-docker-chrome-mcp
description
Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP.
Triggers when user mentions:
- "dev-up.sh"
- "docker dev stack"
- "verify in chrome mcp"
- "test the real flow"
Quick Usage (Already Configured)
1) Start the dev stack (Docker)
Run from the OpenWork repo root:
packaging/docker/dev-up.sh
This prints:
- Web UI URL (http://localhost:<WEB_PORT>)
- OpenWork server URL (http://localhost:<OPENWORK_PORT>)
- Token file path (
tmp/.dev-env-<id>) containingOPENWORK_TOKEN+OPENWORK_HOST_TOKEN - A
docker compose ... downcommand that stops this stack
2) Verify a real UI flow (Chrome MCP)
Minimum gate:
- Open the printed Web UI URL.
- Navigate to the session/chat surface (typically
/session). - Send a message (example:
smoke: hello from chrome mcp). - Confirm a response renders in the UI.
Chrome MCP tool recipe (typical):
chrome-devtools_list_pages(optional: see existing tabs)chrome-devtools_new_pagewith the Web UI URL (orchrome-devtools_navigate_pageif a page is already open)chrome-devtools_take_snapshotto locate the chat input + Send button uidschrome-devtools_fillthe chat input uid with your messagechrome-devtools_clickthe Send button uidchrome-devtools_wait_fora distinctive piece of response text (or re-snapshot until the response appears)
$install
1-click copynpx skills add different-ai/openwork --skill openwork-docker-chrome-mcpSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.