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.

TestMonitor MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: TestMonitor
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install TestMonitor and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "testmonitor": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About 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.

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.

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

The TestMonitor MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect TestMonitor to VS Code Copilot via MCP

Follow these steps to integrate the TestMonitor MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using TestMonitor

Ask Copilot: "Using TestMonitor, help me...". 10 tools available

Why Use VS Code Copilot with the TestMonitor MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with TestMonitor through the Model Context Protocol.

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

TestMonitor + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the TestMonitor MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

TestMonitor MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect TestMonitor to VS Code Copilot via MCP:

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

Example Prompts for TestMonitor in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with TestMonitor immediately.

"List all TestMonitor projects."

"Get me the details for Test Case ID 5521 from project 8840."

"List all issues for Project 8840."

Troubleshooting TestMonitor MCP Server with VS Code Copilot

Common issues when connecting TestMonitor to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

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

TestMonitor + VS Code Copilot FAQ

Common questions about integrating TestMonitor MCP Server with VS Code Copilot.

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.

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.

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.

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.