QA Sphere MCP Server

Integration with QA Sphere test management system, enabling LLMs to discover, summarize, and interact with test cases directly from AI-powered IDEs

Local serverstdioGo

What is the QA Sphere MCP server?

QA Sphere becomes available to MCP clients through the qa sphere mcp server. Integration with QA Sphere test management system, enabling LLMs to discover, summarize, and interact with test cases directly from AI-powered IDEs.

What QA Sphere does

A Model Context Protocol server for the QA Sphere test management system.

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

  • Command — npx -y qasphere-mcp
  • Cursor — The Cursor tool exposed by this server

Installing the qa sphere mcp server

The server is distributed via npm as qasphere-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 2 environment variables: QASPHERE_TENANT_URL, QASPHERE_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • 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)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. QA Sphere sits in that group, and the shape of its toolset — Command, Cursor — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Written in Go.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the qa sphere mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
Commandnpx -y qasphere-mcp
CursorThe Cursor tool exposed by this server.

How to install the QA Sphere MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  • 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)
VariableDescriptionRequired
QASPHERE_TENANT_URLEndpoint or connection string the server talks to.Yes
QASPHERE_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use QA Sphere to Command.
  • Use QA Sphere to Cursor.

Frequently asked questions

It connects QA Sphere to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Command, Cursor) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with QA Sphere directly.