Training course · Model Context Protocol (MCP) · Test Automation & QA

Model Context Protocol (MCP) for Test Automation and QA

Build and connect MCP servers securely: tools, resources and prompts for Claude Code, Cursor, Copilot and your own AI agents.

Duration
2 days (14 hrs)
Format
Online or on-site
Language
German or English
Participants
open dates or exclusive for your team
Certificate
Certificate of attendance

Overview

This course connects Model Context Protocol (MCP) with the everyday processes of Test Automation & QA. Participants work on realistic scenarios and leave with prompts, workflows and checklists they can use straight away.

The Model Context Protocol is an open standard that gives AI applications a uniform way to access external tools, data sources and workflows. Instead of building separate integrations for every assistant, you implement an MCP server once and use it in Claude Code, Claude Desktop, Cursor, GitHub Copilot, VS Code and your own agents. In this two-day course you learn the host, client and server architecture, the three core primitives of tools, resources and prompts, and the stdio and Streamable HTTP transports, applying each of them directly in your own code.

On day one you use the official TypeScript or Python SDK to build an MCP server that exposes internal APIs, databases or files to AI assistants in a controlled way, and you test it with the MCP Inspector. Day two covers remote servers, OAuth-based authorisation, security risks such as prompt injection and tool poisoning, and operations, logging and governance in an enterprise setting. You learn to write tool descriptions that models use reliably, and you leave knowing how to integrate MCP servers safely into your development and agent landscape.

Quality assurance is under pressure: release cycles are getting shorter, applications more complex, and AI-assisted coding produces more code in less time – all of which needs testing. Test automation engineers and QA professionals therefore benefit particularly from AI assistants and agents. These tools derive test cases from user stories and acceptance criteria, write Playwright or Cypress tests with robust selectors, generate API tests from OpenAPI specifications, analyse flaky tests and build test data generators. At the same time the role is shifting: QA becomes the function that systematically safeguards AI-generated code too. This course teaches you to use AI for test design, automation and failure analysis and to adapt your test strategy to the new pace of development.

The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.

Who is this course for?

  • Test automation engineers and SDETs
  • QA engineers and test managers
  • Developers responsible for test suites
  • Business testers moving into automation

Typical challenges we address

  • Unstable end-to-end tests with timing issues and fragile selectors
  • High effort for test case creation, maintenance and test data
  • Gaps in coverage of APIs, edge cases and failure scenarios
  • Growing volumes of AI-generated code that need targeted safeguarding

What you will be able to do

  • You explain the MCP architecture and choose between tools, resources and prompts for each use case.
  • You develop your own MCP server in TypeScript or Python and test it systematically.
  • You connect MCP servers to Claude Code, Cursor, Copilot and custom agents.
  • You run remote servers using Streamable HTTP and OAuth-based authorisation.
  • Derive test cases systematically from requirements with AI and automate them in Playwright, Cypress or API tests.
  • Analyse flaky tests and coverage gaps with AI support and fix them for good.
  • Adapt your test strategy to AI-assisted development and safeguard generated code in a targeted way.

Course outline

Day 1

Module 1 Architecture and core concepts
  • Roles of host, client and server and the lifecycle of a connection
  • JSON-RPC messages, capability negotiation and notifications
  • Tools, resources and prompts: choosing the right primitive
  • Client features such as sampling, roots and elicitation at a glance
Module 2 Building your own MCP server
  • Setting up a server with the official TypeScript or Python SDK
  • Defining tools cleanly with JSON Schema for inputs and outputs
  • Exposing resources and resource templates for documents, records and configuration
  • Testing and debugging with the MCP Inspector and meaningful error messages
Module 3 Connecting to Claude Code, Cursor, Copilot and agents
  • Configuring local stdio servers and remote servers in clients
  • Project-level and user-level configuration, approvals and permissions
  • Writing tool descriptions that models reliably select correctly
  • Integrating MCP servers into custom agents built with the Claude Agent SDK or OpenAI Agents SDK
Module 4 Transport, authorisation and operations
  • Streamable HTTP, session management and stateless servers
  • OAuth-based authorisation, token validation and integration with existing identity providers
  • Deploying as containers, on serverless platforms or behind a gateway
  • Logging, monitoring, rate limiting and versioning tool interfaces

Day 2

Module 5 Security and governance
  • Threats: prompt injection via tool results, tool poisoning, confused deputy
  • Least privilege, confirmation requirements and sandboxing
  • Reviewing and approving third-party servers within the organisation
  • Data protection, logging of personal data and requirements under GDPR and the EU AI Act
Module 6 Practice lab: Test Automation & QA
  • Deriving test cases from requirements
  • Writing Playwright and Cypress tests
  • Analysing flaky tests
  • API tests from specifications
  • Generating test data
  • Coverage and mutation testing
Module 7 Data protection, quality & transfer to daily work
  • Test data should be synthetic or effectively anonymised, as production data containing personal information must not be used unprotected in test environments or prompts (GDPR). Credentials for test systems belong in secret stores rather than test code, and in regulated sectors test results must be traceable and documented, for example as evidence under NIS2 or the Cyber Resilience Act.
  • Ground rules for safe AI use in your team
  • Checking results: facts, sources, tests and the four-eyes principle
  • Personal action plan for the next 30 days
  • Open questions, outlook and resources for further learning

Practical scenarios from your field

Deriving test cases from requirements

The assistant turns user stories and acceptance criteria into structured test cases with equivalence classes, boundary values and negative scenarios, optionally as Gherkin scenarios for behaviour-driven development.

Writing Playwright and Cypress tests

The AI writes end-to-end tests with role-based selectors, page objects or fixtures and proper waiting instead of fixed delays, and runs them iteratively until they are stable.

Analysing flaky tests

The agent examines test history, traces, screenshots and logs, identifies causes such as race conditions, test interdependencies or unstable test data, and proposes lasting fixes.

API tests from specifications

OpenAPI descriptions are turned into API tests for status codes, schemas, authentication and error cases, plus contract tests that surface interface changes between teams early.

Generating test data

The AI builds generators for realistic synthetic test data, factories and seed scripts that deliberately cover edge cases without relying on real personal data. Privacy issues in test environments are avoided.

Coverage and mutation testing

Coverage reports and mutation testing results are analysed, untested paths identified and missing tests added in a targeted way to increase the real value of the suite.

Possible hands-on projects

Flaky test report

A script that merges JUnit XML results from multiple CI runs, detects unstable tests and produces a prioritised list with failure patterns.

Test data generator

A CLI that creates realistic synthetic records, including edge cases, from a database schema or JSON schema. Data volume and distribution are fully configurable.

E2E suite for a demo app

A Playwright test suite with page objects, visual comparisons and CI integration, built by an AI agent for an existing web application.

Prerequisites

Solid programming skills in TypeScript/JavaScript or Python and a basic understanding of HTTP APIs and JSON. Some experience using AI assistants in day-to-day development is helpful. Experience in software testing or test automation and a working knowledge of at least one programming language such as JavaScript, TypeScript, Python or Java.

Technical requirements

A laptop with Node.js or Python, Git and a code editor, plus access to at least one MCP-capable client such as Claude Code, Claude Desktop, Cursor or VS Code with Copilot.

Data protection & compliance

Test data should be synthetic or effectively anonymised, as production data containing personal information must not be used unprotected in test environments or prompts (GDPR). Credentials for test systems belong in secret stores rather than test code, and in regulated sectors test results must be traceable and documented, for example as evidence under NIS2 or the Cyber Resilience Act.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Tue, 24 November 2026 – Wed, 25 November 2026 Online Request
  • Mon, 30 November 2026 – Tue, 1 December 2026 Munich Request
  • Wed, 9 December 2026 – Thu, 10 December 2026 Online Request
  • Tue, 19 January 2027 – Wed, 20 January 2027 Hanover Request
  • Wed, 27 January 2027 – Thu, 28 January 2027 Online Request
  • Thu, 4 February 2027 – Fri, 5 February 2027 Berlin Request

Frequently asked questions

Why would I need my own MCP server?

Whenever AI assistants need access to internal systems such as ticketing tools, databases, documentation or line-of-business applications. Your own server defines precisely which actions and data are available and can then be reused across several clients. That avoids isolated one-off integrations and keeps access firmly under your control.

Which programming language does the course use?

You can choose between TypeScript and Python, both of which have official SDKs. The concepts are identical and all exercises are available in both versions. Developers working in other languages still benefit, because the protocol is language-agnostic and SDKs for other languages follow a similar structure.

How secure is MCP for enterprise use?

The protocol provides mechanisms for authorisation and permissions, but real-world security depends on implementation and operations. Risks such as prompt injection through tool results or over-privileged servers are genuine. We cover concrete countermeasures, approval processes for third-party servers and how to handle personal data.

Do I need programming skills for this course?

A working knowledge of a programming language helps, since you should be able to read, understand and adapt generated tests. Business testers with little coding experience still benefit greatly, because the AI explains code and supports the move into automation. The exercises are designed to accommodate different levels of prior knowledge.

Will AI replace manual and exploratory QA?

No. AI automates recurring tasks such as test case creation, scripting and failure analysis, freeing up time for exploratory testing, risk assessment and acceptance. With AI-generated code in particular, the critical judgement of experienced QA professionals becomes more important, not less.

How much does “Model Context Protocol (MCP) for Test Automation and QA” cost?

The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.

Can I suggest my own date?

Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.

Is the course online or on-site?

Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.

More courses for Test Automation and QA

More Model Context Protocol (MCP) courses

All 29 Model Context Protocol (MCP) courses

Model Context Protocol (MCP) · MunichModel Context Protocol (MCP) · SalzburgModel Context Protocol (MCP) · BerlinModel Context Protocol (MCP) · AugsburgModel Context Protocol (MCP) · HanoverModel Context Protocol (MCP) · BremenModel Context Protocol (MCP) · StuttgartModel Context Protocol (MCP) · KaiserslauternModel Context Protocol (MCP) · Online