Which integrations are available for this server?

Allows integration with Windsurf (Codeium) IDE to use MCP tools for QA analysis. Integration for generating CI/CD pipelines with stages, caching, coverage gates, and quality checks. Allows integration with VS Code via GitHub Copilot Agent to use MCP tools for QA analysis directly in the editor. Supported platform for configuring and running the MCP server with Claude Desktop on Linux systems. Supported platform for configuring and running the MCP server with Claude Desktop on macOS systems. Required runtime for the MCP server, and the server provides integration tools for testing Node.js applications. Used for dependency management and running the MCP server, with integration for generating CI/CD pipelines. Provides a security test checklist based on OWASP Top 10 for different feature types, including SAST/DAST and acceptance criteria.

How do I use MCP QA Engineer SDET?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP QA Engineer SDET Generate Gherkin scenarios for user login feature" 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.

de en es ja ko pt ru zh

MCP QA Engineer SDET

by qamichaelmaia

Overview Schema Related Servers Score Discussions

JavaScript

Local

MCP QA Engineer SDET

Server MCP with specialized tools for software QA. Connect to any IDE or client compatible with the Model Context Protocol and gain access to User Story analysis, test strategy, BDD/Gherkin, contract testing (Pact), integration testing (Testcontainers), performance testing (k6), security testing (OWASP), and CI/CD.

Prerequisites

Node.js 18+
npm 9+
Git

Installation

# 1. Clonar ou entrar na pasta
cd mcp-testing

# 2. Instalar dependências
npm install

# 3. Compilar TypeScript
npm run build

After building, the server will be available at dist/index.js.

For development without building:

npm run dev   # usa tsx — não requer compilação

Available Tools (tools)

Tool	Description
`analyze_user_story`	Complete User Story analysis: decomposition, criteria, scenarios per layer, risk map, test data, checklist
`generate_test_strategy`	Test strategy for the system: adapted pyramid, tools, CI/CD, coverage goals, roadmap
`create_gherkin_scenarios`	BDD scenarios in Gherkin: happy path, negatives, edge cases, Scenario Outline, data tables
`design_contract_tests`	Pact contracts (CDC): interactions, provider states, matchers, versioning, can-i-deploy
`design_integration_tests`	Integration tests: Testcontainers, WireMock, setup/teardown, concurrency, observability
`generate_performance_plan`	Complete k6 plan: smoke/load/stress/spike/soak, thresholds, results analysis
`security_test_checklist`	OWASP Top 10 checklist per feature type + headers, SAST/DAST, acceptance criteria
`review_test_code`	Test code review: anti-patterns, isolation, assertions, mocks, coverage
`troubleshoot_flaky_test`	Flaky test diagnosis: hypotheses, steps, code corrections, prevention policy
`generate_ci_pipeline`	CI/CD pipeline with stages, parallelism, cache, minimum coverage, quality gates
`quality_checklist`	Checklists per artifact: user story, plan, test case, code, contract, suite, bug report

Available Resources (resources)

URI	Description
`qa://pyramid`	Test pyramid: distribution, objectives, anti-patterns
`qa://tool-matrix`	Tool selection matrix by language and need
`qa://gherkin-template`	Complete BDD Feature File template
`qa://k6-templates`	Ready k6 scripts: smoke, load, stress, spike, soak
`qa://glossary`	Glossary of QA/SDET terms

Available Prompts

Prompt	Description
`analyze-story`	User Story analysis session
`start-tdd`	Guided TDD session (Red → Green → Refactor)
`write-test-plan`	Test plan elaboration
`debug-failure`	Failure diagnosis in test or environment

Configuration by IDE

VS Code (GitHub Copilot Agent)

Create or edit .vscode/mcp.json in the root of your workspace:

{
  "servers": {
    "qa-sdet": {
      "type": "stdio",
      "command": "node",
      "args": ["${workspaceFolder}/mcp-testing/dist/index.js"]
    }
  }
}

Requires GitHub Copilot with MCP support (VS Code 1.99+). Enable it in Settings → GitHub Copilot → MCP.

Alternative via user settings.json (global scope):

{
  "mcp": {
    "servers": {
      "qa-sdet": {
        "type": "stdio",
        "command": "node",
        "args": ["C:/caminho/absoluto/mcp-testing/dist/index.js"]
      }
    }
  }
}

Cursor

Create .cursor/mcp.json in the project root:

{
  "mcpServers": {
    "qa-sdet": {
      "command": "node",
      "args": ["./mcp-testing/dist/index.js"]
    }
  }
}

Or configure globally in Cursor → Settings → MCP via the graphical interface.

Claude Desktop

Windows — edit %APPDATA%\Claude\claude_desktop_config.json:

{
  "mcpServers": {
    "qa-sdet": {
      "command": "node",
      "args": ["C:\\Users\\SeuUsuario\\caminho\\mcp-testing\\dist\\index.js"]
    }
  }
}

macOS — edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "qa-sdet": {
      "command": "node",
      "args": ["/Users/seuusuario/caminho/mcp-testing/dist/index.js"]
    }
  }
}

Linux — edit ~/.config/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "qa-sdet": {
      "command": "node",
      "args": ["/home/seuusuario/caminho/mcp-testing/dist/index.js"]
    }
  }
}

Restart Claude Desktop after editing the file.

Windsurf (Codeium)

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "qa-sdet": {
      "command": "node",
      "args": ["/caminho/absoluto/mcp-testing/dist/index.js"]
    }
  }
}

Continue.dev

Edit ~/.continue/config.json (or config.yaml):

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "node",
          "args": ["/caminho/absoluto/mcp-testing/dist/index.js"]
        }
      }
    ]
  }
}

Zed

Edit the Zed configuration file (~/.config/zed/settings.json):

{
  "context_servers": {
    "qa-sdet": {
      "command": {
        "path": "node",
        "args": ["/caminho/absoluto/mcp-testing/dist/index.js"]
      }
    }
  }
}

Any MCP client (generic)

The server uses standard stdio transport. Configure with:

{
  "command": "node",
  "args": ["/caminho/absoluto/para/mcp-testing/dist/index.js"],
  "transport": "stdio"
}

Usage examples

In the IDE chat

Analise esta User Story:
"Como usuário, quero resetar minha senha para recuperar acesso à conta"

The assistant will call analyze_user_story automatically and return the structured analysis.

Crie cenários Gherkin para o fluxo de checkout com os critérios:
- Usuário com carrinho não vazio pode finalizar compra
- Pagamento com cartão inválido é rejeitado com mensagem
- Frete é calculado pelo CEP do endereço de entrega

Gere um plano de performance para POST /api/orders com SLA p95 < 400ms

Revise este código de teste:
[colar o código]

Using the pre-built prompts

In IDEs that support MCP prompts (like Claude Desktop and Cursor):

/analyze-story — User Story analysis
/start-tdd — TDD session
/write-test-plan — test plan
/debug-failure — failure diagnosis

Check if the server is running

# Executar diretamente e verificar output de inicialização
node dist/index.js
# Deve exibir em stderr: "MCP QA SDET Server v2.0.0 pronto."

# Ou via npm
npm start

Development

# Modo desenvolvimento (sem compilação)
npm run dev

# Compilar para produção
npm run build

# Watch mode (recompila ao salvar)
npx tsc --watch

Troubleshooting

"Cannot find module" when running

Run npm run build before npm start. The dist/ directory must exist.

Server not appearing in the IDE

Check the absolute path in the configuration file
Confirm that Node.js 18+ is installed: node --version
Confirm that the build was generated: ls dist/index.js
Restart the IDE after changing the configuration

TypeScript errors during build

npx tsc --noEmit   # verificar erros sem gerar arquivos

Timeout when connecting

Add timeout in the client configuration:

{
  "command": "node",
  "args": ["/caminho/dist/index.js"],
  "timeout": 10000
}

Project structure

mcp-testing/
├── src/
│   └── index.ts          # Servidor MCP completo
├── dist/                 # Gerado pelo build (não versionar)
│   └── index.js
├── package.json
├── tsconfig.json
├── SYSTEM_PROMPT.md      # Prompt de sistema QA SDET Senior
└── README.md

Technologies

Model Context Protocol SDK
TypeScript 5
Node.js 18+

Developed by Michael Maia — QA Engineer SDET

LinkedIn · GitHub · QA Playground

This server cannot be installed

license - not tested

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Qase Test Management
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
PlanExe
MCP server for generating rough-draft project plans from natural-language prompts.

View all MCP Connectors

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/qamichaelmaia/qa-testing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server