Use Vansah MCP with ChatGPT or Claude to find testing information, create and update test cases and plans, and record results through conversation.
Describe what you want to achieve and include the project or Jira work item. Your assistant chooses the appropriate capability. To get started, see Connecting to Vansah MCP.
Your account and projects
What you can do | How it helps |
Confirm your connection | See the connected Atlassian account, Vansah region and number of available workspaces. |
Find your projects | See the Jira projects with Vansah enabled that you can access. |
Review a project | Look up the details of a particular Vansah project. |
Check project options | View test case statuses, priorities, types, environments, releases, sprints and labels. |
Test cases and scripts
What you can do | How it helps |
Find test cases | Search a project by words, status, priority or test type. |
Review a test case | See its details, linked Jira work items and, when requested, its test script. |
Read a test script | View manual steps, written instructions or Given/When/Then scenarios, including a selected saved version. |
Review change history | See who changed a test case, what changed and when. |
View saved versions | List a test case’s versions and see which is the default. |
View linked Jira work items | See the Jira work items connected to a test case. |
Folders and test plans
What you can do | How it helps |
Browse project folders | Find test folders and see how testing is organised within the project. |
Find test plans | Browse standard and advanced plans by name, folder, status or dates. |
Review a test plan | See a plan’s details, requirements, iterations and results. |
Browse test plan folders | Find plan folders and see the plans and subfolders within them. |
View cases in a plan | See the test cases included in a particular plan. |
Find plans for a test case | See which test plans include a particular test case. |
Test runs and results
What you can do | How it helps |
Find test runs | Browse recorded runs in a project, or narrow the list by test case or result. |
Review a test run | See the details and recorded result of an individual run. |
Check available result options | See the standard and custom results available in your workspace, such as Passed or Failed. |
Review results for each step | See each test step’s recorded result and what actually happened during the run. |
View linked work items and defects | See the Jira work items and defects connected to a test run. |
Jira work items and boards
What you can do | How it helps |
Find Jira work items | Search the connected Jira site by project, words, work item type or status. |
Review a Jira board | See work items on a board, with optional work item type and status filters. |
View project components | Find the components used to organise work in a Jira project. |
Coverage and progress reports
What you can do | How it helps |
Review test coverage | Summarise coverage and results for selected Jira work items, test folders or test plans. |
Summarise test execution | Review results over a chosen date range, grouped by date, work item, assigned person, priority, component or label. |
Track testing progress over time | See how testing progresses across a selected period, with an option to exclude weekends. |
Create and update test cases
Use these actions to add or change testing information. Review the proposed content and the selected project before saving.
What you can do | How it helps |
Create a test folder | Add a folder to organise test cases, including a subfolder within an existing folder. |
Create a test case | Add a new case with its details and an optional manual, written or Given/When/Then script. |
Create several test cases | Add a group of test cases together, including their details and test scripts. |
Update a test case | Change its details or replace its complete test script, including an automation script. |
Replace written or scenario scripts | Replace a test case version’s written instructions or Given/When/Then scenarios. |
Add a manual test step | Add an action and its expected result to an existing test case version. |
Edit or reorder a manual step | Change an existing step’s action, expected result, test data or position. |
Create a new version | Copy the current or an earlier test case version into a new version. |
Link cases to a Jira work item | Connect one or more existing test cases to the work item they cover. |
Add cases to a folder or plan | Link existing test cases to a selected test folder or test plan. |
Add supporting files | Prepare images or other files to include in test scripts when creating or updating a test case. |
Create plans and record test results
Use these actions to plan testing or save results from testing you have completed. When recording results, specify the test cases, result and relevant folder, plan or Jira work item.
What you can do | How it helps |
Create a standard test plan | Plan testing for one Jira work item or test folder, with start and end dates. |
Create an advanced test plan | Bring testing for one or more Jira requirements or test folders together in a plan. |
Record results in a test folder | Save results for selected test cases in a test folder. |
Record results in a standard plan | Save results for selected test cases in a chosen test plan iteration. |
Record results in an advanced plan | Save results for selected test cases under a specific requirement in an advanced plan. |
Record results against a Jira work item | Save results for selected test cases against the work item being tested. |
Update an existing test run result | Change a recorded run’s overall result and, if needed, add what actually happened during testing. |
Example requests
Replace the details in brackets with your project, work item or test run.
Show me failed test runs in the [project name] project.
Review test coverage for [Jira work item key] and highlight any gaps.
Draft test cases for [Jira work item key] and show them to me for review before creating them in Vansah.
Update the result of test run [test run key] to [result] and record what actually happened.
Before saving changes
Reviewing existing information leaves your Vansah data unchanged. For a request that adds or changes data, check the selected project, test cases, folder or plan and review what will be saved.
Replacing a test script replaces its complete content. Updating a test run changes its overall result. Check the selected test case version or run before confirming.
If a request is interrupted, check what was saved before trying again, especially when creating cases, plans or test runs.
Access and security
Vansah MCP uses your authenticated Atlassian account and respects your existing Jira and Vansah permissions. Keep passwords and access tokens private.
For data residency and security information, see the MCP Overview and MCP Security best practices.
If you need help
Confirm that you are signed in with the correct Atlassian account.
Check that the Jira project is enabled for Vansah and that your account can access it.
Include the project name and the relevant test case, plan, run or Jira work item key in your request.
If your session has expired, reconnect using the connection guide.
