qasphere

The QA Sphere MCP server enables large language models to interact with QA Sphere test cases directly through the MCP interface. It lets you discover QA Sphere test cases, generate summaries, and chat about test content within AI-enabled IDEs or MCP-enabled clients. By configuring this server in your MCP client, you can reference specific QA Sphere test cases in prompts, retrieve test metadata, and obtain contextual insights to help with test planning, debugging, or test-case reasoning. Tools exposed by the MCP server include case discovery, summarization of test case details, and conversational querying about test cases using natural language or structured prompts.

Prerequisites:

• Node.js (recent LTS versions)
• Access to QA Sphere with API key
• A QA Sphere URL (tenant URL) such as your-company.region.qasphere.com

Installation steps:

1. Verify Node.js is installed: node -v npm -v

2. Ensure you have your QA Sphere API key and tenant URL from QA Sphere settings.

3. Since this MCP server is run via npx, you don’t need a global install. You can start it directly with: npx -y qasphere-mcp

4. Configure your MCP client to point to the server using the following example configuration (JSON format):

   { "mcpServers": { "qasphere": { "command": "npx", "args": ["-y", "qasphere-mcp"], "env": { "QASPHERE_TENANT_URL": "your-company.region.qasphere.com", "QASPHERE_API_KEY": "your-api-key" } } } }

5. Replace the placeholder values with your actual QA Sphere URL and API key. Integrate this configuration into your MCP client (e.g., Claude Desktop, Cursor, or 5ire) following their instructions.

Note: If you prefer not to run via npx every time, you can explore packaging alternatives or containerized setups as needed, but the recommended approach is to use the npx invocation shown above.

Tips and caveats:

• Ensure the QA Sphere API key has the necessary permissions to access test cases and metadata.
• The tenant URL must be the region-specific URL provided by QA Sphere (e.g., your-company.region.qasphere.com).
• When using MCP clients, add the env block to your mcpServers configuration to securely pass credentials at runtime.
• If you encounter authentication errors, double-check the API key scope and that the URL is reachable from your environment.
• Some MCP clients may require a restart or reloading of configurations after adding the new QA Sphere server entry.
• The provided configuration template uses the qasphere-mcp package name; verify the package name in the official repository if there are updates.