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 AutoGen 10 tools — connect in under 2 minutes

Name: TestLink
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add TestLink as an MCP tool provider through the Vinkius and every agent in the group can access live data and take action.

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.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="testlink_agent",
            tools=tools,
            system_message=(
                "You help users with TestLink. "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use TestLink tools. Connect 10 tools through the Vinkius and assign role-based access — a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

Follow these steps to integrate the TestLink MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 10 tools from TestLink automatically

Why Use AutoGen with the TestLink MCP Server

AutoGen provides unique advantages when paired with TestLink through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use TestLink tools to solve complex tasks

Role-based architecture lets you assign TestLink tool access to specific agents — a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive TestLink tool calls

Code execution sandbox: AutoGen agents can write and run code that processes TestLink tool responses in an isolated environment

TestLink + AutoGen Use Cases

Practical scenarios where AutoGen combined with the TestLink MCP Server delivers measurable value.

Collaborative analysis: one agent queries TestLink while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from TestLink, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using TestLink data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process TestLink responses in a sandboxed execution environment

TestLink MCP Tools for AutoGen (10)

These 10 tools become available when you connect TestLink to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

Common issues when connecting TestLink to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

TestLink + AutoGen FAQ

Common questions about integrating TestLink MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call TestLink tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.