TestZeus FastMCP Server

A modern FastMCP server that exposes TestZeus SDK functionality to MCP clients like Claude Desktop and Cursor.

Features

• FastMCP Integration: Built with the modern FastMCP framework for clean, efficient MCP server implementation
• Core TestZeus Operations: manage tests, test runs, tags and environments
• Resource Browsing: Browse TestZeus entities as MCP resources
• Context Logging: Built-in logging and error handling with FastMCP Context

Quick Start

For End Users

Option 1: Install from PyPI (Recommended)

# Install the package
pip install testzeus-mcp-server

# Or using uv (faster)
uv tool install testzeus-mcp-server

Option 2: Install from Source

# Clone the repository
git clone https://github.com/testzeus/testzeus-mcp-server.git
cd testzeus-mcp-server

# Install using uv
uv sync

Configuration

Claude Desktop

1. Edit your Claude Desktop configuration file:

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

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

3. Restart Claude Desktop

Cursor IDE

1. Open Cursor Settings (Cmd/Ctrl + ,)

2. Navigate to Extensions → Model Context Protocol

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

4. Save and restart Cursor

Usage

Basic Operations

Viewing Tests

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]

Creating Tests

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]

Running Tests

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]

Managing Test Data

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]

Managing Environment Files

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]

Managing Tags

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]

Available Tools

• Test Management: list_tests, get_test, create_test, update_test, delete_test, run_test
• Test Run Management: list_test_runs, get_test_run, create_test_run, delete_test_run
• 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

Available Resources

• tests:// - Browse all tests
• test://{test_id} - View specific test details
• test-runs:// - Browse all test runs
• test-run://{test_run_id} - View specific test run details
• environments:// - Browse all environments
• environment://{environment_id} - View specific environment details
• test-data:// - Browse all test data
• test-data://{test_data_id} - View specific test data details
• tags:// - Browse all tags
• tag://{tag_id} - View specific tag details

Development

For Developers

Prerequisites

• Python 3.11+
• uv (recommended) or pip

Setup Development Environment

# 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]"

Development Commands

# 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

Running from Source

# 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-server

then copy the servers File and paste it into llm (claude, codex) config file.

Testing Your Changes

1. Configure your MCP client to use the local version
2. Make your changes
3. Test with your MCP client
4. Run linting and type checking

Project Structure

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

Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Run linting and type checking
6. Submit a pull request

Architecture

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 URI Schemes

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

Troubleshooting

Common Issues

Authentication Failed

• Verify your email and password in the configuration
• Ensure your TestZeus account is active

MCP Server Not Found

# Check if the package is installed
pip list | grep testzeus-mcp-server

# Reinstall if needed
pip install --upgrade testzeus-mcp-server

Permission Denied

# On macOS/Linux, you might need to make the script executable
chmod +x $(which testzeus-mcp-server)

Environment Variables Not Set

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

Error Handling

The server provides detailed error messages for common issues:

• Authentication failures
• Missing required parameters
• TestZeus API errors
• Network connectivity issues

Dependencies

• testzeus-sdk: Official TestZeus Python SDK
• fastmcp: Modern MCP server framework
• aiohttp: Async HTTP client
• pydantic: Data validation

License

MIT License - see LICENSE file for details.

Why MCP Resources?

Traditional tool-only approaches require users to know exactly what tools to call. With MCP resources:

• Discoverable: Browse available tests like files in a directory
• Contextual: See test details before deciding what to do
• Natural: "Show me my tests" instead of "call list_tests tool"
• Rich: Complete entity information, not just IDs
• Real-time: Always current with your TestZeus account

This makes TestZeus truly conversational and intuitive to use with AI assistants.