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

Name: TestLink
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

Cursor's Agent mode turns TestLink into an in-editor superpower. Ask Cursor to generate code using live data from TestLink and it fetches, processes, and writes — all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

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

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using TestLink

Open Agent mode in chat and ask: "Using TestLink, help me..." — 10 tools available

Why Use Cursor with the TestLink MCP Server

Cursor AI Code Editor provides unique advantages when paired with TestLink through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

TestLink + Cursor Use Cases

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

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

TestLink MCP Tools for Cursor (10)

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

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

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

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

TestLink + Cursor FAQ

Common questions about integrating TestLink MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design — tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.