A Model Context Protocol (MCP) server for integrating with the Wopee testing platform. This server provides tools for dispatching analysis, generating app context, user stories, test cases, and running test executions through GraphQL API calls.
For VS Code:
Ctrl+Shift+P (or Cmd+Shift+P on Mac)wopee-mcpFor Cursor:
Ctrl+Shift+P (or Cmd+Shift+P on Mac)wopee-mcpnpm install -g wopee-mcp
.env file:# Create a .env file in the project root
cp env.example .env
# Edit the .env file with your API key
# WOPEE_API_KEY=your_api_key_here
# WOPEE_API_URL=https://api.wopee.io/
Alternative: Set system environment variables:
export WOPEE_API_KEY=your_api_key_here
export WOPEE_API_URL=https://api.wopee.io/
git clone <repository-url>
cd wopee-mcp
npm install
cp env.example .env
.env file with your Wopee API credentials:WOPEE_API_KEY=your_api_key_here
WOPEE_API_URL=https://api.wopee.io/
Before using the Wopee MCP server, ensure you have:
Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)MCP: Install Serverwopee-mcpInstall the package globally:
npm install -g wopee-mcp
Open VS Code settings (Ctrl+, or Cmd+,)
Search for "MCP" and find the MCP settings
Add server configuration:
{
"mcp.servers": {
"wopee": {
"command": "wopee-mcp",
"args": [],
"env": {
"WOPEE_API_KEY": "your_api_key_here",
"WOPEE_API_URL": "https://api.wopee.io/"
}
}
}
}
Restart VS Code to load the new MCP server
Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)MCP: Install Serverwopee-mcpInstall the package globally:
npm install -g wopee-mcp
Open Cursor settings (Ctrl+, or Cmd+,)
Navigate to MCP settings in the sidebar
Add server configuration:
{
"mcp.servers": {
"wopee": {
"command": "wopee-mcp",
"args": [],
"env": {
"WOPEE_API_KEY": "your_api_key_here",
"WOPEE_API_URL": "https://api.wopee.io/"
}
}
}
}
Restart Cursor to load the new MCP server
Once configured, you can use the Wopee tools in your chat interface:
@wopee wopee_dispatch_analysis
Project UUID: project-123
Iterations: 5
Suite Analysis Config:
- Starting URL: https://example.com
- Username: testuser
- Password: testpass
- Cookies Preference: ACCEPT_ALL
@wopee wopee_dispatch_agent
Project UUID: project-123
Suite UUID: suite-123
Analysis Identifier: analysis-123
Test Cases: [{"testCaseId": "test-1", "userStoryId": "story-1"}]
@wopee wopee_generate_app_context
Project UUID: project-123
Suite UUID: suite-123
Extra Prompt: Focus on user authentication flows
@wopee wopee_generate_general_user_stories
Project UUID: project-123
Suite UUID: suite-123
Extra Prompt: Include high-level business requirements
@wopee wopee_generate_user_stories
Project UUID: project-123
Suite UUID: suite-123
Extra Prompt: Include edge cases and error scenarios
@wopee wopee_generate_test_cases
Project UUID: project-123
Suite UUID: suite-123
Extra Prompt: Generate comprehensive test coverage
Selected User Stories: ["story-1", "story-2"]
Get existing app context for a project and suite.
Parameters:
projectUuid (string, required): UUID of the projectsuiteUuid (string, required): UUID of the test suiteExample:
{
"projectUuid": "project-123",
"suiteUuid": "suite-123"
}
Get existing user stories for a project and suite.
Parameters:
projectUuid (string, required): UUID of the projectsuiteUuid (string, required): UUID of the test suiteExample:
{
"projectUuid": "project-123",
"suiteUuid": "suite-123"
}
Get existing test cases for a project and suite.
Parameters:
projectUuid (string, required): UUID of the projectsuiteUuid (string, required): UUID of the test suiteExample:
{
"projectUuid": "project-123",
"suiteUuid": "suite-123"
}
Fetch all analysis suites for a given project.
Parameters:
projectUuid (string, required): UUID of the projectExample:
{
"projectUuid": "project-123"
}
Response: Returns an array of analysis suites with detailed information including:
"Command not found" error:
npm install -g wopee-mcp"API key not configured" error:
"Connection failed" error:
Tools not appearing:
wopee-mcp --versionwopee-mcp --help in terminalwopee_start_analysis tool with a simple URLThe server loads configuration from a .env file in the project root directory (where package.json is located).
WOPEE_API_KEY (required): Your Wopee API keyWOPEE_PROJECT_UUID (required): Your Wopee project UUIDWOPEE_API_URL (optional): Wopee API endpoint (defaults to https://api.wopee.io/)Copy the example file:
cp env.example .env
Edit the .env file in the project root:
# Wopee API Configuration
WOPEE_API_KEY=your_actual_api_key_here
WOPEE_PROJECT_UUID=your_project_uuid_here
WOPEE_API_URL=https://api.dev.wopee.io/
For MCP integration, update your mcp.json:
{
"mcpServers": {
"wopee": {
"command": "node",
"args": ["/path/to/wopee-mcp/dist/index.js"],
"env": {}
}
}
}
Note: The server automatically loads API keys from the .env file in the project root. No need to hardcode them in the MCP configuration.
Run the server in development mode:
npm run dev
Build and run the server:
npm run build
npm start
Run the test suite:
npm test
Run tests in watch mode:
npm run test:watch
Run tests with coverage:
npm run test:coverage
Clean build (removes dist and rebuilds):
npm run build:clean
Validate the package:
npm run validate
Prerequisites:
npm loginPublishing Workflow:
Prepare for release:
./scripts/prepare-release.sh
Publish the package:
./scripts/publish.sh
Or use npm scripts directly:
# Dry run (test without publishing)
npm run publish:dry-run
# Publish patch version (1.0.0 -> 1.0.1)
npm run publish:patch
# Publish minor version (1.0.0 -> 1.1.0)
npm run publish:minor
# Publish major version (1.0.0 -> 2.0.0)
npm run publish:major
Manual Publishing:
# 1. Update version
npm version patch # or minor, major
# 2. Publish
npm publish
Start a new analysis for a given URL.
Parameters:
url (string, required): URL of the application to analyzeExample:
{
"url": "https://example.com"
}
Generate application context based on analysis results.
Parameters:
analysisId (string, required): ID of the analysis to generate context fromprompt (string, optional): Optional prompt to modify the app context generationExample:
{
"analysisId": "analysis-123",
"prompt": "Focus on user authentication flows"
}
Generate user stories based on analysis results.
Parameters:
analysisId (string, required): ID of the analysis to generate user stories fromprompt (string, optional): Optional prompt to modify the user story generationExample:
{
"analysisId": "analysis-123",
"prompt": "Include edge cases and error scenarios"
}
Generate test files by fetching generated scenarios from the Wopee platform.
Parameters:
projectUuid (string, required): UUID of the projectsuiteUuid (string, required): UUID of the test suitebucket (string, required): Bucket name containing the generated scenariosExample:
{
"projectUuid": "e70d893f-b70a-4e45-a93a-7c08ef289aa9",
"suiteUuid": "f0cd35a5-0e11-4d33-995b-433706e10542",
"bucket": "project-suite-generated-scenarios"
}
Run tests either by analysis ID or specific test IDs.
Parameters:
analysisId (string, optional): ID of the analysis to run tests fortestIds (array of strings, optional): Array of specific test IDs to runNote: Either analysisId or testIds must be provided.
Example with analysis ID:
{
"analysisId": "analysis-123"
}
Example with test IDs:
{
"testIds": ["test-1", "test-2", "test-3"]
}
All tools return responses in the following format:
{
"success": true,
"data": { /* tool-specific data */ },
"message": "Success message",
"error": "Error message (only present if success is false)"
}
The server provides detailed error messages for:
src/
├── config.ts # Configuration management
├── graphql/
│ └── client.ts # GraphQL client implementation
├── tools/ # Individual tool implementations
│ ├── wopee_start_analysis.ts
│ ├── wopee_generate_app_context.ts
│ ├── wopee_generate_user_stories.ts
│ ├── wopee_generate_tests.ts
│ └── wopee_run_tests.ts
├── types/
│ └── index.ts # TypeScript type definitions
└── index.ts # Main MCP server implementation
tests/
├── config.test.ts # Configuration tests
└── tools/ # Tool-specific tests
├── wopee_start_analysis.test.ts
├── wopee_generate_tests.test.ts
└── wopee_run_tests.test.ts
src/tools/src/types/index.tssrc/index.tsThe project includes:
MIT License
This repository includes comprehensive GitHub Actions workflows for:
See AUTOMATION.md for detailed information about the automation setup.
To publish a new version:
Automatic (recommended):
git tag v1.0.0
git push origin v1.0.0
Manual via GitHub Actions:
For issues and questions, please create an issue in the repository.
FAQs
MCP server for Wopee.io autonomous testing platform
We found that wopee-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maintainers back GitHub’s npm security overhaul but raise concerns about CI/CD workflows, enterprise support, and token management.
Product
Socket Firewall is a free tool that blocks malicious packages at install time, giving developers proactive protection against rising supply chain attacks.
Research
Socket uncovers malicious Rust crates impersonating fast_log to steal Solana and Ethereum wallet keys from source code.