Server data from the Official MCP Registry
AI testing agents for web apps — dispatch test runs, crawls, fetch artifacts and status.
AI testing agents for web apps — dispatch test runs, crawls, fetch artifacts and status.
Valid MCP server (1 strong, 1 medium validity signals). 8 known CVEs in dependencies (0 critical, 6 high severity) ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry.
12 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
Set these up before or after installing:
Environment variable: WOPEE_API_KEY
Environment variable: WOPEE_PROJECT_UUID
Environment variable: WOPEE_API_URL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-autonomous-testing-wopee-mcp": {
"env": {
"WOPEE_API_KEY": "your-wopee-api-key-here",
"WOPEE_API_URL": "your-wopee-api-url-here",
"WOPEE_PROJECT_UUID": "your-wopee-project-uuid-here"
},
"args": [
"-y",
"wopee-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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.
npx wopee-mcp
Add this server to your MCP configuration.
{
"mcpServers": {
"wopee": {
"command": "npx wopee-mcp",
"env": {
"WOPEE_PROJECT_UUID": "your-project-uuid-here",
"WOPEE_API_KEY": "your-api-key-here"
}
}
}
}
WOPEE_PROJECT_UUID - Your Wopee project UUID. This identifies which project you're working with.WOPEE_API_KEY - Your Wopee API key. You can create one at cmd.wopee.io, in your project's settings.WOPEE_API_URL - The Wopee API endpoint URL. Should be specified only for testing/development purposes.If you're behind a corporate proxy/VPN and experiencing connection timeouts, you can configure proxy settings using standard environment variables:
{
"mcpServers": {
"wopee": {
"command": "npx wopee-mcp",
"env": {
"WOPEE_PROJECT_UUID": "your-project-uuid-here",
"WOPEE_API_KEY": "your-api-key-here",
"HTTPS_PROXY": "http://your-proxy-server:8080"
}
}
}
}
HTTPS_PROXY or https_proxy - Proxy server URL for HTTPS connections (recommended)HTTP_PROXY or http_proxy - Fallback proxy server URLIf you're unsure about your proxy settings, check your VS Code settings (settings.json) for http.proxy value, or consult your IT department. Common corporate proxy formats:
http://proxy.company.com:8080http://10.x.x.x:8080http://username:password@proxy.company.com:8080 (if authentication is required)This is not required for MCP to work. If you see HTTPS or certificate-related errors, that indicates a TLS or certificate trust issue in your environment.
If the server fails with errors such as UNABLE_TO_VERIFY_LEAF_SIGNATURE or certificate has expired, it may be due to:
WOPEE_API_URL points to an internal or dev server)Use a valid TLS certificate – e.g. Let’s Encrypt, or an internal CA – and ensure the full certificate chain is served.
Install the corporate or internal CA so Node trusts it:
Example:
export NODE_EXTRA_CA_CERTS=/etc/ssl/certs/internal-ca.pem
In MCP config env:
"env": {
"WOPEE_PROJECT_UUID": "your-project-uuid-here",
"WOPEE_API_KEY": "your-api-key-here",
"NODE_EXTRA_CA_CERTS": "/path/to/ca.pem"
}
For local debugging only, you may disable TLS verification in Node. This should never be used in production, as it disables HTTPS security and exposes traffic to interception.
export NODE_TLS_REJECT_UNAUTHORIZED=0
Or in MCP config env:
"env": {
"WOPEE_PROJECT_UUID": "your-project-uuid-here",
"WOPEE_API_KEY": "your-api-key-here",
"NODE_TLS_REJECT_UNAUTHORIZED": "0"
}
Treat this as a debug-only escape hatch, not a normal setup step.
Note: Some users have reported setting PYTHONHTTPSVERIFY=0 as well. This MCP server does not use Python; that variable has no effect on it. It would only apply if you run a Python-based MCP host or other tooling that also performs HTTPS in the same environment—outside the scope of this server.
Most tools in this MCP server require a suiteUuid to operate. You have two options to get started:
Start by fetching your existing analysis suites:
Use the wopee_fetch_analysis_suites tool to retrieve all available suites for your project.
This will return a list of all analysis suites with their UUIDs, which you can then use with other tools.
If you don't have any suites yet, you have two options:
Automatic Analysis: Create and dispatch a full analysis/crawling suite:
Use the wopee_dispatch_analysis tool to create and dispatch a new analysis/crawling suite.
Blank Suite: Create an empty suite for manual configuration:
Use the wopee_create_blank_suite tool to create a blank analysis suite.
Both options will return a suite UUID, which you can use for subsequent operations.
wopee_fetch_analysis_suitesFetches all analysis suites for your project. This is a good starting point to see what suites are available.
Example Usage:
Fetch all existing analysis suites for my project
wopee_dispatch_analysisCreates and dispatches a new analysis/crawling suite for your project, or reruns an existing one. Use this to start a fresh analysis session or to re-trigger a previous analysis.
additionalInstructions (optional) - Additional instructions to guide the agent during the analysis/crawling phase (e.g. focus areas, things to ignore, login steps, etc.)additionalVariables (optional) - Additional environment variables to pass to the analysis. Array of objects, each with:
key - Variable name, must be uppercase with underscores only (e.g. MY_VAR, BASE_URL)value - Variable value (non-empty string)rerun (optional) - If provided, reruns an existing analysis suite instead of creating a new one. Object with:
suiteUuid - UUID of the existing suite to rerunanalysisIdentifier - Analysis identifier of the existing suitemode - Rerun mode: FULL (reruns the entire analysis including crawling and generation) or CRAWLING (reruns only the crawling phase)Example Usage:
Dispatch a new analysis suite
Dispatch a new analysis suite and focus on the checkout flow
Dispatch a new analysis suite with additional variables CARD_FILAMENT=123321123 and AUTH_TOKEN=abc123
Rerun the full analysis for suite <suiteUuid> with analysis identifier <analysisIdentifier>
Rerun only the crawling phase for suite <suiteUuid> with analysis identifier <analysisIdentifier>
wopee_create_blank_suiteCreates a blank analysis suite for your project. Use this when you want to manually configure and populate a suite rather than having it automatically analyzed.
Example Usage:
Create a blank analysis suite for my project
These tools generate various artifacts for a specific suite. All require a suiteUuid and type to generate.
wopee_generate_artifactGenerates a specific file(artifact) for the selected suite.
suiteUuid - The UUID of the suitetype - "APP_CONTEXT" | "GENERAL_USER_STORIES" | "USER_STORIES_WITH_TEST_CASES" | "TEST_CASES" | "TEST_CASE_STEPS" | "REUSABLE_TEST_CASES" | "REUSABLE_TEST_CASE_STEPS"Example Usage:
Generate app context for my most recent analysis suite
These tools retrieve generated artifacts for a specific suite. All require a suiteUuid and type.
wopee_fetch_artifactFetches the enquired file(artifact) from the selected suite.
suiteUuid - The UUID of the suitetype - "APP_CONTEXT" | "GENERAL_USER_STORIES" | "USER_STORIES" | "PLAYWRIGHT_CODE" | "PROJECT_CONTEXT"identifier - Identifier of the test case to fetch Playwright code for, ex. US003:TC004Example Usage:
Fetch user stories for the latest suite
These tools are used to update or set certain files(artifacts) for a specific suite. suiteUuid, type and content is required.
wopee_update_artifactUpdates/replaces existing file(artifact) for a specific suite
suiteUuid - The UUID of the suitetype - "APP_CONTEXT" | "GENERAL_USER_STORIES" | "USER_STORIES" | "PLAYWRIGHT_CODE" | "PROJECT_CONTEXT"content - Markdown content for app context, general user stories and project context, structured JSON for user storiesidentifier - Identifier of the test case to fetch Playwright code for, ex. US003:TC004Example Usage:
Update app context file for the most recent suite with this content: <YourMarkdown>
wopee_dispatch_agentDispatches an autonomous testing agent to execute test cases for a selected suite.
suiteUuid - The UUID of the suite containing the test casesanalysisIdentifier - The analysis identifier for the suitetestCases - Array of test case objects to execute, each containing:
testCaseId - The ID of the test caseuserStoryId - The ID of the associated user storyExample Usage:
Dispatch agent for my latest suite's user story US001 and test case TC003
wopee_fetch_executed_test_casesFetches executed test cases and their results for a given analysis suite. Use this to check the status and reports of dispatched agent runs.
suiteUuid - The UUID of the analysis suite to fetch results foranalysisIdentifier (optional) - Analysis identifier to narrow results (e.g. A068)Example Usage:
Fetch test results for suite <suiteUuid>
Show me the executed test cases for my latest analysis suite
Start with a suite:
wopee_fetch_analysis_suites to see existing suites, ORwopee_dispatch_analysis to create a new suiteGenerate artifacts:
wopee_generate_artifact with APP_CONTEXT and specific suiteUuidwopee_generate_artifact with GENERAL_USER_STORIES and specific suiteUuidwopee_generate_artifact with USER_STORIES_WITH_TEST_CASES and specific suiteUuidwopee_generate_artifact with REUSABLE_TEST_CASES and specific suiteUuidwopee_generate_artifact with REUSABLE_TEST_CASE_STEPS and specific suiteUuidwopee_generate_artifact with TEST_CASE_STEPS and specific suiteUuidFetch generated content:
Run tests:
wopee_dispatch_agent to execute test cases with the autonomous testing agentCheck results:
wopee_fetch_executed_test_cases to check the status and reports of dispatched agent runsfetch-test-results prompt for a formatted summary of all test resultsfetch-project-summaryFetches analysis suites and their user stories/test cases, then displays a formatted summary with two markdown tables: a suite overview and a detailed test case breakdown.
fetch-test-resultsFetches analysis suites and their executed test case results, then displays formatted markdown tables showing execution status, agent report status, and code report status for each test case. Also surfaces failed report details.
suiteUuid. Always start by fetching or creating a suite.wopee_dispatch_analysis tool will go through whole cycle of processing - crawling the application and generating all of the files(artifacts) one by one.Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.