Wopee-io/wopee-mcp

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.
> **Documentation** | **Landing Page** | **Dashboard**
Setup
Prerequisites
- Node.js (v18 or higher recommended)
- An IDE that supports MCP (Model Context Protocol), such as Cursor or VSCode
MCP Server Configuration
Add this server to your MCP configuration.
Configuration Example
Required Environment Variables
- **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.
Optional Environment Variables
- **WOPEE_API_URL** - The Wopee API endpoint URL. Should be specified only for testing/development purposes.
Corporate Proxy Configuration
If you're behind a corporate proxy/VPN and experiencing connection timeouts, you can configure proxy settings using standard environment variables:
Supported Proxy Environment Variables
- **HTTPS_PROXY** or **https_proxy** - Proxy server URL for HTTPS connections (recommended)
- **HTTP_PROXY** or **http_proxy** - Fallback proxy server URL
Finding Your Proxy Settings
If 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:8080
- http://10.x.x.x:8080
- http://username:password@proxy.company.com:8080 (if authentication is required)
TLS / Certificate Issues
**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:
- **Self-signed certificates** (e.g. when WOPEE_API_URL points to an internal or dev server)
- **Corporate proxy / SSL inspection** (traffic re-encrypted with a corporate CA your machine doesn’t trust)
- **Missing CA certificates** in Node’s trust store
Preferred solutions (secure)
1. **Use a valid TLS certificate** – e.g. Let’s Encrypt, or an internal CA – and ensure the **full certificate chain** is served.
2. **Install the corporate or internal CA** so Node trusts it:
Example:
In MCP config env:
Insecure workaround (not recommended)
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.
Or in MCP config env:
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.
Getting Started
Most tools in this MCP server require a suiteUuid to operate. You have two options to get started:
Option 1: Use Existing Suites
Start by fetching your existing analysis suites:
This will return a list of all analysis suites with their UUIDs, which you can then use with other tools.
Option 2: Create a New Suite
If you don't have any suites yet, you have two options:
**Automatic Analysis:** Create and dispatch a full analysis/crawling suite:
**Blank Suite:** Create an empty suite for manual configuration:
Both options will return a suite UUID, which you can use for subsequent operations.
Available Tools
Suite Management
wopee_fetch_analysis_suites
Fetches all analysis suites for your project. This is a good starting point to see what suites are available.
- **Returns:** Array of analysis suites with their UUIDs, names, statuses, and metadata
**Example Usage:**