# ContextQA MCP for AI Agents AI Agent Connect > ContextQA lets you manage and run automated test suites directly through your AI client. You can trigger test runs, monitor AI-healing progress, and audit API payloads without switching tabs. It connects your testing environment to your workspace so you can debug failures and check release readiness using natural language. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_arIg6fOatFWYf4ywr6Asm6h013dTDEa83NCzuGoP/ai-agent-connect - **Tags:** automated-testing, ai-healing, test-automation, qa-testing, software-quality ## Description ContextQA changes how you handle the QA lifecycle by bringing your test suite data into your daily conversation with an AI agent. Instead of hunting through dashboards to see why a specific test failed or manually triggering a suite in a separate tab, you can just ask your agent to do it. You get a direct line to your test environments, allowing you to check project structures, pull specific test cases, and see exactly where a run hit a snag. It handles the heavy lifting of navigating your testing infrastructure while you focus on the results. When you find a failure, you can dig into the root cause models and see the screen captures or DOM changes that caused the issue. It's a lot easier to maintain high software quality when your testing data is always just one prompt away. Having this available through the Vinkius catalog makes it simple to plug into your existing workflow and get started immediately. You can audit your API configurations, verify your payloads, and keep your release pipeline moving without the usual friction of manual status checks. ## Tools ### list_executions Inspect internal interaction tracking for global Run chunks. Use this to see a high level view of all your recent runs. ### list_projects Identify bounded ContextQA test environments and their automated validations. This helps you see all your test environments at once. ### get_project Retrieve specific Project mapping UUIDs to analyze execution spaces. Use this to get the exact ID for a project you want to manage. ### get_execution Run static queries to target specific AI-healing Run states. This is how you see the detailed status of a single test run. ### list_environments List static configurations and mapping limits for target layers. Use this to see your available testing environments. ### list_suites Extract structural data for asynchronous GUI test Suites. This gives you a clear overview of your GUI test coverage. ### list_cases Discover the routing limits and structures of ContextQA cases. Use this to see how your specific test cases are organized. ### get_case Validate Data Science object extraction and track specific step boundaries. This helps you see the exact steps within a single case. ### list_api_tests Extract native REST and OpenAPI configurations. This allows you to audit your API tests quickly. ### trigger_run Dispatch live testing commands to route Jobs against pipelines. Use this to start a new test run immediately. ## Prompt Examples **Prompt:** ``` List all test suites for project 'vinkius-app-prod' ``` **Response:** ``` I found 4 suites in 'vinkius-app-prod': 'Checkout-Flow', 'User-Onboarding', 'API-Security-Scan', and 'Mobile-Sanity'. Which one would you like to audit or trigger? ``` **Prompt:** ``` Trigger a run for suite 'Checkout-Flow' in project 'vinkius-app-prod' ``` **Response:** ``` Test run triggered! Suite 'Checkout-Flow' has been queued. You can monitor the progress using Execution ID 'exec_123'. I will notify you once the AI-healing analysis is complete. ``` **Prompt:** ``` Show me why the last execution of project 'mobile-app' failed ``` **Response:** ``` Analyzing last execution for 'mobile-app'... It failed at step 5: 'Click Login Button'. The element was not found. ContextQA's AI-healing attempted to locate it but failed due to a structural change in the DOM. ``` ## Capabilities ### Trigger live test runs Dispatch testing commands to your test clusters using natural language. ### Monitor AI-healing progress Check the status of active runs and see where the healing process succeeded or failed. ### Audit API test payloads Extract REST and OpenAPI configurations to verify your payloads against specs. ### Extract GUI test suites Pull structural data from your GUI test suites to see your current test coverage. ### Inspect failed test boundaries Identify the exact point of failure in a test run with root-cause models. ## Use Cases ### Debugging a failed login flow A QA Engineer needs to see why a login flow failed. They ask the agent to show the last execution for the mobile project. ### Verifying an API payload A Developer wants to verify an API payload. They use the agent to list API tests and check the OpenAPI configurations. ### Checking production suite status A DevOps lead wants to check the status of the production suite. They ask the agent to list executions for the production project. ### Verifying release readiness A Product Owner wants to know if the checkout flow is ready. They ask the agent to trigger a run for that specific suite. ## Benefits - You can trigger test runs instantly with trigger_run without leaving your workspace. - You can see exactly why a test failed using get_execution to inspect AI-healing states. - You can audit your API configurations and payloads using list_api_tests. - You can organize your test environments and projects quickly with list_projects. - You can extract GUI test suites and cases using list_suites and list_cases. ## How It Works The bottom line is you can manage your entire automated testing pipeline through a single chat interface. 1. Connect your ContextQA API key from your dashboard settings. 2. Link the Connector to your preferred AI client like Claude or Cursor. 3. Ask your agent to list projects or trigger specific test suites. ## Frequently Asked Questions **How can ContextQA help my QA team?** It lets you manage test suites and monitor AI-healing results directly in your AI client. You can trigger runs and audit failures without leaving your workspace. **Can I use ContextQA to check my API tests?** Yes, you can use it to extract REST and OpenAPI configurations and verify that your payloads match your specs. **Does ContextQA support AI-healing?** Yes, it allows you to inspect specific AI-healing states and see exactly where the healing process succeeded or failed. **Can I trigger test runs with ContextQA?** You can dispatch live testing commands to your test clusters using natural language prompts. **How do I see why a specific test case failed?** You can ask your agent to inspect a specific execution to see the root-cause models and screen captures. **Can ContextQA help with my GUI tests?** Yes, it can perform structural extraction on your GUI test suites and help you identify points of failure. **Can my agent help me identify the root cause of a failed test case?** Yes. Use the 'get_case' tool to resolve the AI root-cause model for a specific test. The agent retrieves the definitions and AI insights to confirm exactly why a boundary was breached during execution. **How do I trigger a full test suite run via chat?** Provide the 'project_id' and 'suite_id' to your agent and use the 'trigger_run' mutation. The agent will command the backend to queue the tests against live ContextQA test clusters instantly. **Can I see screen captures of failed test steps through the agent?** The 'get_execution' tool retrieves detailed logs tracking failing step boundaries. Where supported by ContextQA, the agent can surface the associated physical screen capture limits to help you visualize the failure.