testmonitor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TESTMONITOR_URL | Yes | Required HTTPS instance URL, optionally ending in /api/v1 | |
| TESTMONITOR_TOKEN | Yes | Required Personal Access Token | |
| TESTMONITOR_TOOLS | No | Optional comma-separated exact tool names; unknown names fail startup | |
| TESTMONITOR_READ_ONLY | No | true exposes and permits only GET tools; defaults to false | false |
| TESTMONITOR_TIMEOUT_MS | No | Request timeout, default 30000, range 1-300000 | 30000 |
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 |
|---|---|
| post_applicationC | Create an application. Create a new application. |
| get_application_collectionC | Get all applications. Retrieve all applications. Apply sorting and pagination to organize the results. Include related data using the relations parameter. |
| get_applicationB | Get a specific application. Retrieve a specific application using its unique identifier. Use the relations parameter to include associated data in a single request. |
| put_applicationC | Update an application. Update an application using its unique identifier. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_applicationB | Delete an application. Delete an application using its unique identifier. Deleted applications are moved to the trash and can be restored later if needed. |
| restore_applicationB | Restore an application. Restore a previously deleted application from the trash using its unique identifier. |
| post_batch_delete_applicationsB | Delete multiple applications. Delete multiple applications in a single request. Deleted applications are moved to the trash and can be restored later if needed. |
| get_application_versionsC | Get all versions for an application. Retrieve all versions for an application using its unique identifier. |
| get_versions_collectionC | Get all versions. Retrieve all versions across all applications. Apply sorting and pagination to organize the results. Include related data using the relations parameter. |
| get_custom_field_collectionB | Get all custom fields. Retrieve all custom fields for a project. Use the model parameter to filter custom fields by resource type (i.e., requirements, risks, test cases, test runs, or issues). |
| post_issueC | Create an issue. Create a new issue within a project. |
| get_issue_collectionB | Get all issues. Retrieve all issues from a project. Apply custom filters, sorting, and pagination to find the issues you need. Include related data using the relations parameter. |
| get_issueB | Get a specific issue. Retrieve a specific issue using its unique identifier. Use the relations parameter to include associated data in a single request. |
| put_issueB | Update an issue. Update an issue using its unique identifier. You can modify the name, description, status, priority, category, resolution, and custom fields. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_issueB | Delete an issue. Delete an issue using its unique identifier. Deleted issues are moved to the trash and can be restored later if needed. |
| restore_issueB | Restore an issue. Restore a previously deleted issue from the trash using its unique identifier. The issue will be fully recovered with all its properties and associations intact. |
| post_batch_update_issuesB | Update multiple issues. Update multiple issues in a single request. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| post_batch_delete_issuesC | Delete multiple issues. Delete multiple issues in a single request. Deleted issues are moved to the trash and can be restored later if needed. |
| get_issue_attachmentsC | Get all attachments for an issue. Retrieve all attachments for an issue using its unique identifier. |
| post_issue_attachmentC | Upload an attachment for an issue. Upload an attachment for an issue using its unique identifier. |
| delete_issue_attachmentC | Delete an attachment from an issue. Delete an attachment from an issue using its unique identifier. |
| get_issue_tags_collectionB | Get all issue tags. Retrieve all tags that are currently used on issues within a project. Tags are labels that help categorize and organize issues, making it easier to filter and group related issues. |
| get_issue_tagsC | Get all tags for an issue. Retrieve all tags assigned to an issue using its unique identifier. |
| post_issue_taskC | Create a task for an issue. Create a task for an issue using its unique identifier. |
| get_issue_tasksC | Get all tasks for an issue. Retrieve all tasks for an issue using its unique identifier. |
| get_issue_taskC | Get a specific task. Retrieve a specific task using its unique identifier. |
| put_issue_taskC | Update a task. Update a task using its unique identifier. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_issue_taskC | Delete a task. Delete a task using its unique identifier. |
| post_issue_test_resultsC | Link test results to an issue. Link test results to an issue using its unique identifier. |
| get_issue_test_resultsC | Get all test results linked to an issue. Retrieve all test results linked to an issue using its unique identifier. |
| delete_issue_test_resultC | Unlink a test result from an issue. Unlink a test result from an issue using its unique identifier. |
| get_issue_commentsC | Get all comments for an issue. Retrieve all comments for an issue using its unique identifier. |
| post_issue_commentC | Post a comment on an issue. Post a comment on an issue using its unique identifier. |
| get_my_issue_collectionB | Get all assigned issues. Retrieve all issues assigned to the authenticated user. Apply custom filters, sorting, and pagination to find the issues you need. Include related data using the relations parameter. |
| get_my_issue_tasks_collectionC | Get all assigned tasks. Retrieve all tasks assigned to the authenticated user. Apply pagination to navigate through the results. |
| post_milestoneC | Create a milestone. Create a new milestone within a project. |
| get_milestone_collectionB | Get all milestones. Retrieve all milestones from a project. Apply custom filters, sorting, and pagination to find the milestones you need. Include related data using the relations parameter. |
| get_milestoneC | Get a specific milestone. Retrieve a specific milestone using its unique identifier. Use the relations parameter to include associated data in a single request. |
| put_milestoneB | Update a milestone. Update a milestone using its unique identifier. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_milestoneB | Delete a milestone. Delete a milestone using its unique identifier. Deleted milestones are moved to the trash and can be restored later if needed. |
| restore_milestoneB | Restore a milestone. Restore a previously deleted milestone from the trash using its unique identifier. The milestone will be fully recovered with all its properties and associations intact. |
| post_batch_delete_milestonesB | Delete multiple milestones. Delete multiple milestones in a single request. Deleted milestones are moved to the trash and can be restored later if needed. |
| post_projectD | Create a project. Create a new project. |
| get_project_collectionB | Get all projects. Retrieve all projects. Apply custom filters, sorting, and pagination to find the projects you need. Include related data using the relations parameter. |
| get_projectC | Get a specific project. Retrieve a specific project using its unique identifier. |
| put_projectB | Update a project. Update a project using its unique identifier. You can modify the name, description, and other project settings. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| archive_projectB | Archive a project. Archive a project using its unique identifier. Archived projects are read-only and no longer appear in the project overview. |
| unarchive_projectB | Unarchive a project. Unarchive a project using its unique identifier. The project will be restored to an active state and become visible in the project overview again. |
| get_project_members_collectionC | Get all project members. Retrieve all members of a project. Project members have access to the project's resources and can perform actions based on their roles. |
| get_requirement_types_collectionB | Get all requirement types. Retrieve all requirement types configured for a project. Requirement types classify requirements by their nature, such as functional or non-functional. |
| get_risk_classifications_collectionC | Get all risk classifications. Retrieve all risk classifications configured for a project. Risk classifications categorize risks by their type. |
| get_milestone_types_collectionB | Get all milestone types. Retrieve all milestone types configured for a project. Milestone types categorize milestones by their purpose, such as releases or sprints. |
| get_issue_categories_collectionB | Get project issue categories. Retrieve all issue categories configured for a project. Issue categories classify issues by their type, such as bug, feature, or test design. |
| get_issue_priorities_collectionB | Get project issue priorities. Retrieve all issue priorities configured for a project. Issue priorities indicate the urgency of an issue. |
| get_issue_resolutions_collectionB | Get project issue resolutions. Retrieve all issue resolutions configured for a project. Issue resolutions describe how an issue was resolved. |
| get_issue_statuses_collectionB | Get project issue statuses. Retrieve all issue statuses configured for a project. Issue statuses track the current state of an issue in your workflow. |
| get_test_result_states_collectionB | Get all test result statuses. Retrieve all test result statuses configured for a project. Test result statuses define the possible outcomes when executing a test case. |
| get_my_project_collectionB | Get all assigned projects. Retrieve all projects that the authenticated user is a member of. Apply custom filters, sorting, and pagination to find the projects you need. Include related data using the relations parameter. |
| get_symbols_collectionC | Get all symbols. Retrieve all available symbols. |
| post_requirementC | Create a requirement. Create a new requirement within a project. |
| get_requirement_collectionB | Get all requirements. Retrieve all requirements from a project. Apply custom filters, sorting, and pagination to find the requirements you need. Include related data using the relations parameter. |
| get_requirementB | Get a specific requirement. Retrieve a specific requirement using its unique identifier. This endpoint returns all details of the requirement, including its name, description, type, and custom fields. Use the relations parameter to include associated data in a single request. |
| put_requirementB | Update a requirement. Update a requirement using its unique identifier. You can modify any field including the name, description, type, and custom fields. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_requirementB | Delete a requirement. Delete a requirement using its unique identifier. Deleted requirements are moved to the trash and can be restored later if needed. |
| restore_requirementA | Restore a requirement. Restore a previously deleted requirement from the trash using its unique identifier. The requirement will be fully recovered with all its properties and associations intact. |
| post_batch_update_requirementsA | Update multiple requirements. Update multiple requirements at once in a single request. Specify the requirement identifiers and the fields you want to update, and all selected requirements will receive the same field values. This endpoint supports partial updates. |
| post_batch_delete_requirementsB | Delete multiple requirements. Delete multiple requirements at once in a single request. Specify the requirement identifiers you want to delete, and all selected requirements will be moved to the trash. Deleted requirements can be restored later if needed. |
| get_requirement_tags_collectionB | Get all requirement tags. Retrieve all tags that are currently used on requirements within a project. Tags are labels that help categorize and organize requirements, making it easier to filter and group related requirements. |
| get_requirement_tagsA | Get all tags for a requirement. Retrieve all tags assigned to a specific requirement using its unique identifier. |
| get_requirement_test_casesC | Get test cases assigned to a requirement. Retrieve all test cases assigned to a specific requirement using its unique identifier. |
| post_riskC | Create a risk. Create a new risk within a project. |
| get_risk_collectionB | Get all risks. Retrieve all risks from a project. Apply custom filters, sorting, and pagination to find the risks you need. Include related data using the relations parameter. |
| get_riskB | Get a specific risk. Retrieve a specific risk using its unique identifier. This endpoint returns all details of the risk, including its name, description, classification, and custom fields. Use the relations parameter to include associated data in a single request. |
| put_riskB | Update a risk. Update a risk using its unique identifier. You can modify any field including the name, description, classification, and custom fields. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_riskA | Delete a risk. Delete a risk using its unique identifier. Deleted risks are moved to the trash and can be restored later if needed. |
| restore_riskA | Restore a risk. Restore a previously deleted risk from the trash using its unique identifier. The risk will be fully recovered with all its properties and associations intact. |
| post_batch_update_risksB | Update multiple risks. Update multiple risks at once in a single request. Specify the risk identifiers and the fields you want to update, and all selected risks will receive the same field values. This endpoint supports partial updates. |
| post_batch_delete_risksA | Delete multiple risks. Delete multiple risks at once in a single request. Specify the risk identifiers you want to delete, and all selected risks will be moved to the trash. Deleted risks can be restored later if needed. |
| get_risk_tags_collectionB | Get all risk tags. Retrieve all tags that are currently used on risks within a project. Tags are labels that help categorize and organize risks, making it easier to filter and group related risks. |
| get_risk_tagsC | Get all tags for a risk. Retrieve all tags assigned to a specific risk using its unique identifier. |
| get_risk_test_casesC | Get test cases assigned to a risk. Retrieve all test cases assigned to a specific risk using its unique identifier. |
| post_teamD | Create a team. Create a new team. |
| get_team_collectionB | Get all teams. Retrieve all teams. Apply custom filters, sorting, and pagination to find the teams you need. Include related data using the relations parameter. |
| get_teamC | Get a specific team. Retrieve a specific team using its unique identifier. |
| put_teamB | Update a team. Update a team using its unique identifier. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_teamB | Delete a team. Delete a team using its unique identifier. Deleted teams are moved to the trash and can be restored later if needed. |
| restore_teamA | Restore a team. Restore a previously deleted team from the trash using its unique identifier. The team will be fully recovered with all its properties and members intact. |
| post_batch_delete_teamsA | Delete multiple teams. Delete multiple teams at once in a single request. Specify the team identifiers you want to delete, and all selected teams will be moved to the trash. Deleted teams can be restored later if needed. |
| get_team_membersB | Get all members of a team. Retrieve all members of a specific team using its unique identifier. |
| post_team_membersC | Add members to a team. Add one or more users as members to a team. |
| delete_team_memberC | Remove a member from a team. Remove a member from a team using the team and user identifiers. |
| post_test_caseC | Create a test case. Create a new test case within a project. |
| get_test_case_collectionA | Get all test cases. Retrieve all test cases from a project. Use the folder identifier to filter test cases by specific folders, or apply custom filters, sorting, and pagination to find the test cases you need. Include related data using the relations parameter. |
| get_test_caseA | Get a specific test case. Retrieve a specific test case using its unique identifier. This endpoint returns all details of the test case, including its steps, expected results, priority, and custom fields. Use the relations parameter to include associated data in a single request. |
| put_test_caseB | Update a test case. Update a test case using its unique identifier. You can modify any field including the name, description, steps, expected results, priority, and custom fields. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_test_caseB | Delete a test case. Delete a test case using its unique identifier. Deleted test cases are moved to the trash and can be restored later if needed. |
| restore_test_caseA | Restore a test case. Restore a previously deleted test case from the trash using its unique identifier. The test case will be fully recovered with all its properties, associations, and historical test results intact. |
| move_test_caseC | Move a test case to a folder. Move a test case to a different folder within the project using its unique identifier. This allows you to reorganize your test cases into a logical folder structure for better organization and navigation. |
| post_batch_update_test_casesB | Update multiple test cases. Update multiple test cases at once in a single request. Specify the test case identifiers and the fields you want to update, and all selected test cases will receive the same field values. This endpoint supports partial updates. |
| post_batch_delete_test_casesA | Delete multiple test cases. Delete multiple test cases at once in a single request. Specify the test case identifiers you want to delete, and all selected test cases will be moved to the trash. Deleted test cases can be restored later if needed. |
| get_test_case_tags_collectionB | Get all test case tags. Retrieve all tags that are currently used on test cases within a project. Tags are labels that help categorize and organize test cases, making it easier to filter and group related test cases. |
| get_test_case_commentsC | Get all comments for a test case. Retrieve all comments for a test case using its unique identifier. |
| post_test_case_commentC | Post a comment on a test case. Post a comment on a test case using its unique identifier. |
| get_test_case_attachmentsC | Get all attachments for a test case. Retrieve all attachments associated with a specific test case using its unique identifier. |
| post_test_case_attachmentC | Upload an attachment for a test case. Upload a new attachment to a test case. Attachments help document your test cases with supporting files such as screenshots, test data files, configuration examples, or reference documents. |
| delete_test_case_attachmentB | Delete an attachment from a test case. Delete a specific attachment from a test case using both the test case identifier and the attachment identifier. This permanently removes the file from the test case. |
| get_test_case_tagsC | Get all tags for a test case. Retrieve all tags assigned to a specific test case using its unique identifier. |
| get_test_case_requirementsC | Get all requirements for a test case. Retrieve all requirements assigned to a specific test case using its unique identifier. |
| get_test_case_risksB | Get all risks for a test case. Retrieve all risks assigned to a specific test case using its unique identifier. |
| get_test_case_applicationsB | Get all applications for a test case. Retrieve all applications assigned to a specific test case using its unique identifier. Applications represent different versions or variants of your software that need to be tested. |
| get_test_case_test_runsB | Get all test runs for a test case. Retrieve all test runs that include a specific test case using its unique identifier. |
| get_test_case_test_resultsC | Get all test results for a test case. Retrieve the complete execution history for a specific test case using its unique identifier. |
| get_test_case_issuesC | Get all issues for a test case. Retrieve all issues associated with a specific test case using its unique identifier. |
| post_test_environmentC | Create a environment. Create a new test environment. |
| get_test_environment_collectionC | Get all environments. Retrieve all test environments. Apply sorting and pagination to organize the results. |
| get_test_environmentC | Get a specific environment. Retrieve a specific test environment using its unique identifier. |
| put_test_environmentB | Update an environment. Update a test environment using its unique identifier. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_test_environmentB | Delete an environment. Delete a test environment using its unique identifier. This action is permanent and cannot be undone. |
| post_test_runC | Create a test run. Create a new test run within a project. |
| get_test_run_collectionB | Get all test runs. Retrieve all test runs from a project. Apply custom filters, sorting, and pagination to find the test runs you need. Include related data using the relations parameter. |
| get_test_runB | Get a specific test run. Retrieve a specific test run using its unique identifier. This endpoint returns all details of the test run, including its name, environment, state, and custom fields. Use the relations parameter to include associated data in a single request. |
| put_test_runB | Update a test run. Update a test run using its unique identifier. You can modify any field including the name, environment, assigned test cases or users, and custom fields. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_test_runB | Delete a test run. Delete a test run using its unique identifier. Deleted test runs are moved to the trash and can be restored later if needed. |
| restore_test_runA | Restore a test run. Restore a previously deleted test run from the trash using its unique identifier. The test run will be fully recovered with all its test cases, test results, and configuration intact. |
| open_test_runB | Open a test run. Open a previously closed test run using its unique identifier. Reopening a test run allows you to continue creating and updating test results. |
| close_test_runB | Close a test run. Close a test run using its unique identifier, marking it as completed. Closed test runs can be reopened if further testing is needed. |
| clone_test_runB | Clone a test run. Create a copy of an existing test run using its unique identifier. The cloned test run optionally includes the same test cases and user assignments, allowing you to quickly set up a new test run with similar configurations. |
| move_test_runB | Move a test run. Move a test run to a different milestone within the project using its unique identifier. Moving a test run preserves all its test cases, test results, and configuration. |
| post_batch_update_test_runsB | Update multiple test runs. Update multiple test runs at once in a single request. Specify the test run identifiers and the fields you want to update, and all selected test runs will receive the same field values. This endpoint supports partial updates. |
| post_batch_delete_test_runsA | Delete multiple test runs. Delete multiple test runs at once in a single request. Specify the test run identifiers you want to delete, and all selected test runs will be moved to the trash. Deleted test runs can be restored later if needed. |
| get_test_run_states_collectionA | Get all test run states. Retrieve all available test run states. Test run states represent the lifecycle stages a test run can be in, such as open, in progress or closed. |
| get_test_run_tags_collectionA | Get all test run tags. Retrieve all tags that are currently used on test runs within a project. Tags are labels that help categorize and organize test runs, making it easier to filter and group related test runs. |
| get_test_run_tagsC | Get all tags for a test run. Retrieve all tags assigned to a specific test run using its unique identifier. |
| get_test_run_test_casesB | Get all test cases for a test run. Retrieve all test cases assigned to a specific test run using its unique identifier. |
| get_test_run_usersC | Get all users for a test run. Retrieve all users assigned to a specific test run using its unique identifier. |
| get_test_run_test_resultsB | Get all test results for a test run. Retrieve all test results for a specific test run using its unique identifier. |
| get_my_test_run_collectionA | Get all assigned test runs. Retrieve all test runs assigned to the currently authenticated user. Apply custom filters, sorting, and pagination to find the test runs you need. Include related data using the relations parameter. |
| post_test_resultC | Create a test result. Create a new test result. |
| get_test_result_collectionB | Get all test results. Retrieve all test results from a project. Apply custom filters, sorting, and pagination to find the test results you need. Include related data using the relations parameter. |
| get_test_resultB | Get a specific test result. Retrieve a specific test result using its unique identifier. Use the relations parameter to include associated data in a single request. |
| put_test_resultC | Update a test result. Update a test result using its unique identifier. You can modify the status, notes, and other fields. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| mark_test_result_viewedC | Mark a test result as viewed. Mark a test result as viewed using its unique identifier. |
| mark_test_result_not_viewedC | Mark a test result as not viewed. Mark a test result as not viewed using its unique identifier. |
| get_test_result_commentsC | Get all comments for a test result. Retrieve all comments for a test result using its unique identifier. |
| post_test_result_commentC | Post a comment on a test result. Post a comment on a test result using its unique identifier. |
| get_test_result_attachmentsC | Get all attachments for a test result. Retrieve all attachments for a test result using its unique identifier. |
| post_test_result_attachmentC | Upload an attachment for a test result. Upload an attachment for a test result using its unique identifier. |
| delete_test_result_attachmentC | Delete an attachment from a test result. Delete an attachment from a test result using its unique identifier. |
| get_test_result_issuesB | Get all issues for a test result. Retrieve all issues linked to a test result using its unique identifier. |
| post_test_result_issuesC | Link issues to a test result. Link issues to a test result using its unique identifier. |
| get_test_suites_collectionC | Get all test suites.. Get all test suites (root folders). This endpoint is deprecated. We recommend updating your code. DEPRECATED. |
| get_test_suiteC | Get a specific test suite. Retrieve a test suite (folder) using its identifier. DEPRECATED. |
| post_folderC | Create a folder. Create a new folder within a project to organize test cases. Folders provide a hierarchical structure for managing large numbers of test cases, making them easier to navigate and maintain. |
| get_folders_collectionB | Get all folders. Retrieve all test case folders from a project. Use the parent identifier to filter folders by their parent folder, allowing you to navigate the folder hierarchy level by level. |
| get_folderB | Get a specific folder. Retrieve a specific test case folder using its unique identifier. This endpoint returns all details of the folder, including its name, description, and parent folder. |
| put_folderB | Update a folder. Update a test case folder using its unique identifier. You can modify the folder name, description, or parent folder relationship. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_folderA | Delete a folder. Delete a test case folder using its unique identifier. Deleted folders are moved to the trash and can be restored later if needed. When you delete a folder, all test cases and subfolders within that folder are also moved to the trash. |
| restore_folderB | Restore a folder. Restore a previously deleted test case folder from the trash using its unique identifier. The folder will be fully recovered with all its properties, test cases, and subfolders intact. |
| post_userC | Create a user. Create a new user account. |
| get_user_collectionA | Get all users. Retrieve all users. Apply custom filters, sorting, and pagination to find the users you need. Include related data using the relations parameter. |
| get_userC | Get a specific user. Retrieve a specific user using its unique identifier. |
| put_userB | Update a user. Update a user using its unique identifier. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_userA | Delete a user. Permanently delete a user using its unique identifier. This action cannot be undone. Consider archiving the user instead if you want to retain their data and history. |
| make_admin_userB | Grant user admin privileges. Grant a user admin privileges using its unique identifier. Admin users have full access to all settings and resources across the account. |
| remove_admin_userB | Revoke user admin privileges. Revoke a user's admin privileges using its unique identifier. The user will retain access to their assigned projects but will no longer have account-wide admin access. |
| archive_userB | Archive a user. Archive a user using its unique identifier. Archived users can no longer sign in or be assigned to projects and test runs, but their historical data is preserved. |
| my_accountA | Get authenticated user. Retrieve the user account details for the currently authenticated user. |
| post_webhookD | Create a webhook. Create a new webhook. |
| get_webhook_collectionC | Get all webhooks. Retrieve all webhooks. Apply pagination to find the webhooks you need. |
| get_webhookC | Get a specific webhook. Retrieve a specific webhook using its unique identifier. |
| put_webhookB | Update a webhook. Update a webhook using its unique identifier. You can modify the name, URL, and the events that trigger the webhook. This endpoint supports partial updates, so you only need to include the fields you want to change. |
| delete_webhookB | Delete a webhook. Delete a webhook using its unique identifier. This action is permanent and cannot be undone. |
| get_webhook_event_collectionA | Get all webhook events. Retrieve all available webhook events. Webhook events define the triggers that cause a webhook to send a notification, such as when a test case is created or a requirement is updated. |
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 173 tools
With 173 tools, many operations are near-identical across resource types (e.g., get_X_collection vs get_X, get_X_tags vs get_X_tags_collection), which can cause misselection without careful reading. Descriptions do distinguish them, but the sheer volume increases cognitive load and overlap risk.
The dominant pattern is action_resource (get_application, post_issue, put_test_case, delete_webhook, restore_milestone) with batch and association variants, which is highly predictable. Minor deviations like 'my_account' (noun only) and mixed action verbs (open/close, archive/unarchive, mark_viewed) slightly break uniformity.
173 tools is an extreme mismatch for a single MCP server, far exceeding practical bounds (typically 3-15) and likely to overwhelm an agent's selection process. The surface is excessively granular, with many near-duplicate operations across resources.
The server covers extensive CRUD lifecycles for core entities (applications, issues, projects, requirements, risks, teams, test cases, test runs, test results, users, webhooks, folders) including batch, restore, comments, attachments, and associations. Minor gaps exist for configuration entities like custom fields and test result states, which are read-only.