TestMonitor MCP. Audit QA projects, issues, and requirements from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
TestMonitor MCP Server reads your entire QA project history directly into your chat window. It lists projects, fetches test runs and milestones, audits defects via `list_issues`, or maps requirements against features—all without you leaving your AI client.
Get the full picture of your codebase's quality status instantly.
What your AI agents can do
Get project details
Fetches specific metadata for one TestMonitor project ID.
Get test case details
Retrieves the full setup and expected steps for a single test case.
Get test run details
Gets detailed results, passed/failed counts, and status for one specific test run instance.
The server retrieves a list of every project ID available on your TestMonitor instance.
It fetches full metadata, including status and scope, for any given project ID.
The tool pulls a list of issues (defects) from a specified project ID.
You can retrieve lists of all available milestones, or details for any specific test execution run.
The server pulls a comprehensive list of business requirements tied to the project scope.
It lists every user account provisioned in your TestMonitor workspace for role verification.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
TestMonitor MCP Server: 10 Tools for Project & QA Management
These tools allow you to query every major component of your TestMonitor setup—from listing projects to fetching deep test run results.
019d7612get project details
Fetches specific metadata for one TestMonitor project ID.
019d7612get test case details
Retrieves the full setup and expected steps for a single test case.
019d7612get test run details
Gets detailed results, passed/failed counts, and status for one specific test run instance.
019d7612list account users
Lists all user accounts tied to the TestMonitor workspace.
019d7612list issues
Pulls a list of defects and reported issues from a specified project scope.
019d7612list milestones
Retrieves all defined milestones for the current project.
019d7612list projects
Lists every available project ID on your TestMonitor instance.
019d7612list requirements
Pulls a list of all business requirements defined for the target project.
019d7612list test cases
Lists every test case available within a specific TestMonitor project.
019d7612list test runs
Retrieves a list of all completed and pending test runs for the target project.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with TestMonitor, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You're tired of clicking through a dozen dashboards just to figure out if your code actually works. The TestMonitor MCP Server connects your entire QA project history directly into your chat window. You don't have to navigate web UIs; you just ask your AI client, and it handles the digging for you.
It pulls everything—project status, test results, reported bugs, requirements mapping—all from one place.
When you connect this server, you get instant access to every piece of data defining your product's quality. You can look at what's done, what's broken, and who signed off on it, all without leaving your chat interface. It’s the full picture of your codebase's health, right now.
Project Scope & Metadata
To start, you use list_projects to pull a list of every project ID sitting on your TestMonitor instance. Need more info? Use get_project_details with a specific ID to grab full metadata, including the current status and overall scope for that particular effort. You can also run list_requirements, which pulls a comprehensive list of all business requirements tied to the target project's scope so you know exactly what the product's supposed to do.
Testing & Execution Auditing
When it comes to testing, this server gives you deep visibility. You can run list_test_runs to get a list of all test cycles—both completed and pending—for the project. If you want details on one specific attempt, use get_test_run_details. That tells you exactly how many tests passed versus failed, and what the overall status was for that particular run instance.
If you need to check out the individual components of your test suite, first call list_test_cases to get a list of every available test case in scope. Then, use get_test_case_details to retrieve the full setup and expected steps for any single test case. You can also track project progress by calling list_milestones, which pulls all defined milestones, helping you see if the team hit its targets.
Defect Tracking & Team Audit
When things go wrong, this server makes it easy to find out why. Use list_issues to pull a definitive list of defects and reported issues from any specified project scope. You'll get details on what broke and where the fix needs to happen.
To confirm who owns what or who signed off on changes, you can call list_account_users. This tool pulls every user account provisioned in your TestMonitor workspace so you've got your role verification ready. Together, these tools let you look at project scope, list requirements, check all the runs and milestones, find every bug reported via list_issues, or get the setup details for a single test case—you can map it out completely from your chat window.
How TestMonitor MCP Works
- 1 First, subscribe to the server and provide your Subdomain and Personal Access Token.
- 2 Next, tell your AI client exactly what you need—for example: 'What are the issues for project 8840?'
- 3 The agent calls the right tool (e.g.,
list_issues), processes the data, and returns a clean summary directly to your chat.
The bottom line is you use natural conversation to run complex QA queries that used to require logging into multiple web dashboards.
Who Is TestMonitor MCP For?
This is for Quality Directors who hate manual status reports. It's also for Bug Triagers stuck in endless Jira tickets and Product Owners needing to cross-reference requirements against active test cases before a release. If you spend more than five minutes clicking between dashboards, you need this.
Needs quick summaries of current Test Runs and their related Milestones right before stand-ups, without logging into the full dashboard.
Uses the AI to list reported defects (list_issues) and immediately pull contextual backlog data for new tickets.
Cross-references explicit requirements against active test cases using list_requirements without losing focus in the UI.
What Changes When You Connect
- Immediate Defect Visibility: Instead of navigating to the Issues tab, just ask for defects.
list_issuespulls all reported bugs for a project instantly, letting you see if an issue is 'Open' or 'In Progress'. - Full Requirement Mapping: Stop manually checking boxes. Use
list_requirementsand map them against active test cases—it tells you which feature specs are fully covered by tests. - Test Run Deep Dive: You get more than just a pass/fail count.
get_test_run_detailsshows the full history and specific results for any single execution run, making debugging faster. - Scope Management: Need to know what's running?
list_projectsgives you an inventory of every project ID available in your environment right away. - Team Accountability: Quickly confirm who owns a feature or bug. The
list_account_userstool shows all provisioned users, eliminating guesswork about team roles.
Real-World Use Cases
The Pre-Standup Status Check
A QA Director needs to report on the status of three projects before a standup. Instead of opening three dashboards, they prompt: 'Give me milestones and test runs for Project A, B, and C.' The agent uses list_milestones and list_test_runs multiple times and compiles a single, actionable summary in the chat.
Triage a Critical Bug
A bug triager finds an issue ID. They ask the agent to pull all details for that defect using list_issues, then cross-reference it with requirements using list_requirements to ensure the bug isn't related to old, unrecorded features.
Onboarding a New Team Member
A new engineer needs to understand the project scope. They ask: 'What are all the active projects and who works on them?' The agent uses list_projects and then runs list_account_users to build an immediate, comprehensive resource document.
Validating Feature Scope
A Product Owner wants to confirm that a new feature (REQ-10) has adequate testing coverage. They ask the agent to list requirements using list_requirements and then check linked test cases via list_test_cases, verifying nothing was missed.
The Tradeoffs
Asking for a full report in one go
Prompting: 'Give me everything about Project 8840—all bugs, all requirements, and the test run status.' The agent gets overwhelmed or only returns partial data because the request is too broad.
→
Break it down. First, ask for the scope: 'List projects for this quarter' (list_projects). Then, drill down: 'What issues are attached to 8840?' (uses list_issues), and finally: 'Show me milestones for 8840' (uses list_milestones). Keep your queries specific.
Forgetting the Project ID
Trying to list issues or test cases without first identifying which project they belong to. The agent fails because most tools require a parent ID.
→
Always start with list_projects to get the target IDs. Use that ID in all subsequent calls, like when calling list_issues.
Assuming Test Cases are always current
Relying on list_test_cases without checking if a specific run (get_test_run_details) actually used the latest version of that test case. You might get stale data.
→
After viewing test cases, immediately follow up with 'What was the result for Test Case ID 5521 on Project 8840?' (using get_test_run_details). This validates execution against the definition.
When It Fits, When It Doesn't
Use this server if your primary bottleneck is accessing structured QA data—you need a chat interface to run complex, multi-step queries involving defects, requirements, and test runs. If you just need raw JSON dumps or bulk exports of an entire dataset (e.g., every single column from the underlying database), this isn't enough. You'll need a dedicated API endpoint that allows SQL query parameters. This tool is for intelligence gathering; it organizes and presents data in plain English, not for ETL pipelines. If you only need to know who works on what, list_account_users handles that cleanly.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by TestMonitor. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Status reports shouldn't take half a day of clicking between tabs.
Right now, checking project status is tedious. You open the main dashboard, then click on 'Issues', copy over 20 bug IDs. Then you switch to 'Milestones' just to check the due date. If you need to cross-reference a bug ID against a requirement ID, you have to leave the issue tracker entirely and jump into another system. It’s pure context switching hell.
With this MCP server, that whole process shrinks to a few lines of chat. You simply ask: 'What are all the open issues for Project 8840, and what requirements does the most critical bug relate to?' The agent runs `list_issues`, pulls the data, uses `get_project_details` for context, and gives you the answer in one clean response.
TestMonitor MCP Server: Get project status instantly.
Manual steps that disappear include opening the 'Requirements' view to check coverage, then having to open the 'Test Cases' list to see which ones are actually mapped. You also stop manually calculating if a test run is complete by checking `list_test_runs` and comparing it to `list_milestones` dates.
It’s simple: you ask for the synthesis of data, and the server provides it. It moves QA tracking from being an act of dashboard navigation to one of conversation.
Common Questions About TestMonitor MCP
How do I list all projects using TestMonitor MCP Server? +
You call list_projects. This tool returns a complete inventory of every project ID on the instance, which you then need to feed into other tools like list_issues.
What is the difference between `get_test_cases_details` and `get_project_details`? +
get_test_case_details gives you a step-by-step breakdown of one specific test. get_project_details provides high-level metadata about the entire project, like its overall status or coverage score.
Can I check for defects using `list_issues`? +
Yes, that's exactly what it does. You provide a Project ID, and list_issues returns all currently reported defects attached to that project scope.
How do I find out who is assigned to the account? +
Use the list_account_users tool. This fetches a simple list of every user provisioned in your workspace, which helps you confirm ownership or roles.
What does calling `list_milestones` show about a project's timeline? +
It retrieves all defined milestones for a given project. This lets you track the scheduled progress and due dates, giving you a clear view of overall delivery status.
How do I use `list_requirements` to map feature specifications? +
You provide the Project ID to pull all core requirements for that project. This allows your agent to cross-reference specific features against existing test cases or reported issues.
What details does `get_test_run_details` return for a specific run? +
This tool gives you a complete report card for one test execution. You get granular data on which steps passed, failed, and the overall metrics of that particular test cycle.
If I use `list_test_runs`, what information can I gather about history? +
You must specify a Project ID to index all historical runs. This tool gathers records for every completed or in-progress test run, letting you track performance over time.
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 MCP server 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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Percentage Calculation Engine
Stop LLMs from miscalculating discounts and interest. Deterministically calculate exact percentages and relative increases.
NVIDIA Audio
Transcribe speech, generate voices, translate audio, and clone voices via NVIDIA Audio APIs.
Duo Security (Two-Factor Authentication API)
Manage Duo Security users, trigger 2FA authentication, and handle account administration directly from any AI agent.
You might also like
CartonCloud
Manage warehouse and transport operations via CartonCloud — track orders, monitor stock, and manage consignments directly from any AI agent.
Hyperbrowser (Web Infra for AI)
Cloud browsers for AI agents via Hyperbrowser — manage sessions, scrape pages, and extract structured data.
Tactile CRM
Connect your AI to Tactile CRM. Query companies, read contact details, and evaluate your sales opportunities and pipelines natively from the terminal.