# TestRail MCP for AI Agents AI Agent Connect > TestRail MCP connects your AI client directly to your QA management platform. It lets you query test projects, pull manual test steps, and get real-time run metrics without leaving your IDE or chat window. It turns your QA data into actionable context for debugging and release planning. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_a3w9BHlckmfMyJzVTNVdATfpLpvPdZbPanOT8MYC/ai-agent-connect - **Tags:** qa-testing, test-suites, test-cases, release-management, test-automation, quality-assurance ## Description Stop jumping between your code editor and a browser tab full of QA tickets just to find out why a build failed or what the specific manual steps are for a bug. This Connector brings your entire quality assurance lifecycle into your conversational workflow. Instead of hunting through folders or waiting for a lead to send a screenshot, you can just ask your agent to pull the exact preconditions for a test case or list the milestones for an upcoming release. It handles the heavy lifting of navigating complex project hierarchies so you can focus on the actual work. When you use this through the Vinkius catalog, you get a direct line to your project's health. You can see which tests are blocked, what's currently running, and get the full logic for manual cases instantly. It makes your QA data searchable and usable in the same place you're already writing code. It bridges the gap between your technical tasks and the QA documentation that often feels disconnected from the actual development process. Instead of copy-pasting from a web UI into your tickets or chat history, you can have your agent do the heavy lifting. This means your team stays in sync with the latest testing results without the usual overhead of manual status checks. It's about making sure that the information you need to do your job is always one prompt away. ## Tools ### list_test_projects Lists all available projects on your instance to help you find project IDs. This is the first step for navigating your data. ### list_test_runs Lists all test runs within a project so you can see historical and active data. Use this to find specific run IDs. ### list_project_sections Pulls the folder hierarchy and sections for a project to help with navigation. This helps you see how tests are organized. ### list_test_suites Lists all test suites within a specific project. Use this to identify different testing areas. ### list_run_tests Lists all test case instances within a specific test run to see exactly what was executed. This is perfect for debugging failures. ### get_test_case_details Retrieves the full logic, preconditions, and steps for a specific manual test case. Use this to see exactly how a test should be performed. ### get_test_project_details Fetches the specific details and configuration for a TestRail project. This helps you understand the scope of a project quickly. ### get_test_run_details Provides the summary and status for a specific test run. Use this to check the health of a specific execution. ### list_test_cases Lists all test cases within a project, with the option to filter by suite. This is great for finding specific test logic. ### list_project_milestones Pulls a list of all milestones for a specific project. Use this to track release dates and major QA goals. ## Prompt Examples **Prompt:** ``` What are the manual steps for test case 1285? ``` **Response:** ``` Case ID `1285`: **OAuth Registration Gateway Failure** > **Priority:** CRITICAL_HIGH | **Estimate:** 5m > **Preconditions:** Server must be isolated via VPN routing rules. **Steps:** 1. Call initialization endpoint bypassing token assignment. (Expected Result: API triggers `ERR401` gracefully without cascading stack traces). 2. Force brute-force retries mimicking scripts. (Expected Result: IP locks completely after exactly 5th try). Would you like me to help you draft a script for these steps? ``` **Prompt:** ``` Give me a summary of the last test run. ``` **Response:** ``` Metrics recovered for Test Run **`#403: Sanity Validation Build.v45`**: - **Total Executed Tests:** 80 - **Passed:** 71 ✅ - **Failed (Action Required):** 6 ❌ - **Blocked (Dependency issues):** 3 ⏸️ This run has notable defect traces. Would you like me to extract the exact test lists behind the 6 failed triggers? ``` **Prompt:** ``` What milestones are left for the Core Payment project? ``` **Response:** ``` Project: **Core Payment Backend** Remaining Milestones: - **Regression Testing** (Due: Oct 15) - **Final Smoke Test** (Due: Oct 20) - **Production Deployment** (Due: Oct 25) All milestones are currently on track. Would you like to see the specific test suites associated with the next milestone? ``` ## Capabilities ### Pull manual test steps Get exact instructions and preconditions for any specific test case instantly. ### Check run status See which tests passed, failed, or are blocked in an active run. ### Browse project hierarchies Navigate folders and sections to find specific test suites and projects. ### Track release milestones View upcoming QA deadlines and project goals without opening a browser. ### Fetch project details Get high-level info on project IDs and suite architectures. ## Use Cases ### Debugging a reported bug A developer asks the agent for the manual steps of a failing case to see the exact reproduction steps and preconditions. ### Release status check A product manager asks the agent to summarize the status of the current test run to see if the build is ready for production. ### Automating manual tests An automation engineer uses the agent to pull all test cases from a suite to begin writing scripts for a new feature. ### Onboarding to a new project A new hire asks the agent to list all sections and milestones to understand the project scope and testing organization. ## Benefits - Stop context switching by pulling manual test steps into your IDE using get_test_case_details. - Get instant visibility into release progress by querying list_project_milestones for upcoming deadlines. - Speed up bug fixing by letting your agent fetch list_test_runs to see exactly where things are failing. - Map out complex test repositories quickly by using list_project_sections to see the full folder structure. - Simplify automation work by using list_test_cases to find the logic you need to turn into code. ## How It Works The bottom line is you get a direct bridge between your QA data and your active development workspace. 1. Subscribe to the TestRail MCP on Vinkius. 2. Enter your TestRail Base URL and your API credentials in your AI client. 3. Ask your agent to pull test cases, run metrics, or project milestones. ## Frequently Asked Questions **Can the TestRail MCP help me see manual test steps?** Yes, it pulls the exact steps and preconditions for any manual test case so you don't have to hunt for them in the web app. **How does TestRail MCP help with bug fixing?** It lets your agent fetch the specific reproduction steps for a case, making it much faster to see what's going wrong without leaving your IDE. **Can I use TestRail MCP to check release status?** You can ask your agent to summarize the latest test runs and check upcoming milestones to see if you're ready to ship. **Does TestRail MCP work with Cursor or Claude?** Yes, it connects to any MCP-compatible client like Claude, Cursor, and Windsurf to bring your QA data into those tools. **Can TestRail MCP help with test automation?** It's great for this because you can pull manual test logic and then ask your agent to help you write the code for it. **How do I connect TestRail MCP to my instance?** You just need to provide your TestRail Base URL along with your API credentials in your AI client. **Can I use my regular TestRail password to authenticate?** Technically yes, as TestRail uses HTTP Basic Auth. However, it is highly discouraged for security purposes. The gold standard is to generate a dedicated API Key via your profile interface strictly tied to this connection. **Why isn't the API agent responding despite my credentials being correct?** TestRail requires the instance administrator to explicitly configure system-level API enablement. Ask your workspace admin to go to Administration > Site Settings > API and tick 'Enable API' box. **Can the AI rewrite my test cases explicitly inside your TestRail app?** No. Consistent with security best practices, the TestRail MCP functions only as a powerful read-only query extraction engine. It retrieves metadata, sections, milestones, and reports, protecting your ground-truth data from accidental AI deletion.