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

Name: TestLink
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to TestLink through the Vinkius — pass the Edge URL in the `mcps` parameter and every TestLink tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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

from crewai import Agent, Task, Crew

agent = Agent(
    role="TestLink Specialist",
    goal="Help users interact with TestLink effectively",
    backstory=(
        "You are an expert at leveraging TestLink tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in TestLink "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, TestLink becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TestLink tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

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

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

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from TestLink

Why Use CrewAI with the TestLink MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with TestLink through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

TestLink + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries TestLink for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries TestLink, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain TestLink tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries TestLink against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

TestLink MCP Tools for CrewAI (10)

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

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

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

TestLink + CrewAI FAQ

Common questions about integrating TestLink MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.