Vansah MCP connects an AI assistant to your Vansah testing information in Jira. Ask questions and carry out supported testing tasks using everyday language, with access controlled by your existing Jira and Vansah permissions.
What is Vansah MCP?
MCP stands for Model Context Protocol. It gives an AI assistant a standard way to use tools from another application. Vansah provides a hosted MCP server that connects a compatible assistant to your Vansah workspace.
You can connect through the Vansah listings for ChatGPT or Claude, or use another client that supports Vansah’s remote MCP connection and sign-in process.
What can your assistant help with?
Task | Examples |
Find testing information | Search test cases, folders, plans and test runs, and review scripts, versions and history. |
Create or improve test cases | Create cases, update their details or scripts, add steps and create new versions. |
Connect tests to requirements | Find Jira work items and link test cases to work items, Test Folders or plans. |
Plan testing | Create Test Plans or Advanced Test Plans and prepare test runs for selected requirements. |
Review or record results | Read test run results and logs, or update supported test run results. |
Understand testing progress | Review coverage, execution and burnup reports to identify gaps and follow progress. |
The actions available depend on the supported tools and your permissions. See Supported MCP Tools for the detailed list.
How the connection works
Add Vansah to your AI assistant using a supported connection method.
Sign in with the Atlassian account that has access to the Jira site you want to use, and review the requested permissions.
Choose the Jira site when prompted. Your assistant can then use the available Vansah tools for that connection.
Vansah uses Atlassian OAuth for sign-in. You do not need to give the assistant your Atlassian password or an API token. Connecting does not give it access beyond your existing Jira and Vansah permissions.
Try a simple request
Start with a request that reads information, and name the Jira space or work item so your assistant knows where to look:
“Show the Vansah spaces I can access.”
“Find the test cases linked to work item CHECKOUT-123.”
“Summarize the results for test plan CHECKOUT-P1.”
Replace the example keys with your own. For requests that create or change testing information, ask the assistant to show you the proposed changes for review before applying them.
Data Residency and Security
Vansah MCP follows the same Data Security and Governance Policy as Vansah for Jira. Customer data processed and retained by Vansah MCP remains within the supported Atlassian data residency region to which the Vansah for Jira app is pinned. Vansah MCP does not independently route, store or replicate customer data outside this designated region.
The diagram below illustrates how an MCP client connects to Vansah and how Vansah’s regional hosting applies.
Your AI provider also matters. Information returned to an assistant is subject to that provider’s own processing and storage terms. Use an assistant approved by your organization and review those terms before connecting sensitive or regulated data.
For the published policies and guidance, see:
Get connected
Follow Connecting to Vansah MCP for setup steps and connection checks. Review MCP Security best practices before using the connection with your team’s data.