qasphere-mcp
The QA Sphere MCP Server enables interaction with QA Sphere test management via APIs, allowing LLMs to access test case information. You can:
Retrieve specific test cases using unique markers (e.g.,
BDI-123)Get project information using project codes
List all projects in the QA Sphere account
List test cases with options for filtering, pagination, sorting, and including related data
List test case folders with pagination and sorting options
List all tags defined within a project
Supports running the QA Sphere MCP server using Node.js, allowing interaction with QA Sphere's test management system
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@qasphere-mcp show me test cases for the login feature"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
QA Sphere MCP Server
This repository is archived and no longer maintained.
QA Sphere now serves an MCP server directly — there is no need to run this standalone package. The hosted server is always up to date with the QA Sphere API, exposes the full set of tools allowed by your role, and needs nothing installed locally.
Recommended setup: in QA Sphere go to Settings ⚙️ → MCP Server, pick your assistant and access level, add an API key, and follow the setup instructions shown there. See the QA Sphere documentation for details.
The instructions below are kept for reference only. While running the standalone
server, it points this out once per session; set
QASPHERE_MCP_HIDE_MIGRATION_NOTICE=1 to silence that.
A Model Context Protocol server for the QA Sphere test management system.
This integration enables Large Language Models (LLMs) to interact directly with QA Sphere test cases, allowing you to discover, summarize, and chat about test cases. In AI-powered IDEs that support MCP, you can reference specific QA Sphere test cases within your development workflow.
Prerequisites
Node.js (>=22)
QA Sphere account with API access
API key from QA Sphere (Settings ⚙️ → API Keys → Add API Key)
Your company's QA Sphere URL (e.g.,
example.eu2.qasphere.com)
Related MCP server: MCP RAG Agent Server
Setup Instructions
This server is compatible with any MCP client. Configuration instructions for popular clients are provided below.
Claude Desktop
Navigate to
Claude→Settings→Developer→Edit ConfigOpen
claude_desktop_config.jsonAdd the QA Sphere configuration to the
mcpServersdictionary
Cursor
Option 1: Manual Configuration
Go to
Settings...→Cursor settings→Add new global MCP serverAdd the QA Sphere configuration
Option 2: Quick Install
Click the button below to automatically install and configure the QA Sphere MCP server:
5ire
Open 'Tools' and press 'New'
Complete the form with:
Tool key:
qasphereCommand:
npx -y qasphere-mcpEnvironment variables (see below)
Configuration Template
For any MCP client, use the following configuration format:
{
"mcpServers": {
"qasphere": {
"command": "npx",
"args": ["-y", "qasphere-mcp"],
"env": {
"QASPHERE_TENANT_URL": "your-company.region.qasphere.com",
"QASPHERE_API_KEY": "your-api-key"
}
}
}
}Replace the placeholder values with your actual QA Sphere URL and API key.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Support
If you encounter any issues or need assistance, please file an issue on the GitHub repository.
Available Tools
15 toolscreate_test_caseCreate 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.
Inputs: type (required), title (required), folderId (required), priority (required), +12 more. Returns: id, seq
get_projectGet 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%/...
Inputs: projectCode (required). Returns: id, code, links, title, +5 more
get_test_caseGet 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.
Inputs: marker (required). Returns: id, pos, seq, tags, +23 more
list_custom_fieldsList Custom FieldsA
List all custom fields available for a project. Useful when creating or updating test cases with custom field values — use the systemName property as the key on the customFields parameter of create_test_case / update_test_case. Only enabled fields should be used. Custom fields allow you to extend test cases with additional metadata specific to your organization's needs.
Inputs: projectCode (required). Returns: customFields
list_foldersList FoldersA
List folders for test cases within a specific QA Sphere project. Allows pagination and sorting.
Inputs: projectCode (required), limit, offset, sortField, +1 more. Returns: data, limit, total, offset
list_projectsList ProjectsB
Get a list of all projects from current QA Sphere TMS account (qasphere.com)
Inputs: no named parameters. Returns: projects
list_requirementsList 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 requirementIds parameter.
Inputs: projectCode (required), include, sortField, sortOrder. Returns: requirements
list_test_casesList 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.
Inputs: projectCode (required), tags, draft, limit, +11 more. Returns: data, limit, total, offset
list_test_cases_tagsList Test Case TagsA
List all tags defined within a specific QA Sphere project.
Inputs: projectCode (required), include, sortField, sortOrder. Returns: tags
update_test_caseUpdate 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.
Inputs: projectCode (required), tcaseOrLegacyId (required), tags, links, +10 more. Returns: message
upsert_foldersUpsert 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.
Inputs: folders (required), projectCode (required). Returns: ids
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that exposes the QMetry Test Management for Jira Cloud REST API as tools for MCP-compatible clients. It enables users to manage test cases, test cycles, test executions, test plans, folders, and automation rules through natural language interactions.3057 npmMIT
- FlicenseNot gradedqualityDmaintenanceThis MCP server enables intelligent API testing automation by combining RAG knowledge retrieval with tool execution capabilities. It allows QA engineers to perform natural language-driven API testing with contextual knowledge support.-
- AlicenseAqualityDmaintenanceMCP server for QTM4J (QMetry Test Management for Jira) Open API, enabling test case and cycle management via natural language.2139 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that connects AI agents to TestOps, enabling test case management, launches, defects, and analytics through natural language.48MIT