Wopee Mcp
Let your agent dispatch Wopee.io AI test runs and crawls on your web app, then pull status, logs, and artifacts before you merge or release.
Overview
wopee-mcp is a MCP server for the Ship phase that dispatches Wopee.io AI testing agents for web apps and returns run status, crawls, and artifacts over stdio.
What is this MCP server?
- Dispatch AI-driven test runs and crawls for web applications
- Fetch run status, artifacts, and results into the agent context
- stdio npm package wopee-mcp at registry version 1.26.2
- Configurable WOPEE_API_URL with project UUID scoping
- Requires WOPEE_API_KEY for authenticated Wopee.io API access
- npm package wopee-mcp version 1.26.2
- Transport: stdio
- Default API base https://api.wopee.io
Community signal: 3 GitHub stars.
What problem does it solve?
Indie builders merge UI changes blind because spinning up structured test runs and collecting evidence means leaving the agent IDE for yet another SaaS console.
Who is it for?
Solo developers shipping web SaaS or complex marketing sites who want agent-triggered exploratory and regression testing on Wopee.io.
Skip if: Native mobile-only products with no web surface, or teams that refuse cloud test keys and need purely local unit tests.
What do I get? / Deliverables
Once WOPEE_API_KEY is configured, your agent can start test runs and crawls and surface artifacts inline so you fix failures before customers do.
- Dispatched AI test or crawl runs against your web app
- Run status and logs available to the agent
- Downloadable or referenced test artifacts from Wopee.io
Recommended MCP Servers
Journey fit
Automated web testing belongs in ship when you are proving the product is safe to release, not while you are still sketching scope or writing blog posts. Testing is the precise subphase for MCP servers that trigger test agents, site crawls, and artifact retrieval against a staging or production URL.
How it compares
Cloud AI web-test dispatcher MCP, not a markdown code-review skill or an infra monitoring server.
Common Questions / FAQ
Who is wopee-mcp for?
It is for developers and indie founders using AI coding agents who already test web apps on Wopee.io and want dispatch, crawl, and artifact tools inside MCP.
When should I use wopee-mcp?
Use it in the ship testing subphase before releases or after meaningful frontend changes, when you need agent-driven runs and downloadable artifacts from Wopee.io.
How do I add wopee-mcp to my agent?
Install the npm package wopee-mcp, set WOPEE_API_KEY (and optionally WOPEE_PROJECT_UUID and WOPEE_API_URL), add the stdio server io.github.Wopee-io/wopee-mcp in Claude Code or Cursor, then invoke tools to start runs and fetch results.