PractiTest MCP. Audit complex test runs from a chat window.

Listen up. This server plugs PractiTest right into your AI client, so you don't have to jump through hoops across five different dashboards just to check on QA. It lets your agent orchestrate the entire testing lifecycle via natural conversation, mapping everything from initial business requirements down to specific failed steps.

Tracking Scope and Structure
When you need a high-level view of the project, you can start by listing all defined test sets using list_sets. This gives you names, current status flags, planned dates, and who's assigned to test them. To see every single test case in the system, run list_tests; this returns a JSON:API format list showing IDs, statuses, and any traceability links attached to those tests.

If you want to drill down on specific groups of tests, use get_set. You'll get the name, status, instance count, and execution summary for that exact test set. For an even finer grain view of a single set, list_instances shows every individual copy of a test case—the IDs and their last run statuses.

If you want to know what custom data fields are floating around in your project, check out list_custom_fields; it'll show the field name, type, and possible values.

Monitoring Execution and Failures
Need to track how well everything’s running? You can pull up a list of every test run execution using list_runs. This gives you IDs, status markers (PASSED or FAILED), duration times, and timestamps for every attempt. To trace exactly why something failed—a key capability for finding the root cause—the agent uses historical data from those runs to pinpoint precisely which step threw a failure flag.

To get all the nitty-gritty details on one test case, you run get_test. This pulls up everything: its name, specific steps it includes, what preconditions must be met before running, the expected results, and any linked requirements. You can also use list_examples to pull all details for a single test case.

Auditing Compliance and Defects
For compliance checks, you don't have to manually count anything. Running list_requirements gives you every business requirement, showing its current status and exactly how many test cases are pointing back to it in the project. This lets you audit system compliance at a glance.

When things go wrong, your agent handles defect triage. Using list_issues, you retrieve all reported defects, giving you the issue name, severity level, and which specific test instances they’re linked to. If you've got questions about who works here, run list_users to get names, emails, and assigned roles for every user in your PractiTest account.

The full capability set lets you:

• Audit the entire project against its business requirements using list_requirements.
• Identify open defects by listing issues with list_issues, showing severity and linked test instances.
• View complete test case details, including steps, expected results, and preconditions, via get_test.
• Map out all users and their roles using list_users.

It's this deep connection that lets your agent manage the entire QA scope—it doesn't just list things; it connects requirements to tests, tracks runs, and pins down defects. You don't need a dozen tabs open.