Skip to content
Vinkius

TestLink Connector for AI agents.

10 live capabilities

Access your test plans and manual test cases through natural language.

Live agent request TestLink / Connector

Waiting for input…

AI Agent

Why people use TestLink

TestLink for faster QA test plan navigation

With this Connector, you just ask your agent to find the steps. It pulls the manual instructions, preconditions, and expected results directly into your chat. You get the data you need without the tab-switching.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get instant access to your QA test data through a natural language chat.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Defining a regression cycle

    A QA Lead asks the agent to list all plans for a project to see what needs to be included in the next release.

  2. Real-world use case 02

    Documenting a bug fix

    A developer asks for the manual steps of a specific test case to ensure they understand the expected behavior of a feature.

  3. Real-world use case 03

    Verifying build versions

    An engineer asks which builds are active for a specific plan to make sure they are testing the correct software version.

Complete set · 10capabilities

The complete TestLink capability set.

These are the exact actions your AI can choose when you ask it to work with TestLink.

Capability set01 / 03

01—04

4 capabilities in this set.

Part of 10 available through TestLink.

  1. 01 Capability

    Get test plan details

    Shows the specific details of a test plan. Use this to see what a plan covers at a glance.

  2. 02 Capability

    Get test project details

    Retrieves the core information for a TestLink project. It's the starting point for finding any other project data.

  3. 03 Capability

    Get test suite details

    Gets the specific data for a test suite. This is useful for understanding a specific branch of your test coverage.

  4. 04 Capability

    List test builds

    Shows all builds associated with a test plan. Use it to confirm which version of the software is being tested.

Capability set02 / 03

05—07

3 capabilities in this set.

Part of 10 available through TestLink.

  1. 05 Capability

    List test cases

    Lists every test case inside a suite. This is great for getting a high-level view of what's being tested.

  2. 06 Capability

    List test plans

    Shows all plans for a specific project. Use this to see the full roadmap of testing for a project.

  3. 07 Capability

    List test projects

    Lists every project on your TestLink server. It gives your agent a bird's eye view of your entire testing environment.

Capability set03 / 03

08—10

3 capabilities in this set.

Part of 10 available through TestLink.

  1. 08 Capability

    List test suites

    Shows all suites within a project. This helps you navigate the hierarchy of your test organization.

  2. 09 Capability

    Get user info

    Shows who is currently logged in. This helps you confirm your agent has the right permissions to see the data.

  3. 10 Capability

    Get test case details

    Pulls the full instructions and expected results for a specific test case. It helps you see exactly what to do without opening a browser.

Set up in minutes

One URL. Then ask TestLink to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use TestLink from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_Txd0bdinEzyETBUMcUstyIr6u481CAjFsmC77a1k/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it TestLink, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable TestLink for the conversation.

Where the request belongs

Work TestLink can move forward.

Built around the request

This is for QA engineers and developers who are tired of the tab-switching tax when trying to find test requirements in a legacy management capability.

01

QA Lead

Pulls entire test plans into a chat to define the scope of a new regression cycle quickly.

02

Test Engineer

Grabs step-by-step instructions from old test cases to include in their documentation or markdown files.

03

Software Developer

Checks the preconditions for a complex bug without having to ask a QA teammate for a screenshot or login.

Bring your own AI

Change the model, client or framework. Keep TestLink connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about TestLink.

The practical details behind the request, access and result.

Can the TestLink MCP access my self-hosted data?

Yes, it connects directly to your self-hosted TestLink instance using your Base URL and Developer API Key.

Can I use this to read manual test steps?

Yes, you can ask your agent to pull the full manual instructions and expected results for any specific test case.

Does this work with Cursor or Claude?

It works with any MCP-compatible client, including Claude, Cursor, and Windsurf.

How do I check which software build is assigned to a plan?

You can ask your agent to list the builds for a specific test plan, and it will return the target versions.

Can it help with regression planning?

It can list all test plans for a project, making it much faster to see what needs to be covered in a new cycle.

Is my data secure?

The Connector uses your own Developer API Key to authenticate, so your data stays within your environment.

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

One connection away

Give your agent a direct line to TestLink.

Connect TestLink once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available