Wopee 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.

npx wopee-mcp

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

{
  "mcpServers": {
    "wopee": {
      "command": "npx wopee-mcp",
      "env": {
        "WOPEE_PROJECT_UUID": "your-project-uuid-here",
        "WOPEE_API_KEY": "your-api-key-here"
      }
    }
  }
}

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:

{
  "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"
      }
    }
  }
}

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:

   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"
   }
   

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.

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 `PYTHONHT

... View full README on GitHub