An end-to-end QA automation framework that generates test cases using RICE POT methodology, executes them via Playwright, captures evidence (screenshots, logs, reports), creates JIRA bugs for failures, and attaches artifacts to JIRA tickets.
This server has critical structural deficiencies. No MCP server registration code is visible, tools appear to be standalone Node.js scripts, not MCP tool definitions. No JSON Schema input schemas are present for any tool. Descriptions exist but are verbose (200+ chars) and lack actionable guidance. No output schemas documented. No error handling patterns. The codebase shows hardcoded credentials (email, issueKey), file paths, and API endpoints, severe security violations. This is not a functional MCP server; it's a collection of automation scripts.
Attaches test evidence files (screenshots, HTML reports, execution summaries, logs) to an existing JIRA issue. Authenticates via JIRA API token and uploads files via multipart form data
Creates test result directories, generates metadata JSON, Playwright execution logs, network logs, console logs, conversation history, and execution summary JSON with test results and artifact references
Creates a JIRA bug ticket in the SCRUM project with detailed bug information including summary, steps to reproduce, expected/actual results, environment details, and labels. Authenticates via JIRA API token and saves the created issue key and URL to a JSON file
Executes automated test cases against https://ui.freecrm.com using Playwright in headless mode, captures screenshots on failure, generates execution logs, and produces HTML and JSON reports
Generates an HTML test execution report from the execution summary JSON, displaying test case details, steps, expected results, actual results, status, and screenshot links
Generates 6 test cases (2 positive, 4 negative) for FreeCRM login page using RICE POT test design methodology and exports them to an Excel file (freecrm_login_testcases.xlsx)
No MCP server registration detected. Tools are standalone Node.js scripts, not MCP tool definitions. No evidence of MCP SDK integration, tool registration via tools/list, or protocol message handling.
No input schemas visible for any tool. create_jira_bug and attach_jira_evidence show partial parameter descriptions in comments, but no JSON Schema definitions. Other tools have no parameter documentation at all.
Hardcoded credentials and secrets in source code. attach_jira_evidence.js contains email '[email protected]', issueKey 'SCRUM-25', and hostname 'myqatask.atlassian.net'. JIRA API token read from env but email is hardcoded. Violates secret-injection pattern.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 26 | 2026-07-28+ | v2 |
No output schemas documented. Tools return file paths, JSON objects, and HTTP responses, but no schema definitions guide LLM parsing. build_artifacts.js writes multiple JSON files but does not declare their structure.
No error handling or recovery guidance. Scripts use console.log/console.error and process.exit(). No structured error responses, no actionable error messages, no retry guidance for LLMs.