# PractiTest MCP for AI Agents AI Agent Connect > PractiTest MCP lets you manage your QA test cycles and project data directly through your AI agent. Instead of clicking through menus to check test results or create new runs, you can just ask your agent to pull the data or perform the action. It connects your PractiTest workspace to your AI client so you can handle test management, requirement tracking, and QA reporting in one place. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_WPLaAtvDfNnWYy76l0P0pqFN9UmkzlstxMxSTja8/ai-agent-connect - **Tags:** qa-testing, test-management, bug-tracking, quality-assurance, test-automation ## Description PractiTest lets you manage your QA test cycles and project data directly through your AI agent. Managing a software testing lifecycle usually means jumping between tabs to check requirements, create new test instances, and aggregate results into reports. This Connector changes that by giving your AI agent a direct line into your PractiTest workspace. You can ask your agent to find a specific requirement, check the status of a test run, or even spin up new test instances without leaving your chat interface. It makes it way easier to keep your QA data organized and accessible. Because Vinkius hosts this integration, you can plug it into your existing workflow and start querying your test data immediately. Instead of manual data entry or hunting for project IDs, your agent handles the heavy lifting of navigating the PractiTest API for you. You get a way to manage your testing environment using natural language, making it much faster to keep your team updated on the current state of quality assurance. ## Tools ### get_requirement Get the specific details of a requirement within a project. This helps you quickly verify QA coverage. ### get_test Pull the information for a specific test from your PractiTest workspace. Use this to see test details quickly. ### list_instances See all the instances currently grouped within a specific project. This is great for monitoring active testing. ### list_projects View all projects that your API token has permission to access. Use this to navigate between different projects. ### list_requirements Get a full list of requirements for a specific project. Use this to see what needs to be tested. ### list_runs See all the test runs associated with a particular project. This helps you track progress over time. ### list_tests Pull a list of all tests included in a specific project. Use this to get a bird's eye view of your test suite. ### create_instance Make a new instance in a project by providing the necessary JSON data. This automates your test setup. ### create_run Start a new test run in a project by sending the required JSON data. It saves you from manual form filling. ### create_test Add a new test to a project using a JSON data string. Use this to expand your test suite quickly. ### get_project Get the core details of a specific project in your account. This is useful for quick project verification. ## Prompt Examples **Prompt:** ``` What's the status of the test runs for our latest web project? ``` **Response:** ``` ### Current Test Runs: Web Project | Run ID | Status | Test Count | Last Updated | | :--- | :--- | :--- | :--- | | **#4502** | ✅ Passed | 42 | 2 mins ago | | **#4505** | 🔄 In Progress | 12 | Just now | | **#4498** | ❌ Failed | 3 | 1 hour ago | **Summary:** The latest run (#4505) is currently active with 12 tests remaining. Run #4502 passed successfully. ``` **Prompt:** ``` Create a new test called 'Password Reset' in project 505. ``` **Response:** ``` I've created the new test for you. **Test Details:** - **Name:** Password Reset - **Project ID:** 505 - **Status:** Created successfully Would you like me to add any specific steps or requirements to this test now? ``` **Prompt:** ``` List all requirements for the 'Login' project. ``` **Response:** ``` Here are the requirements for the **Login** project: * **REQ-101:** User must be able to log in with email. * **REQ-102:** User must be able to log in with social accounts. * **REQ-103:** Password must be masked during entry. * **REQ-104:** MFA must be triggered after login. Total requirements found: 4. ``` ## Capabilities ### Pull project requirements Get details on specific requirements to check your QA coverage. ### Create test runs Generate new test runs within a project using your AI agent. ### List active instances See all instances in a project to monitor current testing progress. ### Fetch test details Retrieve specific information about any test in your workspace. ### Automate report data Gather live QA metrics to build status updates quickly. ## Use Cases ### Checking coverage A QA lead asks the agent to list all requirements for project X to see if any are missing tests. The agent uses list_requirements to pull the data instantly. ### Quick run setup A developer wants to start a new test run and asks the agent to create it using the standard JSON template. The agent uses create_run to handle the request. ### Status updates A project manager asks for a list of all active instances to see the current progress of the latest release. The agent uses list_instances to provide a quick summary. ### Requirement deep-dive A tester needs to see the specific details of a bug-fix requirement and asks the agent to fetch it. The agent uses get_requirement to pull the exact details. ## Benefits - Faster test creation: Use create_test and create_run to set up testing cycles in seconds without manual form filling. - Better requirement tracking: Quickly check QA coverage by pulling requirements with list_requirements and get_requirement. - Real-time status checks: Use list_runs and list_instances to see exactly where your testing stands right now. - Easier data aggregation: Pull live QA data to create status reports without copy-pasting from the PractiTest UI. - Centralized QA management: Keep your entire testing workflow inside your favorite AI chat interface instead of switching apps. ## How It Works The bottom line is you get a conversational interface for your entire PractiTest QA workspace. 1. Connect your PractiTest API token to the Connector in the Vinkius dashboard. 2. Open your preferred AI client like Claude or Cursor and select the PractiTest MCP. 3. Ask your agent to perform tasks like listing projects or creating new tests. ## Frequently Asked Questions **Can the PractiTest MCP help me create test runs?** Yes, it lets your agent create new test runs directly. You just provide the details, and the agent handles the creation in your workspace. **How does the PractiTest MCP help with QA coverage?** You can use it to list and fetch requirements. This helps you quickly see which parts of your project are covered by tests. **Can I use the PractiTest MCP to see my projects?** Yes, the Connector can list all projects your API token can access, making it easy to switch contexts. **Does the PractiTest MCP work with Cursor or Claude?** It works with any MCP-compatible client, including Claude, Cursor, and Windsurf. **Can I automate my QA reporting with the PractiTest MCP?** You can pull live QA data and project details to build reports much faster than manual copy-pasting. **What do I need to set up the PractiTest MCP?** You just need a PractiTest API token. Once you provide that to the Connector, your agent can start querying your data. **Can the AI Agent execute tests inside PractiTest?** While the agent cannot run automated testing scripts directly in PractiTest, it can create Test Runs, log results into Instances, and manage the administrative side of QA efficiently. **Are custom fields supported when creating new tests?** Yes! The AI agent formats API requests dynamically. If your workspace requires custom fields, simply instruct the agent on which attributes to include during the test creation. **Is there a limit on how many tests the agent can list at once?** The agent adheres to PractiTest API pagination limits. By default, it returns a single page of results, but you can explicitly ask the AI to query a different page number or limit.