A modern FastMCP server that exposes TestZeus SDK functionality to MCP clients like Claude Desktop and Cursor.
- FastMCP Integration: Built with the modern FastMCP framework for clean, efficient MCP server implementation
- Comprehensive TestZeus Operations: Complete test lifecycle management including tests, test runs, test run groups, environments, test data, and tags
- Advanced Scheduling: Test report scheduling with cron expressions and time-based filtering
- Multi-Channel Notifications: Email and webhook notification support for test results
- Report Management: Generate, download, and manage test reports in multiple formats (CTRF, PDF, CSV, ZIP)
- Resource Browsing: Browse all TestZeus entities as MCP resources for easy discovery
- Context Logging: Built-in logging and error handling with FastMCP Context
# Install the package
pip install testzeus-mcp-server
# Or using uv (faster)
uv tool install testzeus-mcp-server# Clone the repository
git clone https://github.com/testzeus/testzeus-mcp-server.git
cd testzeus-mcp-server
# Install using uv
uv sync-
Edit your Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:%APPDATA%/Claude/claude_desktop_config.json -
Add the TestZeus MCP server configuration:
{ "mcpServers": { "testzeus": { "command": "uv", "args": ["run", "testzeus-mcp-server"], "env": { "PATH": "/path/to/testzeus-mcp-server", "TESTZEUS_EMAIL": "[email protected]", "TESTZEUS_PASSWORD": "your-password" } } } } -
Restart Claude Desktop
-
Open Cursor Settings (
Cmd/Ctrl + ,) -
Navigate to Extensions → Model Context Protocol
-
Add a new MCP server with these settings:
{ "name": "TestZeus", "command": "uv", "args": ["run", "testzeus-mcp-server"], "env": { "PATH": "/path/to/testzeus-mcp-server", "TESTZEUS_EMAIL": "[email protected]", "TESTZEUS_PASSWORD": "your-password" } } -
Save and restart Cursor
User: "What tests do I have?"
Assistant: [Lists all available tests with descriptions]
User: "Show me details of my login test"
Assistant: [Displays comprehensive test information]
User: "Create a test for user registration flow"
Assistant: [Creates a new test with appropriate parameters]
User: "Tag it with 'authentication' and 'critical'"
Assistant: [Applies tags to the test]
User: "Run all tests tagged with 'smoke'"
Assistant: [Discovers and runs smoke tests]
User: "Check the status of recent test runs"
Assistant: [Shows test run statuses and results]
User: "Create a test run group for regression testing"
Assistant: [Creates a new test run group with multiple tests]
User: "Execute my smoke test group"
Assistant: [Runs all tests in the specified group]
User: "Download the report for my last test run group"
Assistant: [Downloads the group's test report in specified format]
User: "Create a weekly test report schedule"
Assistant: [Sets up automated test report generation]
User: "Schedule daily reports for tests tagged 'critical'"
Assistant: [Creates a schedule with tag-based filtering]
User: "List all my active schedules"
Assistant: [Shows all configured test report schedules]
User: "Create a notification channel for the dev team"
Assistant: [Sets up email notifications for test results]
User: "Add webhook notifications to my channel"
Assistant: [Configures webhook integration for real-time alerts]
User: "Show me all notification channels"
Assistant: [Lists all configured notification channels]
User: "Download the latest test report as PDF"
Assistant: [Downloads the most recent test report in PDF format]
User: "Get the CTRF report for test run group XYZ"
Assistant: [Downloads the Common Test Report Format file]
User: "Show me all available test reports"
Assistant: [Lists all generated test reports with their formats]
User: "Show me all test data"
Assistant: [Lists all available test data with details]
User: "Create test data for user signup scenarios"
Assistant: [Creates new test data with appropriate content]
User: "Add a CSV file to my test data"
Assistant: [Adds supporting file to test data]
User: "Remove all files from test data ID 123"
Assistant: [Removes all supporting files from the test data]
User: "Add a configuration file to my staging environment"
Assistant: [Adds the specified file to the environment]
User: "Remove the old config.json from environment"
Assistant: [Removes the specific file from environment]
User: "Clean up all files from my test environment"
Assistant: [Removes all supporting files from the environment]
User: "List all my tags"
Assistant: [Shows all available tags and their values]
User: "Create a tag for priority with value 'high'"
Assistant: [Creates a new tag for test organization]
- Test Management:
list_tests,get_test,create_test,update_test,delete_test,run_tests - Test Run Management:
list_test_runs,get_test_run,delete_test_run - Test Run Group Management:
list_test_run_groups,get_test_run_group,create_test_run_group,delete_test_run_group,cancel_test_run_group,download_test_run_group_report,download_test_run_group_attachments - Environment Management:
list_environments,get_environment,create_environment,update_environment,delete_environment,add_environment_file,remove_environment_file,remove_all_environment_files - Test Data Management:
list_test_data,get_test_data,create_test_data,update_test_data,delete_test_data,add_test_data_file,remove_test_data_file,remove_all_test_data_files - Tag Management:
list_tags,get_tag,create_tags,update_tag,delete_tag - Test Report Schedule Management:
list_test_report_schedules,get_test_report_schedule,create_test_report_schedule,update_test_report_schedule,delete_test_report_schedule - Notification Channel Management:
list_notification_channels,get_notification_channel,create_notification_channel,update_notification_channel,delete_notification_channel,remove_notification_config - Test Report Run Management:
list_test_report_runs,get_test_report_run,delete_test_report_run,download_test_report
tests://- Browse all teststest://{test_id}- View specific test detailstest-runs://- Browse all test runstest-run://{test_run_id}- View specific test run detailstest-run-groups://list- Browse all test run groupstest-run-group://{test_run_group_id}- View specific test run group detailsenvironments://- Browse all environmentsenvironment://{environment_id}- View specific environment detailstest-data://- Browse all test datatest-data://{test_data_id}- View specific test data detailstags://- Browse all tagstag://{tag_id}- View specific tag detailstest-report-schedules://list- Browse all test report schedulestest-report-schedule://{schedule_id}- View specific test report schedule detailsnotification-channels://list- Browse all notification channelsnotification-channel://{channel_id}- View specific notification channel detailstest-report-runs://list- Browse all test report runstest-report-run://{report_id}- View specific test report run details
- Python 3.11+
- uv (recommended) or pip
# Clone the repository
git clone https://github.com/testzeus/testzeus-mcp-server.git
cd testzeus-mcp-server
# Install development dependencies
uv sync --dev
# Or with pip
pip install -e ".[dev]"# Install dependencies
make install
# Run linting
make lint
# Run type checking
make type-check
# Run tests (when available)
make test
# Run the server locally
make run
# Clean build artifacts
make clean
# Build package
make build# Run directly
uv run testzeus-mcp-server
# Or with make
make run
# To get mcp server location
uv run mcp dev testzeus_mcp_server/server.py
# With custom environment
[email protected] uv run testzeus-mcp-serverthen copy the servers File and paste it into llm (claude, codex) config file.
- Configure your MCP client to use the local version
- Make your changes
- Test with your MCP client
- Run linting and type checking
testzeus-mcp-server/
├── testzeus_mcp_server/
│ ├── __init__.py
│ ├── __main__.py # Entry point
│ └── server.py # Main MCP server implementation
├── .github/
│ └── workflows/ # CI/CD workflows
├── docs/ # Documentation
├── examples/ # Usage examples
├── tests/ # Test files (when added)
├── pyproject.toml # Project configuration
├── uv.lock # Dependency lock file
├── Makefile # Development commands
└── README.md
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Run linting and type checking
- Submit a pull request
This server is built with FastMCP, providing:
- Decorative Tools: Simple
@mcp.tool()decorators for clean function definitions - Resource Templates: Dynamic resource URIs with
@mcp.resource()decorators - Context Integration: Built-in logging and error handling via FastMCP Context
- Modern Python: Type hints, async/await, and clean code structure
The implementation focuses purely on TestZeus business logic without MCP protocol boilerplate.
| Resource Type | URI Format | Description |
|---|---|---|
| Tests | test://id |
Test configurations and metadata |
| Test Runs | test-run://id |
Test execution instances |
| Environments | environment://id |
Test environment configurations |
| Test Data | test-data://id |
Test datasets and fixtures |
| Tags | tag://id |
Test organization tags |
| Test Run Groups | test-run-group://id |
Grouped test execution instances |
| Test Report Schedules | test-report-schedule://id |
Automated test report schedules |
| Notification Channels | notification-channel://id |
Notification configurations |
| Test Report Runs | test-report-run://id |
Generated test reports |
- Verify your email and password in the configuration
- Ensure your TestZeus account is active
# Check if the package is installed
pip list | grep testzeus-mcp-server
# Reinstall if needed
pip install --upgrade testzeus-mcp-server# On macOS/Linux, you might need to make the script executable
chmod +x $(which testzeus-mcp-server)Make sure environment variables are properly set in your MCP client configuration.
Find Path by running mcp inspector, copy the Servers File and paste it in llm (claude, codex, cursor, ...) config.json file.
uv run mcp dev testzeus_mcp_server/server.py
The server provides detailed error messages for common issues:
- Authentication failures
- Missing required parameters
- TestZeus API errors
- Network connectivity issues
- testzeus-sdk: Official TestZeus Python SDK
- fastmcp: Modern MCP server framework
- aiohttp: Async HTTP client
- pydantic: Data validation
- httpx: HTTP client for file downloads
MIT License - see LICENSE file for details.
Traditional tool-only approaches require users to know exactly what tools to call. With MCP resources:
- Discoverable: Browse available tests, schedules, reports, and configurations like files in a directory
- Contextual: See complete entity details before deciding what actions to take
- Natural: "Show me my test reports" instead of "call list_test_report_runs tool"
- Rich: Complete entity information including relationships, status, and metadata
- Real-time: Always current with your TestZeus account
- Comprehensive: Access to the full TestZeus ecosystem including advanced features like scheduling and notifications
This makes TestZeus truly conversational and intuitive to use with AI assistants, enabling complex test management workflows through natural language.
- install lib if not working : uv add python-dateutil
- for dev add sdk file : "testzeus-sdk @ file:///path_to_dir/testzeus-sdk", and add to pyproject
[tool.hatch.metadata]
allow-direct-references = truethen run
rm -rf .venv
uv syncthen check uv run python -c "import testzeus_sdk; print(testzeus_sdk.__file__)"
- If you only want local dev linking (editable mode), bypass pyproject dependency altogether
uv pip install -e /path/to/testzeus-sdk