
Wopee Mcp
Connects Claude to Wopee.io's autonomous testing platform for web apps. You get tools to dispatch full analysis suites with crawling, create blank test suites, fetch existing suites, and generate artifacts like user stories, test cases, and reusable test steps. The workflow is straightforward: either grab an existing suite UUID or create one, then use that to trigger test runs or pull generated content. Supports custom instructions during crawling and environment variables for things like auth tokens. Requires a Wopee project UUID and API key from their dashboard. Built for teams that want to hook AI agents directly into their testing pipeline without switching contexts.
- GitHub stars
- 4
- tools
- 10
- auth
- Secret needed
- transport
- STDIO
- env vars
- 3
- last updated
- Nov 12, 2026
Tools
10 toolsPublic tool metadata for what this MCP can expose to an agent.
wopee_fetch_analysis_suitesFetches all analysis suites for your project. This is a good starting point to see what suites are available.
Fetches all analysis suites for your project. This is a good starting point to see what suites are available.
No parameter schema in public metadata yet.
wopee_dispatch_analysisCreates and dispatches a new analysis/crawling suite for your project, or reruns an existing one.
Creates and dispatches a new analysis/crawling suite for your project, or reruns an existing one.
No parameter schema in public metadata yet.
wopee_create_blank_suiteCreates a blank analysis suite for your project.
Creates a blank analysis suite for your project.
No parameter schema in public metadata yet.
wopee_generate_artifactGenerates a specific file(artifact) for the selected suite.
Generates a specific file(artifact) for the selected suite.
No parameter schema in public metadata yet.
wopee_fetch_artifactFetches the enquired file(artifact) from the selected suite.
Fetches the enquired file(artifact) from the selected suite.
No parameter schema in public metadata yet.
wopee_update_artifactUpdates/replaces existing file(artifact) for a specific suite
Updates/replaces existing file(artifact) for a specific suite
No parameter schema in public metadata yet.
wopee_dispatch_agentDispatches an autonomous testing agent to execute test cases for a selected suite.
Dispatches an autonomous testing agent to execute test cases for a selected suite.
No parameter schema in public metadata yet.
wopee_fetch_recent_executionsFetches the most recent test case executions for the current project (up to 20, newest first).
Fetches the most recent test case executions for the current project (up to 20, newest first).
No parameter schema in public metadata yet.
wopee_fetch_executed_test_casesFetches executed test cases and their results for a given analysis suite.
Fetches executed test cases and their results for a given analysis suite.
No parameter schema in public metadata yet.
wopee_create_github_issueFiles a GitHub issue into the repository linked to the current project.
Files a GitHub issue into the repository linked to the current project.
No parameter schema in public metadata yet.
Sponsors
Configuration
WOPEE_API_KEY*secretWopee.io API key for authentication
WOPEE_PROJECT_UUID*UUID of the Wopee.io project to work with
WOPEE_API_URLWopee.io API base URL, only for dedicated or self-hosted instances (defaults to https://api.wopee.io)
Readme
Wopee.io MCP Server
AI-powered autonomous testing for your apps -- connect Claude, Cursor, or any MCP-compatible AI agent to Wopee.io and generate test cases, user stories, and run autonomous tests in seconds.
Requirements
- Node.js 20.18 or newer (Node.js 22 recommended). The server runs with
npx; there is nothing else to install. - A Wopee.io project with an API key. In Commander, open the project and go to More › Settings › API Keys; the same screen shows the project UUID. See API keys.
Setup
Per-client guides (Claude Code, Cursor, VS Code, Codex and more): docs.wopee.io/guides/wopee-mcp.
npx -y @wopee-io/init sets all of this up in a repo: it writes a git-ignored .env and the entries below for each agent you pick.
1. Put the credentials in the repo's .env
Details
- Repository
- github.com/wopee-io/wopee-mcp
- Category
- Search & Web Crawling
- Package
wopee-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active