# TestMonitor MCP for AI Agents AI Agent Connect > TestMonitor MCP lets you pull your QA project data, test runs, and defect logs directly into your AI chat. Instead of hunting through dashboards, you can ask your agent to list projects, check milestone progress, or map requirements against feature specs. It connects your cloud infrastructure so you can manage QA tasks and team assignments without leaving your workspace. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_oUSR4BtkMlXIV58CHABZT39Yq2DSP4r9MO0hKGi4/ai-agent-connect - **Tags:** qa-testing, test-runs, requirements-management, milestone-tracking, test-coverage, issue-tracking ## Description Managing a QA lifecycle usually feels like a game of whack-a-mole between different tabs. You're constantly switching between project boards to see if a milestone hit its deadline or digging through long lists of defects to find the right one for a specific test project. This Connector changes that by letting your AI agent do the heavy lifting for you. You can just ask for a summary of what's finished, which bugs are still open, and who is actually assigned to a specific role. It pulls real-time data from your TestMonitor instance so you can stay focused on the actual work. By adding this to your toolkit via the Vinkius catalog, you move away from manual data entry and toward a conversational way of managing your test coverage and requirements. It's about getting the right answer in seconds rather than spending ten minutes navigating a UI to find a single test case detail. You can cross-reference requirements against feature specs without ever leaving your chat window. It turns your QA data into a searchable knowledge base that your agent can query whenever you need a status update or a deep dive into a specific test run. ## Tools ### get_project_details Pull specific metadata for a single TestMonitor project. This helps you see the status and coverage of a project at a glance. ### list_test_cases Get a full list of all test cases in a project. Use this to check your total test coverage. ### list_issues Retrieve a list of all defects or issues within a project. Use this to see what bugs need fixing. ### list_milestones View all project milestones and their current status. This keeps your project timeline visible. ### list_projects Get a list of all projects available on your instance. This is the starting point for finding your projects. ### list_requirements See all requirements mapped to a project. Use this to ensure every feature is accounted for. ### list_test_runs See all test runs associated with a specific project. This helps you track recent testing activity. ### list_account_users View all users and their roles in your workspace. This helps you see who owns which part of the project. ### get_test_case_details Get the full steps and expected results for a specific test case. This lets you see exactly what a test is supposed to do. ### get_test_run_details Pull the specific results and details for a single test run. This gives you a deep dive into a specific run. ## Prompt Examples **Prompt:** ``` What's the status of the Vinkius CRM Engine project? ``` **Response:** ``` Project: **Vinkius CRM Engine V2** - **Status:** Active - **Milestones:** 4 of 10 completed - **Recent Activity:** 2 test runs completed in the last 24 hours. Would you like me to list the specific milestones or the latest test runs for this project? ``` **Prompt:** ``` Show me the steps for test case 5521. ``` **Response:** ``` ### Test Case 5521: API Logout Auth Rejection - **Status:** Approved - **Linked Requirement:** REQ-10 - **Steps:** 1. Force invalid Bearer string to the `/auth/logout` endpoint. 2. Ensure cache header remains un-poisoned. - **Expected Result:** Returns raw 401 HTTP unauthorized block immediately. ``` **Prompt:** ``` Are there any open bugs for the CRM project? ``` **Response:** ``` I found 2 open issues for the Vinkius CRM Engine V2 project: | ID | Title | State | | :--- | :--- | :--- | | **ISS-91** | Registration Webhook drops payload | In Progress | | **ISS-99** | Avatar uploads broken on edge | Open | Should I pull more details on either of these? ``` ## Capabilities ### List ongoing QA projects Get a full list of all projects available on your TestMonitor instance. ### Retrieve project metadata Pull specific details like status and coverage for a single project. ### View all test runs See every test run associated with a specific project in one list. ### Pull test run details Get the specific results and status for an individual test run. ### Check milestones See all project milestones and their current progress. ### List test cases Retrieve all test cases within a project to check coverage. ### Get test case details Access the full steps and expected results for a specific test case. ### Map requirements List all requirements mapped to a project for easy auditing. ### Find defects Query all issues and software defects linked to a project. ### See workspace users List all users and their roles within your account. ## Use Cases ### Pre-meeting status updates A Quality Director needs a summary of all milestones and test runs across three projects before a stand-up. They ask the agent to list them all and get a summary in seconds. ### Rapid defect triaging A Bug Triager wants to see all open issues for a specific project. They use the agent to pull the list and identify the most critical defects for the day. ### Requirement gap analysis A Product Owner wants to see if a new requirement has corresponding test cases. They ask the agent to list requirements and cross-reference them against the test case list. ### Deep dive into failing tests A Developer needs the specific steps for a failing test case. They ask the agent to pull the details for a specific test case ID to see the expected results. ## Benefits - Get instant summaries of project milestones without opening your browser. - Quickly pull defect lists to prioritize bug fixes for your team. - Map requirements to test cases automatically to ensure full coverage. - Check test run statuses across multiple projects in one request. - Identify user roles and ownership instantly to clear up task confusion. - Access specific test case steps and expected results without navigating menus. ## How It Works The bottom line is you get a conversational interface for your entire QA management suite. 1. Subscribe to the TestMonitor MCP through the Vinkius platform. 2. Enter your TestMonitor subdomain and Personal Access Token in your AI client. 3. Ask your agent to pull project data, list milestones, or fetch defect logs. ## Frequently Asked Questions **Can I use TestMonitor MCP to track bugs in my QA workflow?** Yes. You can ask your agent to list all issues or defects for a specific project. It pulls the data directly so you can see what needs fixing without opening your browser. **How does TestMonitor MCP help with QA requirements?** It allows your agent to list all requirements mapped to a project. This makes it easy to verify that every feature has been accounted for during the testing phase. **Can TestMonitor MCP show me my project milestones?** Yes. You can ask for a list of milestones for any project to see your current progress and upcoming deadlines in a simple list. **Does TestMonitor MCP work with Claude or Cursor?** Yes. It works with any MCP-compatible client including Claude, Cursor, and Windsurf. Once connected, your agent can query your QA data freely. **Can I see specific test case steps using TestMonitor MCP?** You can. If you provide a test case ID, the agent can pull the full description, including the specific steps and the expected results. **Is TestMonitor MCP good for large QA teams?** It's excellent for teams who need to stay organized. It helps leads get high-level summaries and triagers find specific bugs quickly across large projects. **Does this tool automate actual user interface tests on websites?** No. TestMonitor is essentially a Test Management Hub. You document your cases, requirements, runs, and defect reports structurally. The Connector reads this deep structural data allowing the AI to help correlate bugs to requirements and plan sprints—it does not inherently control a web-browser headless tester to run things. **Which ID should I pass to fetch Test Runs or Cases?** Almost all context actions downstream require a `project_id`. Start by telling your prompt: 'List all my TestMonitor projects'. Take the numeric ID corresponding to your target platform, then use it as the anchor for subsequent 'list test cases', 'list runs', or 'list issues' queries. **Where do I track the Personal Access Token setting?** It is tied to your individual profile. Log in via web, go to the top right avatar, pick 'My Account', open the 'API' sub-tab, and hit 'Create Token'. Copy it precisely because it is obscured upon closing.