4,000+ servers built on MCP Fusion
Vinkius
VS Code CopilotIDE
Why use TestMonitor MCP Server with VS Code Copilot?

Bring Qa Testing
to VS Code Copilot

Create your Vinkius account to connect TestMonitor to VS Code Copilot and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Get Project DetailsGet Test Case DetailsGet Test Run DetailsList Account UsersList IssuesList MilestonesList ProjectsList RequirementsList Test CasesList Test Runs
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
TestMonitor

What is the TestMonitor MCP Server?

Link up your TestMonitor cloud infrastructure with any AI agent to streamline QA tracking operations and retrieve real-time milestone data without having to navigate web dashboards.

What you can do

  • Project Triage — List all ongoing projects alongside their high-level metadata such as test coverage and delivery status
  • Runs & Milestones Tracking — Instantly retrieve project-scoped test runs, milestones lists, and deadline progress
  • Defect Auditing — Query all generated issues or software defects explicitly linked to a specific test project
  • Requirement Tracing — Ask the agent to map requirements against existing feature specifications without manually matching them in the UI
  • Team Management Lookup — Easily list out all the users provisioned in the workspace to confirm roles or debugging ownership

How it works

  1. Subscribe to this server
  2. Provide your Subdomain and your Personal Access Token
  3. Coordinate your entire QA suite from Claude, Cursor, or any compatible AI IDE

Who is this for?

  • Quality Directors — request a quick summary of the current Test Runs and their respective Milestones before daily stand-ups
  • Bug Triagers — leverage the AI to list reported defects and quickly assign the contextual backlog data to new tickets
  • Product Owners — read the explicit specifications of any Requirement and cross-reference against active test cases without breaking focus

Built-in capabilities (10)

get_project_details

Retrieves details for a specific TestMonitor project

get_test_case_details

Retrieves full details for a specific TestMonitor test case

get_test_run_details

Retrieves details for a specific TestMonitor test run

list_account_users

Lists all users associated with the TestMonitor account

list_issues

Lists all issues (defects) within a project

list_milestones

Lists all milestones within a project

list_projects

Project IDs are required for most other tools. Lists all projects available on the TestMonitor instance

list_requirements

Lists all requirements for a project

list_test_cases

Lists all test cases within a specific TestMonitor project

list_test_runs

Lists all test runs within a specific project

Why VS Code Copilot?

GitHub Copilot Agent mode brings TestMonitor data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

TestMonitor in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run TestMonitor with Vinkius?

The TestMonitor connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

View full TestMonitor details →
TestMonitor
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect TestMonitor using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

TestMonitor and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect TestMonitor to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures TestMonitor for VS Code Copilot

Every request between VS Code Copilot and TestMonitor is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →