TestLink MCP. Query the entire test management structure via chat.

Listen up, pal. You gotta connect your self-hosted TestLink setup to any AI agent and ditch that clunky old UI. This server exposes every core function of TestLink as actionable tools for your agent. It maps all that complex test data—from the biggest projects down to tiny individual steps—right into natural chat conversation.

Your AI client handles all the heavy lifting, letting you pull specific steps, check preconditions, or list active builds without ever touching a legacy dashboard.

Project Discovery and Scope Management
You'll start by seeing what big picture stuff is going on. You can run list_test_projects to get a directory listing of every major test project sitting on the server. When you know which project you wanna dig into, use get_test_project_details to grab all the general info for that specific TestLink project ID.

Navigating the Hierarchy
To walk through your entire suite structure, first check out the projects with list_test_projects, then jump in and run list_test_suites to get a list of every defined test suite tied to a project. If you need more depth on those suites, call get_test_suite_details for details about a specific suite, including its parent scope.

From there, you can map out the whole folder and category tree by calling list_test_cases, which outputs every individual test case found within that designated test suite. For the nitty-gritty on any single item, you'll use get_test_case_details to pull all manual steps, expected results, metadata, and preconditions for a specific test case ID.

Testing Plans and Builds
If your goal is tracking what needs testing, start by listing the plans themselves. Run list_test_plans to get every defined test plan belonging to a project. Grab all the associated data using get_test_plan_details for a chosen instance. When you need to know which versions of the app are tied to that plan, execute list_test_builds.

This function confirms exactly which software builds are linked to a specific test plan ID.

Checking Context and Permissions
Before you start pulling data, you gotta make sure your agent has clearance. Use get_user_info to check the API token's authenticated status and see what user identity it’s running under within TestLink.

This toolset lets you query the full lifecycle of a software test, allowing your agent to verify your authentication context via get_user_info, retrieve general project info using get_test_project_details, list all available projects with list_test_projects, and drill down through the structure. You can then use list_test_suites or get_test_suite_details to map out the full category tree, listing every case via list_test_cases.

To get the deep details on a plan, run list_test_plans followed by get_test_plan_details, and confirm linked software versions with list_test_builds. Finally, when you're down to the actual procedure, call get_test_case_details for all the steps, expected results, and metadata on that single test case. You'll get every piece of data without having to look at a messy web interface.