Why should I plug an AI agent into an older legacy application like TestLink?

Because retrieving test assets from older GUIs can be painfully slow for developers. By mapping the database to an AI agent, your devs can just chat: 'What are the steps to reproduce Test Case 4022?' The agent calls the XML-RPC backend and instantly formats the manual steps logically in the chat space.

Can it read all my hierarchical QA Suites and specific cases?

Yes! The testlink agent is configured to retrieve Suites. You just list a Project ID, traverse downwards into Test Suites, and then request Test Cases by the retrieved Suite ID. It allows full architectural transparency over chat.

Does my TestLink server need to be accessible to the internet?

No. Because MCP servers process logic strictly locally through a sidecar setup, the interaction happens right on your machine/endpoint. As long as the machine running the AI client (e.g. Cursor, Claude Desktop) can resolve the Internal Network URL, the connection is solid.

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

Name: TestLink
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 TestLink and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "testlink": {
      "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 TestLink MCP Server

Connect your TestLink self-hosted environment to any AI agent and bring your classic test management structure seamlessly into your modern AI workflow via natural language.

GitHub Copilot Agent mode brings TestLink 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 & Plan Scoping — Retrieve all test projects, query their active states, and list all comprehensive test plans linked to them
Suite Navigation — Browse the hierarchical folder tree of Test Suites mapping your organizational test coverage
Test Cases Verification — Dive deep into individual test cases to read manual steps, expected results, priorities, and preconditions without navigating the legacy UI
Build Tracking — Inspect active software builds allocated within any specific test plan to confirm QA target versions
Environment Sanity — Check the agent’s connection and user mapping via the native whoami interrogation

The TestLink 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 TestLink to VS Code Copilot via MCP

Follow these steps to integrate the TestLink 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 TestLink

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

Why Use VS Code Copilot with the TestLink MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with TestLink 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

TestLink + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the TestLink 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

TestLink MCP Tools for VS Code Copilot (10)

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

get_test_case_details

Retrieves full details for a specific test case

get_test_plan_details

Retrieves details for a specific test plan

get_test_project_details

Retrieves details for a specific TestLink test project

get_test_suite_details

Retrieves details for a specific test suite

get_user_info

Retrieves information about the authenticated TestLink user

list_test_builds

Lists all builds available for a specific test plan

list_test_cases

Lists all test cases within a specific test suite

list_test_plans

Requires a project ID. Lists all test plans associated with a specific project

list_test_projects

Lists all test projects available on the TestLink server

list_test_suites

Lists all test suites within a specific test project

Example Prompts for TestLink in VS Code Copilot

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

"Find out if the server is working and tell me who I am authenticated as."

"Give me the step-by-step definition for Test Case ID 5440."

"List all active test plans for Project ID 2."

Troubleshooting TestLink MCP Server with VS Code Copilot

Common issues when connecting TestLink 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.

TestLink + VS Code Copilot FAQ

Common questions about integrating TestLink 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.