Qasphere MCP

What Hypersequent/qasphere-mcp does

Hypersequent/qasphere-mcp MCP server exposes QA Sphere test case access through the Model Context Protocol. Its purpose is to bring test management information into conversations and development workflows that use MCP-compatible assistants. An agent can discover relevant test cases, summarize their content, and discuss or reference specific cases while working in an AI-powered IDE.

The integration is intended for teams that keep test cases in QA Sphere and want an assistant to work with that material without requiring users to copy test case details into the conversation manually. The provided material describes access to test cases, but does not list individual MCP tool names or document mutation operations.

How it works

The standalone server runs locally and communicates with a QA Sphere tenant using credentials supplied through environment variables. MCP clients start it with Node.js tooling, then expose its QA Sphere capabilities to the connected language model. The client configuration identifies the process command and passes the tenant address and API key to it.

The repository is archived and no longer maintained. QA Sphere now provides a hosted MCP server directly from the product. That hosted option is described as being kept current with the QA Sphere API, requiring no local installation, and exposing the tools permitted by the user’s role.

Setup and configuration

The archived Hypersequent/qasphere-mcp MCP server requires Node.js 22 or newer, a QA Sphere account with API access, an API key, and the company’s QA Sphere tenant URL. The API key is created in QA Sphere under Settings, API Keys, and Add API Key.

A compatible MCP client can start the package with:

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

Claude Desktop and Cursor setup instructions are included in the repository. Cursor also has a documented quick-install option, while other MCP clients can use the same general configuration structure. Replace the example environment values with the actual tenant hostname and API key.

Tools and capabilities

The documented capabilities include:

• Discovering QA Sphere test cases
• Summarizing test case content
• Chatting about test cases
• Referencing specific test cases from an AI-powered IDE
• Restricting hosted-server tools according to the user’s QA Sphere role

The README does not provide a complete tool catalog, input schema, or output schema for the standalone package. It also does not establish that the server can create, edit, delete, execute, or otherwise mutate test cases.

Limitations and notes

The most important limitation is project status: the standalone repository is archived and no longer maintained. QA Sphere recommends using its hosted MCP server, configured from Settings, MCP Server, where the assistant and access level can be selected and an API key can be added. That hosted service is the better fit when current API coverage and role-based tool availability matter.

The standalone package remains documented for reference and can display a migration notice. Setting QASPHERE_MCP_HIDE_MIGRATION_NOTICE=1 suppresses that notice for a session. The available material does not state which QA Sphere subscription levels include API access, so service pricing cannot be determined from this listing.

Getting started with this Hypersequent/qasphere-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.