MCP For Claude Marketplace
PractiTest

PractiTest MCP Connector for Claude

A+

Bring your end-to-end QA management to your AI — list tests, instances, test sets, requirements, and trace logical software defects natively.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner
More Details Connect to Claude

Connect your PractiTest workspaces to any AI agent and empower it to orchestrate the entire QA lifecycle from physical requirements tracing to defect mapping natively via chat conversations.

What you can do

  • Test Cases & Sets — Tell the AI to investigate any Test Case or Test Set, discovering exact preconditions and expected results (list_tests, get_test, list_sets)
  • Test Instances & Runs — Retrieve deep execution histories pinpointing exactly which step caused a regression bounding PASSED/FAILED statuses (list_runs)
  • Requirements Tracking — Audit physical system compliance extracting arrays dictating QA delivery thresholds (list_requirements)
  • Issue Mapping — Find exact Software Defects bound natively to QA traces verifying complex failure logic (list_issues)

How it works

  1. Subscribe to this server
  2. Supply your PractiTest Personal API Token and Project ID
  3. Launch Claude, Cursor, or any compatible MCP client to instruct the AI with full test management autonomy

Forget moving between dashboard views trying to identify where a trace broke down. Simply ask the agent 'Why did the latest Payment flow fail?'

Who is this for?

  • QA Automation Engineers — verify integration outputs traversing test run histories instantaneously
  • Product Owners — read live requirement statuses cross-referencing execution states mapped in the chat window
  • Software Developers — dive into reported Issues parsing exact test execution failures natively before diving into code
qa-testingtest-managementbug-trackingrequirements-traceabilitytest-automationsoftware-quality

10 tools expose this connector's capabilities to your AI agent.

list_tests

List all test cases in a PractiTest project. PractiTest is an end-to-end test management platform with traceability from requirements to defects. Returns test names, IDs, statuses, custom fields, and traceability links. Uses JSON:API format

get_test

Get full details of a PractiTest test case including name, description, preconditions, steps, expected results, custom fields, and requirement links

list_sets

List all test sets in a PractiTest project. Test sets group test instances for execution. Returns set names, statuses, planned/actual dates, and assigned testers

get_set

Get full details of a PractiTest test set including name, status, instances count, and execution summary

list_instances

List all test instances in a PractiTest test set. Instances are test-set-specific copies of test cases. Returns instance IDs, test references, and last run statuses

list_runs

List all runs for a PractiTest test instance. Runs record actual test execution results. Returns run IDs, statuses (PASSED/FAILED/BLOCKED/NOT_RUN/N_A), durations, and timestamps

list_requirements

List all requirements in a PractiTest project. Requirements provide traceability to test cases and defects. Returns names, statuses, and linked test counts

list_issues

List all issues (defects) in a PractiTest project. Returns issue names, statuses, severities, and linked test references

list_custom_fields

List all custom fields in a PractiTest project. Returns field names, types, applicable entities, and possible values

list_users

List all users in the PractiTest account. Returns user names, emails, roles, and statuses

See how to talk to your AI agent using PractiTest.

List all tests inside our active QA regression instance and find the ones mapped as failed.

I queried `list_runs` pulling executions. Exactly 3 Test Runs crashed the regression suite: Run ID `1202` (Login Flow Bypass), Run ID `1203` (Cart State Mismatch), and Run ID `1209` (Payment Fallback Failed). Should I extract step histories for #1209 using `get_test`?

Do we have any new custom fields we should be aware of inside the requirements area?

I analyzed `list_custom_fields` crossing your dictionaries. Let's see... a new custom List field 'GDPR Category' (ID 402) was instantiated targeting Requirement entities with possible values strings: ['P1', 'P2', 'Ignore'].

Are there any open defects (issues) linked directly to testing scenarios surrounding multi-currency operations?

Investigating `list_issues`, I see one highly relevant defect: 'EUR vs GBP Cart Rounding Error' (Issue ID #91). It carries a `High` severity and it strictly ties to instances in your 'Multicurrency V2' test cluster. Current status: UNRESOLVED.

Yes. If an execution failed, the agent uses `list_runs` for the instance. Since an instance maps directly to test steps, the AI inherently decodes the exact execution traces to show you the failing parameters.

Related Connectors

LI

Livepeer (Decentralized Video) MCP

34 tools Official

Manage decentralized video infrastructure via Livepeer — upload assets, manage live streams, create clips, and monitor viewership metrics directly from any AI agent.

C View details →
AD

Ayuntamiento de Barcelona (CKAN) MCP

7 tools Official

Access the Open Data BCN portal to query urban datasets, environmental records, and public statistics directly through AI.

F View details →
WR

Wrike MCP

6 tools Official

Manage tasks, projects, and folders on Wrike — the most versatile work management platform for teams.

A+ View details →
VE

VSPN Esports DB MCP

10 tools Official

Automate esports intelligence via VSPN — fetch live tournament brackets, deep player telemetry, and team rosters directly from any AI agent.

A+ View details →