Now that you've installed Vansah MCP, you're ready to explore how AI assistants can securely interact with your Vansah testing workspace. Using natural language, AI agents can create, search, update, and manage requirements, test cases, test plans, test runs, defects, and other testing assets directly within Vansah.
Vansah MCP tools work seamlessly together through prompts, allowing AI assistants to perform multiple actions in a single request. For example, you can ask your AI assistant to search for existing test cases, generate new test cases from user stories, update test execution results, create defects from failed tests, and organize assets into folders all from one prompt.
By understanding these capabilities, you can craft powerful prompts that automate complex quality engineering workflows and significantly improve productivity.
MCP tools
Test Cases
Test Cases
Create, manage, and organise manual and automated test cases.
Search Test Cases
Search test cases using keywords, folders, components, priorities, automation status, or linked requirements.
Example prompts
Find login test cases.
Show regression tests for Payments.
List automated test cases.
Create Test Cases
Create Test Cases
Generate new test cases from requirements, user stories, defects, or natural language.
Supported fields include:
Title
Objective
Preconditions
Test Steps
Expected Results
Priority
Folder
Labels
Example prompts
Create test cases for user registration.
Generate boundary tests for age validation.
Create happy path and negative test cases.
Update Test Case
Update Test Case
Modify existing test cases.
Update:
Test Steps
Expected Results
Priority
Folder
Automation Status
Labels
Custom Fields
Example prompts
Move these test cases into Regression.
Update the expected results.
Mark this test case as automated.
Test Plans
Test Plans
Manage test planning activities.
Search Test Plans
Search by:
Release
Sprint
Status
Owner
Labels
Create Test Plan
Create Test Plan
Create a new test plan and configure:
Scope
Objectives
Releases
Iterations
Assigned testers
Update Test Plan
Update Test Plan
Modify:
Name
Description
Status
Schedule
Assigned users
Traceability
Traceability
Explore relationships across your testing lifecycle.
View Traceability
Retrieve links between:
Requirements
Test Cases
Test Runs
Test Logs
Defects
Example prompts
Show all test cases covering this requirement.
Which failed tests relate to this defect?
Find requirements without test coverage.
Search
Search
Search across your entire Vansah workspace.
Search includes:
Requirements
Test Cases
Test Plans
Test Runs
Test Logs
Defects
Folders
Example prompts
Find everything related to authentication.
Search for Payment Gateway.
Show all failed regression tests.
Rate Limits
To ensure a reliable experience for all users, Vansah MCP enforces rate limits on API requests made through AI assistants. All requests performed by MCP tools count toward your API usage limits.
Rate limits are applied at two levels:
Per User – Limits the number of requests an authenticated user can make within a given time period.
Per Workspace – Limits the total number of requests across all users, AI assistants, and integrations connected to the same Vansah workspace. This limit depends on your Vansah subscription plan.
Because the workspace limit is shared, requests may be rate limited even if an individual user has not reached their personal limit.
Some MCP tools may also have tool-specific rate limits that are lower than the general API limits. These limits may change over time as the platform evolves.
Current Limits
Limit | Value |
General API Requests | 180 requests per minute (example) |
Search Operations | 30 requests per minute (example) |
Note: The values above are examples. Refer to the latest Vansah API documentation for the current limits applicable to your workspace.
Examples
The following examples demonstrate when rate limiting may occur:
35 search requests per minute → Exceeds the search-specific limit.
12 search requests + 170 API requests per minute → Exceeds the general API request limit.
185 API requests per minute → Exceeds the general API request limit.
When a rate limit is exceeded, your MCP client may receive a 429 Too Many Requests response. We recommend implementing exponential backoff or retry logic before sending additional requests.