testit-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TESTIT_URL | Yes | The URL of the TestIT instance | |
| TESTIT_TOKEN | Yes | Your TestIT API token | |
| TESTIT_PROJECT_ID | No | Optional default project UUID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List projects, optionally filtered by name, archive or favorite flag. |
| get_projectB | Get a project by ID. |
| create_projectB | Create a new project (payload: CreateProjectApiModel, at least name). Cloud instances may answer 402 when the plan's project limit is reached. |
| update_projectA | Replace a project (PUT, full model with id); fields not sent are cleared. Prefer set_project. |
| delete_projectC | Delete a project by ID. |
| set_projectA | Partially update a project (JSON Patch): only name/description you pass change. |
| list_project_autotest_namespacesB | Autotest namespaces of a project with their classes (for filtering search_autotests). |
| search_projectsC | Search projects by filter. |
| list_work_itemsC | List work items (test cases, checklists, shared steps) of a project, with optional filters. |
| search_work_itemsB | Search work items across projects. Typed filter fields are combined with an optional raw "filter" object (TestIT WorkItemFilterApiModel) for advanced fields. |
| get_work_itemC | Get a work item by ID (UUID). |
| create_work_itemA | Create a test case, checklist or shared step. Defaults: entityTypeName=TestCases, state=NotReady, priority=Medium, duration=60000 ms (always 0 for SharedSteps — required by TestIT). Extra CreateWorkItemApiModel fields can be passed in "payload". |
| update_work_itemA | Replace a work item (PUT, full model with id). Fields not sent are cleared; prefer set_work_item. |
| delete_work_itemC | Delete a work item by ID (UUID). |
| get_work_item_historyC | Get work item history. |
| get_work_item_versionsC | Get all versions of a work item. |
| restore_work_itemA | Restore an archived (deleted) work item by ID. |
| purge_work_itemA | Permanently delete an archived work item. Irreversible; the item must be deleted (archived) first. |
| upload_work_item_attachmentC | Upload an attachment to a work item. |
| set_work_itemA | Partially update a work item: only the given fields change (JSON Patch), each call creates a new version. Prefer this over update_work_item (full replacement). Use move_work_item to change section. |
| move_work_itemB | Move a work item to another section (optionally before nextWorkItemId). |
| list_work_item_commentsC | List comments of a work item. |
| create_work_item_commentC | Add a comment to a work item. |
| update_work_item_commentC | Replace the text of a work item comment. |
| delete_work_item_commentC | Delete a work item comment. |
| list_work_item_autotestsC | Autotests linked to a work item. |
| unlink_work_item_autotestsA | Remove ALL autotest links of a work item; it becomes manual (isAutomated=false). To drop one link use unlink_autotest_work_item. |
| list_shared_step_referencesC | Where a shared step is used: work items whose steps reference it, and sections (target). |
| get_work_item_test_results_historyB | Test results of a work item across test runs/plans (newest first), with optional filters. |
| list_sectionsA | List all sections (folders) of a project as a flat list with parentId. The root section has parentId=null. Use section IDs as sectionId when creating work items. |
| get_sectionB | Get a section with its precondition/postcondition steps. |
| create_sectionB | Create a section. parentId defaults to the project's root section (TestIT rejects parentId=null). |
| rename_sectionC | Rename a section. |
| move_sectionA | Move a section (with its work items and subsections) under another parent. Optionally place it before nextSectionId. |
| delete_sectionA | Delete (archive) a section together with its subsections and work items. |
| list_test_runsC | List test runs for a project. |
| get_test_runC | Get a test run by ID. |
| create_test_runB | Create an empty test run in a project (state NotStarted). Extra CreateEmptyTestRunApiModel fields (attachments, links) can be passed in "payload". |
| start_test_runB | Start a test run. |
| stop_test_runC | Stop a test run. |
| search_test_runsB | Search test runs (across projects if no project given). Typed fields are merged over an optional raw "filter" (TestRunFilterApiModel). projectIds defaults to the current project. |
| set_test_runB | Partially update a test run (JSON Patch): only name, description, tags you pass change. |
| create_test_run_from_autotestsA | Create a test run (not bound to a test plan) pre-filled with one result per autotest x configuration. Fill results via submit_test_run_results by autoTestExternalId. |
| create_test_run_from_test_pointsB | Create a test run inside a test plan from explicit selectors: for each configuration, the work items whose test points to include. Like create_test_run_from_work_items, only AUTOMATED test points are accepted. |
| rerun_test_run_resultsA | Re-run autotest results of a run: each selected result gets a new pending attempt and the run goes back to InProgress. Submit new results via submit_test_run_results; attempts are listed by get_test_result_reruns. |
| create_test_run_from_work_itemsA | Create a test run inside a test plan for the given work items x configurations (the plan becomes InProgress). Only AUTOMATED work items are accepted (linked to an autotest, see link_autotest_work_item); TestIT rejects manual ones. Results are pre-created and filled via submit_test_run_results; the run completes when all results are in. |
| complete_test_runA | Complete a test run (InProgress/Stopped -> Completed). |
| delete_test_runA | Delete (archive) a test run by ID. Use restore_test_run to undo or purge_test_run to remove permanently. |
| restore_test_runA | Restore an archived (deleted) test run. |
| purge_test_runA | Permanently delete an archived test run. Irreversible; delete (archive) it first. |
| get_test_run_resultsC | Get test results for a test run. |
| get_test_resultC | Get a test result by ID. |
| search_test_resultsB | Search test results. Typed fields are merged with an optional raw "query" (TestResultsFilterApiModel) for advanced fields. |
| set_test_resultA | Change selected fields of a test result (JSON Patch) without touching the others. To change the result status use statusCode (patching outcome is ignored by TestIT). Raw RFC 6902 operations can be added via "operations". |
| update_test_resultA | Replace a test result (PUT). WARNING: this is a full replacement — fields not sent (comment, message, links, step results...) are cleared. Prefer set_test_result for partial changes. |
| submit_test_run_resultsA | Send autotest results into a test run (POST /testRuns/{id}/testResults). Each result needs an existing autotest externalId and a configurationId. Returns created test result IDs. |
| get_test_result_rerunsA | All attempts of a test result (original + reruns) with runNumber, outcome and status. The original result keeps its status; later attempts are separate results. |
| get_test_results_statisticsB | Counts of test results by status (passed/failed/skipped/blocked/...) and failure category for a filter, e.g. one or more test runs. |
| list_test_result_attachmentsA | List attachments of a test result (id, name, type, size). |
| upload_test_result_attachmentB | Attach a file (screenshot, log) to a test result. Returns the new attachment id. |
| get_test_result_attachmentA | Download a test result attachment; content is returned base64-encoded. |
| delete_test_result_attachmentC | Delete an attachment from a test result. |
| list_test_plansB | List test plans for a project. |
| get_test_planC | Get a test plan by ID. |
| create_test_planB | Create a test plan (status New). Extra CreateTestPlanApiModel fields can be passed in "payload". |
| update_test_planA | Replace a test plan (PUT). Requires id, name, projectId in payload; fields not sent are cleared. |
| set_test_plan_stateA | Change test plan status: start (-> InProgress), pause (-> Paused), complete (-> Completed). |
| create_test_plan_cloneA | Clone a test plan (copy named " (1)", status New). Returns the new plan. |
| list_test_plan_test_runsB | List test runs of a test plan, optionally filtered by state. |
| delete_test_planA | Delete (archive) a test plan. Use restore_test_plan to undo or purge_test_plan to remove it for good. |
| restore_test_planA | Restore an archived (deleted) test plan. |
| purge_test_planA | Permanently delete an archived test plan. Irreversible; delete (archive) it first. |
| assign_test_points_testerA | Assign a tester (user UUID) to the given test points of a test plan. TestIT has no user list API: take user ids from existing entities (createdById, testerId). Returns the affected point ids. |
| unassign_test_points_testerB | Remove the tester from the given test points of a test plan. Returns the affected point ids. |
| reset_test_pointsA | Reset the given test points of a test plan back to NoResults (their results are discarded). |
| get_test_plan_summaryB | Test plan totals: test points (total/manual/automated/completed), defects, planned and spent duration. |
| list_test_plan_configurationsC | Configurations used by the test points of a test plan. |
| get_test_plan_historyC | Change history of a test plan. |
| list_test_plan_test_suitesA | Get the test suite tree of a test plan (suites with nested children). |
| get_test_suiteC | Get a test suite by ID. |
| create_test_suiteA | Create a test suite in a test plan (top-level, or nested under parentId). Then fill it with set_test_suite_work_items. |
| set_test_suite_work_itemsA | Set the work items of a test suite. REPLACES the current list; test points are created for each work item x suite configuration (the default configuration if none set). |
| set_test_suite_configurationsB | Set the configurations of a test suite (replaces the current list). |
| list_test_suite_test_pointsA | List test points of a test suite (work item x configuration, with status and tester). |
| search_test_pointsB | Search test points across test plans/suites. Typed fields are merged with an optional raw "filter" (TestPointFilterRequestModel). |
| delete_test_suiteA | Delete a test suite with its nested suites and test points. |
| set_test_suiteA | Rename a test suite (JSON Patch on name). |
| list_test_suite_test_resultsC | Test results of all test points in a test suite (latest attempts, with autotest and configuration). |
| list_test_suite_configurationsC | Configurations of a test suite. |
| get_test_point_work_itemC | The work item (test case) a test point represents. |
| list_test_point_test_runsC | Test runs that include a test point. |
| search_autotestsB | Search autotests. Typed fields are merged over an optional raw "filter" (AutoTestFilterApiModel). projectIds defaults to the current project. |
| get_autotestC | Get an autotest by UUID. |
| create_autotestA | Create an autotest. Linking it to test cases (workItemIds) makes those cases automated, which is required to create test runs from a test plan. Results are later sent by externalId (submit_test_run_results). Extra AutoTestCreateApiModel fields can go into "payload". |
| delete_autotestA | Delete (archive) an autotest. Archived autotests return 404 from get_autotest and can only be found via search_autotests with isDeleted=true; the API has no restore or purge for autotests. |
| list_autotest_work_itemsC | List work items (test cases) linked to an autotest. |
| link_autotest_work_itemA | Link an autotest to a work item; the work item becomes automated. |
| unlink_autotest_work_itemB | Remove the link between an autotest and a work item. |
| set_autotestA | Partially update an autotest (JSON Patch): only name, title, description, namespace, classname you pass change. externalId is the result-matching key and is not editable here. |
| get_autotest_results_historyB | Results of an autotest across test runs (status, outcome, run, plan, configuration, duration), newest first. |
| list_autotest_test_runsC | Test runs that contain the autotest. |
| get_autotest_average_durationB | Average duration (ms) of passed and failed results of an autotest. |
| set_autotests_flakyA | Mark (value=true) or unmark (value=false) autotests as flaky by id. |
| get_project_analyticsB | Get analytics for all test plans in a project. |
| get_test_plan_analyticsC | Get analytics for a specific test plan. |
| get_test_run_statisticsB | Get test result statistics for a specific test run, optionally filtered. |
| list_shared_stepsC | List shared steps of a project, with optional filters. |
| get_shared_stepC | Get a shared step by ID. |
| list_configurationsB | List configurations for a project. Every project has a default one ("Any"); test points and results are always bound to a configuration. |
| search_configurationsB | Search configurations by name substring across projects (default: current project). |
| get_configurationB | Get a configuration by ID. |
| create_configurationC | Create a configuration (environment such as browser/OS). Extra ConfigurationPostModel fields can go into "payload". |
| set_configurationA | Partially update a configuration: only the given fields change (JSON Patch). Prefer this over update_configuration. |
| update_configurationA | Replace a configuration (PUT, ConfigurationPutModel with id). Fields not sent are cleared; use set_configuration for partial changes. |
| delete_configurationA | Delete (archive) a configuration. Use restore_configuration to undo or purge_configuration to remove it for good. |
| restore_configurationB | Restore an archived configuration. |
| purge_configurationA | Permanently delete an archived configuration. Irreversible; delete (archive) it first. |
| search_configuration_parametersB | List configuration parameters (e.g. browser, os) with their values and projects. Defaults to the current project; name filters by substring. |
| get_configuration_parameterB | Get a configuration parameter with its values and projects. |
| create_configuration_parameterC | Create a configuration parameter with allowed values. |
| update_configuration_parameterA | Replace a configuration parameter (PUT): name, the FULL list of values and projects. Values not sent are removed. |
| delete_configuration_parameterC | Delete a configuration parameter. |
| upload_attachmentA | Upload a file to TestIT and get its attachment id/metadata. Pass the id in attachmentIds of create_work_item to attach it. |
| get_attachmentB | Download an attachment; content is returned base64-encoded. |
| get_attachment_metadataC | Attachment metadata: name, type, size, author, dates. |
| delete_attachmentA | Delete an attachment that is not linked to any entity (TestIT returns 422 for linked ones). |
| list_test_statusesA | List test result statuses (system and custom): code, name, type. Use "code" as statusCode in submit_test_run_results / set_test_result (codes are case-insensitive, e.g. PASSED, FAILED, BLOCKED). |
| list_tagsA | List tags. With projectId/projectName: tags used by that project's work items (plain names). Without: all tags in the instance (search with searchValue). |
| list_test_plan_tagsC | Tags used by test plans (instance-wide). |
| list_project_attributesB | List custom attributes of a project (id, name, type, isRequired, options). Use attribute ids as keys of "attributes" when creating work items or test plans. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 130 tools
Most tools target a distinct resource and action, and descriptions explicitly disambiguate close pairs such as list vs search, set vs update, and the multiple create_test_run_from_* variants. However, the 130-tool surface includes several near-duplicate patterns and lifecycle variants that can still cause misselection under load.
Names consistently use snake_case verb_noun phrasing (list_, get_, create_, set_, delete_, restore_, purge_) across all resources. Minor variants like create_test_plan_clone and rerun_test_run_results remain readable and follow the same convention.
130 tools far exceeds the 3-15 range appropriate for an MCP server and the 25+ threshold for 'too many'; even for a broad test-management API, this volume creates significant selection and context burden.
The surface covers CRUD and lifecycle operations for projects, work items, sections, test plans, suites, runs, results, autotests, configurations, attachments, comments, shared steps, tags, and analytics. Stated API limitations (e.g. no user list, no autotest restore/purge) are documented rather than hidden gaps.