# Testim MCP for AI Agents AI Agent Connect > Testim lets you trigger automated AI tests, inspect execution logs, and manage branches natively via your AI agent. Instead of jumping back and forth between your code editor and the Testim dashboard, you can run test plans, check results, and manage branches using plain English. It connects your QA pipelines directly to your workspace. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_dV0W5EQeoJdAE8PdakI0g1dIqsqeDyfRO2hc7Oq6/ai-agent-connect - **Tags:** automated-testing, end-to-end-testing, test-automation, qa-automation, execution-logs, test-suite ## Description Testim lets you trigger automated AI tests, inspect execution logs, and manage branches natively via your AI agent. You spend a lot of time switching tabs between your IDE and your testing platform to make sure a new deployment didn't break the checkout flow. This connection changes that by bringing your entire test suite into your AI client. You can ask your agent to run a specific regression suite or check the status of a nightly build without ever leaving your current screen. It handles the heavy lifting of navigating the dashboard for you. When you're trying to coordinate work across different features, you can manage branches and merge test changes through a simple conversation. It's a way to keep your testing cycle moving at the same speed as your development. You can find this and thousands of other connections in the Vinkius catalog to keep your tools in sync. It makes sure that your testing workflow actually keeps up with your coding pace. ## Tools ### get_test_details Pull all the technical details for a single Testim test. Use this to understand exactly how a specific test is configured. ### list_project_branches See all the parallel branches currently in your project. This gives you a clear view of all active development streams. ### list_tests Get a full list of all automated tests in your project. This is useful for auditing your overall test coverage. ### merge_project_branch Merge test changes from one branch into another one. This helps you sync your test configurations across different features. ### create_project_branch Create a new branch for your test development. This helps you keep different features isolated during the testing phase. ### get_execution_results See the pass or fail status for a specific test run. This provides immediate feedback on your latest deployment. ### run_tests_by_label Trigger a run for every test that has a specific label. This allows for quick, targeted testing of specific components. ### run_test_plan Start a run for a pre-defined test plan. This is the fastest way to kick off your standard regression cycles. ### run_test_suite Execute all tests within a specific test suite. Use this to run grouped tests for specific functional areas. ### run_specific_test Trigger an immediate run for one specific test. This is perfect for verifying a single UI fix or a specific user flow. ## Prompt Examples **Prompt:** ``` Did the nightly regression pass? ``` **Response:** ``` The nightly regression plan finished 5 minutes ago. Status: PASSED All 142 tests in the Nightly-Regression plan were successful. Would you like to see the execution logs? ``` **Prompt:** ``` Run the tests for the login page on the feature branch. ``` **Response:** ``` I have triggered the tests for the login page on the feature/new-login branch. Your execution ID is EXC-88291. I will let you know as soon as the results are in. ``` **Prompt:** ``` Show me all the active branches. ``` **Response:** ``` You have 4 active branches in your project: - master (Default) - feature/checkout-fix (ID: FTR22) - bugfix/header-overlap (ID: BUG09) - dev/mobile-nav (ID: DEV44) Which one would you like to work on? ``` ## Capabilities ### Trigger specific test runs Start a single test or a full plan by just asking your agent. ### Check test results See if your latest deployment passed or failed instantly in your chat. ### Manage test branches Create and merge branches to keep your test versions organized. ### Run tests by label Execute batches of tests based on specific tags or labels. ### View test details Get full information on any test in your project quickly. ### List project branches See all active development branches in one view. ## Use Cases ### Verifying a UI fix instantly A developer pushes a small CSS fix and asks their agent to run a specific test. The agent uses run_specific_test to verify the fix immediately. ### Triggering a nightly regression A QA engineer tells their agent to start the nightly regression. The agent uses run_test_plan to kick off the suite and reports back the execution ID. ### Auditing release health A release manager asks for the status of the latest build. The agent uses get_execution_results to confirm everything is green before the push. ### Managing parallel feature tests A team works on three features at once. They use create_project_branch and list_project_branches to keep their test environments organized. ## Benefits - Stop jumping between windows by running test plans and suites directly in your AI client using run_test_plan and run_test_suite. - Get faster feedback on deployments by using get_execution_results to see pass or fail statuses instantly. - Keep your test environment clean by using create_project_branch and merge_project_branch to manage versioning. - Run targeted tests quickly by using run_tests_by_label to execute only what you need for a specific feature. - Save time on audits by using list_tests and list_project_branches to get a bird's eye view of your project. ## How It Works The bottom line is you can manage your entire E2E testing lifecycle through a chat interface instead of manual dashboard navigation. 1. Connect your Testim Project ID and API Key to the Connector. 2. Tell your AI agent which test suite or plan you want to run. 3. Get back the execution ID and real-time status of your tests. ## Frequently Asked Questions **Can I use the Testim MCP to run my regression tests?** Yes, you can trigger full regression suites or specific test plans just by asking your AI agent. It handles the execution on the Testim platform and reports back the status to your chat. **Does the Testim MCP support specific test labels?** It does. You can ask your agent to run all tests that match a specific label, which is great for running targeted tests for certain features or environments. **How do I check if my latest deployment passed the tests?** You can ask your agent to fetch the results for a specific execution. It will pull the pass or fail status and any error details directly into your conversation. **Can I manage my test branches without opening the Testim dashboard?** Yes, this Connector lets you list, create, and merge test branches using natural language. It keeps your development workflow inside your editor or chat app. **Is this Connector good for QA engineers who need to audit test plans?** It is perfect for that. You can quickly list tests, check branch statuses, and retrieve execution IDs to ensure everything is green before a release. **Can I run a single test instead of a whole suite?** Yes, you can use the Connector to trigger an immediate run for one specific test. This is helpful for quickly verifying a single UI fix or a specific user flow. **Can my AI agent actually trigger test runs remotely?** Yes! You can ask your agent to list your available tests, pick an ID, and say 'Run this sequence'. Testim's dynamic runner architecture handles the load while your AI returns the execution ID for you to track. **How can it help me troubleshoot a failed test run?** Typically, you'd open the Testim dashboard, navigate to the specific test suite run, and read the logs. With this integration, you just instruct the agent to retrieve results for that specific Execution ID; it will summarize error strings immediately in markdown. **Can I merge test changes through the agent?** Absolutely. Because Testim supports branching, your agent can act as a command terminal. Ask to list branches, select a recently updated feature branch, and say 'Merge branch feature-login into master'.