qasphere-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QASPHERE_API_KEY | Yes | API key from QA Sphere (Settings ⚙️ → API Keys → Add API Key) | |
| QASPHERE_TENANT_URL | Yes | Your company's QA Sphere URL (e.g., example.eu2.qasphere.com) |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_custom_fieldsA | List all custom fields available for a project. Useful when creating or updating test cases with custom field values — use the |
| list_foldersA | List folders for test cases within a specific QA Sphere project. Allows pagination and sorting. |
| upsert_foldersA | Creates or updates multiple folders in a single request using folder path hierarchies. Automatically creates nested folder structures and updates existing folders' comments. Returns an array of folder ID arrays, each representing the full folder path hierarchy as an array of folder IDs. |
| get_projectA | Get a project information from QA Sphere using a project code (e.g., BDI). You can extract PROJECT_CODE from URLs https://acme-corp.eu2.qasphere.com/project/%PROJECT_CODE%/... |
| list_projectsB | Get a list of all projects from current QA Sphere TMS account (qasphere.com) |
| list_requirementsA | List requirements linked to test cases in a project. Requirements are references to external documentation or specifications (like Jira issues) that test cases verify. Use this tool to find requirement IDs when you need to filter test cases by requirement using list_test_cases with the |
| list_shared_preconditionsB | List reusable shared preconditions for a project. Supports sorting by title or creation date and can include test case usage counts. Use the returned |
| get_shared_preconditionA | Fetch details for a single shared precondition by ID. |
| list_shared_stepsA | List reusable shared steps for a project. Supports sorting by title or creation date and can include test case usage counts. Use the returned |
| get_shared_stepB | Fetch details for a single shared step by ID. |
| list_test_cases_tagsA | List all tags defined within a specific QA Sphere project. |
| get_test_caseA | Get a test case from QA Sphere using a marker in the format PROJECT_CODE-SEQUENCE (e.g., BDI-123). You can use URLs like: https://acme-corp.eu2.qasphere.com/project/%PROJECT_CODE%/tcase/%SEQUENCE%?any Extract %PROJECT_CODE% and %SEQUENCE% from the URL and use them as the marker. |
| list_test_casesB | List test cases from a project in QA Sphere. Supports pagination and various filtering options. Usually it makes sense to call get_project tool first to get the project context. |
| create_test_caseB | Create a new test case in QA Sphere. Supports both standalone and template test cases with various options like steps, tags, requirements, and parameter values for templates. |
| update_test_caseA | Update an existing test case in QA Sphere. Only users with role User or higher are allowed to update test cases. Optional fields can be omitted to keep the current value. |
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 15 tools
Each tool targets a distinct entity and action: projects, folders, test cases, tags, requirements, shared steps, and shared preconditions are all clearly separated. The get/list pairs are unambiguous because one returns details by ID while the other lists collection-level data.
Tool names mostly follow a consistent verb_noun pattern like list_projects, get_test_case, create_test_case, and update_test_case. Minor deviations include upsert_folders and list_test_cases_tags, which break the otherwise predictable naming slightly.
At 15 tools, the set is at the upper bound of a well-scoped server but every tool supports a clear purpose in the QA Sphere test case workflow. The count feels justified by the domain breadth rather than padded with redundant operations.
The main test case lifecycle is well covered with list, get, create, and update, but delete_test_case is missing, which is a notable gap for full CRUD coverage. Supporting entities like shared steps and preconditions are read-only, leaving no way to manage them through this server.