QA MCP Server
Allows verifying Lambda deployments via last-modified timestamps, comparing deployments across environments, confirming code is deployed before testing.
Allows finding PRs linked to Jira tickets, checking merge status and commit details, verifying code changes before testing.
Allows checking E2E test results, triggering builds with custom parameters, monitoring build history, waiting for builds and updating PR descriptions.
Allows finding and claiming tickets, marking passed/failed, generating test cases, summarizing comments, analyzing stories/epics for QA readiness.
Allows listing and reading messages from Webex rooms, searching for discussions, posting updates and notifications, and AI-powered conversation summaries.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@QA MCP Servercheck E2E test results for latest Jenkins build"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
QA MCP Server
An AI-powered QA automation server built on the Model Context Protocol (MCP). Integrates Jira, GitHub, Jenkins, AWS, and Webex into a unified interface for QA engineers.
Tool catalog: dwonng.github.io/qa-mcp-server — auto-generated from the
@mcp.tool()decorators inqa_mcp/server.pyon every push tomain.
Features
Jira Integration
Find tickets ready for QA or in progress
Claim tickets for validation (assign + set validator + update status)
Mark tickets as passed/failed with formatted comments
Generate AI-powered test cases from ticket descriptions
Summarize comment threads
Analyze stories and epics for QA readiness
GitHub Integration
Find PRs linked to Jira tickets
Check PR merge status and commit details
Verify code changes before testing
Jenkins Integration
Check E2E test results
Trigger builds with custom parameters
Monitor build history
Wait for builds and update PR descriptions with results
AWS Integration
Verify Lambda deployments via last-modified timestamps
Compare deployments across environments
Confirm code is deployed before testing
Webex Integration
List and read messages from Webex rooms
Search for discussions about specific topics
Post updates and notifications
AI-powered conversation summaries
Quick Start
Prerequisites
Python 3.11+
Docker (recommended) or local Python environment
API tokens for the services you want to use
Quick Install (Pre-built Image)
Add to your MCP configuration (~/.cursor/mcp.json):
{
"mcpServers": {
"qa-automation": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "JIRA_URL=https://your-jira.atlassian.net",
"-e", "JIRA_PERSONAL_TOKEN=your_token",
"-e", "GITHUB_TOKEN=ghp_your_token",
"ghcr.io/dwonng/qa-mcp-server:latest"
]
}
}
}Full Installation
Clone the repository
git clone https://github.com/DwonnG/qa-mcp-server.git cd qa-mcp-serverCreate your config
cp config_example.py config.py # Edit config.py with your Jira field IDs, Jenkins paths, etc.Add to your MCP client with all integrations:
{ "mcpServers": { "qa-automation": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "JIRA_URL=https://your-jira.atlassian.net", "-e", "JIRA_PERSONAL_TOKEN=your_token", "-e", "GITHUB_HOST=https://api.github.com", "-e", "GITHUB_TOKEN=ghp_your_token", "-e", "JENKINS_URL=https://your-jenkins.com", "-e", "JENKINS_USER=your_user", "-e", "JENKINS_TOKEN=your_token", "-e", "AWS_REGION=us-east-1", "-e", "WEBEX_TOKEN=your_webex_token", "-v", "$HOME/.aws:/root/.aws:ro", "-v", "$HOME/.config/qa-mcp-server/config.py:/app/config.py:ro", "ghcr.io/dwonng/qa-mcp-server:latest" ] } } }
Note: Mount your
config.pyfor custom JQL templates, field mappings, and Jenkins job paths.
Local Development
# Create virtual environment
python -m venv venv
source venv/bin/activate # or `venv\Scripts\activate` on Windows
# Install dependencies
pip install -r requirements.txt
# Run the server
python run.pyConfiguration
config.py
This file contains organization-specific settings:
Setting | Description |
| Custom field IDs for your Jira instance |
| Workflow transition IDs |
| Maps repos to Lambda function names |
| Jenkins job paths |
| JQL query templates |
| Template Epic key for release testing cloning |
See config_example.py for a template with documentation.
Environment Variables
Variable | Required | Description |
| Yes | Your Jira instance URL |
| Yes | Jira API token or PAT |
| No | Set to |
| No | GitHub API URL (default: api.github.com) |
| Yes | GitHub personal access token |
| Yes* | Jenkins server URL |
| Yes* | Jenkins username |
| Yes* | Jenkins API token |
| No | AWS region (default: us-east-1) |
| No | Webex bot or personal token |
*Required only if using Jenkins features
Available Tools
Jira Tools
qa_get_qa_queue- Find tickets waiting in the QA queue ready to be testedqa_find_in_progress- Find tickets developers are working onqa_claim_ticket- Claim a ticket for QA validationqa_resolve_pass- Mark ticket as QA passedqa_fail_ticket- Mark ticket as QA failed with bug reportqa_add_comment- Add a comment to any ticketqa_generate_test_cases- AI-generated test casesqa_summarize_comments- Summarize ticket commentsqa_analyze_story- Analyze story for QA readinessqa_analyze_epic- Analyze epic for release readinessqa_clone_release_epic- Clone release testing template Epic and tasks for a new version
GitHub Tools
qa_get_pr_info- Get PR detailsqa_find_prs_for_ticket- Find PRs linked to a Jira ticketqa_find_pr_for_commit- Find PR that introduced a commit
Jenkins Tools
qa_check_e2e_tests- Check E2E test resultsqa_get_recent_builds- Get build historyqa_trigger_e2e_tests- Trigger a test buildqa_get_my_test_builds- View your Jenkins test buildsqa_wait_for_build_and_update_pr- Wait for build and update PR
AWS Tools
qa_check_deployment- Verify Lambda deploymentqa_check_all_deployments- Check all Lambdas for a repoqa_compare_environments- Compare deployments across envsqa_get_deployment_summary- Formatted deployment status
Webex Tools
webex_list_rooms- List accessible Webex roomswebex_get_messages- Read messages from a roomwebex_summarize_room- AI summary of conversationwebex_post_message- Post a messagewebex_search_messages- Search for messages
Workflow Tools
qa_get_ticket_context- Full context (Jira + PRs + deployment)qa_verify_vulnerability_resolved- Verify vuln fix: find PR, check merge, verify deployment, check tests, resolve ticketqa_verify_and_resolve_vulnerability- One-click vuln verification
1-minute demo
See DEMO_1_MINUTE.md for a scripted 1-minute demo: find ready tickets → get details → AI test cases (optional: claim ticket).
Example Usage
You: "Are there any tickets ready for QA?"
AI: Found 3 tickets in QA status...
You: "Claim PROJ-12345 for QA"
AI: Claimed! Assigned to you, validator set, status updated to In Progress.
You: "Check if the PR for PROJ-12345 is merged and deployed"
AI: PR #456 merged 2 hours ago. Lambda last modified 1 hour ago. Deployed!
You: "Mark PROJ-12345 as passed - verified login flow works correctly"
AI: Resolved as passed with QA comment added.
You: "Clone the release testing template for version 3.3.0"
AI: Created new Epic O365-50500 "Release 3.3.0 Testing" with 8 test tasks cloned.Project Structure
qa-mcp-server/
├── run.py # Entry point
├── config.py # Your settings (git-ignored)
├── config_example.py # Settings template
├── requirements.txt # Dependencies
├── Dockerfile
├── README.md
├── LICENSE
│
├── qa_mcp/ # Main package
│ ├── __init__.py
│ ├── server.py # MCP server with all tools
│ ├── handlers.py # AI analysis handlers
│ ├── prompts.py # AI prompt templates
│ │
│ └── clients/ # Service integrations
│ ├── __init__.py
│ ├── jira.py
│ ├── github.py
│ ├── jenkins.py
│ ├── aws.py
│ ├── webex.py
│ └── ai.py
│
└── examples/ # Configuration examples
├── env.example # Environment variables template
└── mcp_config.json # MCP client config exampleArchitecture
┌─────────────────────────────────────────────────────────────┐
│ MCP Client │
│ (Cursor, Claude Desktop) │
└─────────────────────────┬───────────────────────────────────┘
│ MCP Protocol
┌─────────────────────────▼───────────────────────────────────┐
│ QA MCP Server │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Jira │ │ GitHub │ │ Jenkins │ │ AWS │ │
│ │ Client │ │ Client │ │ Client │ │ Client │ │
│ └────┬─────┘ └────┬─────┘ └────┬─────┘ └────┬─────┘ │
│ │ │ │ │ │
│ ┌────▼─────────────▼─────────────▼─────────────▼────┐ │
│ │ config.py │ │
│ │ (Organization-specific settings) │ │
│ └────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘Roadmap
v1.1 - Modular Integrations
Feature flags to enable/disable integrations (Webex, Jenkins, AWS)
Only register MCP tools for configured services
Graceful handling when optional services aren't configured
v1.2 - Flexible Jira Support
Make custom fields (validator, test_result) optional
Support Jira Cloud and Jira Server/Data Center
Configurable workflow transitions (not hardcoded IDs)
v1.3 - CI/CD Abstraction
Abstract CI/CD interface (not just Jenkins)
GitHub Actions support
GitLab CI support
v1.4 - Deployment Verification
Abstract deployment checker (not just AWS Lambda)
Kubernetes deployment status
Generic health check endpoints
v1.5 - Testing & Quality
Unit tests for clients
Integration test examples
CI pipeline for the project itself
Contributing
Contributions are welcome! Please:
Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request
License
MIT License - see LICENSE file for details.
Acknowledgments
Built with FastMCP
Inspired by the need to automate repetitive QA tasks
Thanks to the MCP community for the protocol specification
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DwonnG/qa-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server