QA SphereSAFE
MCP Server for QA Sphere TMS
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[!IMPORTANT] 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)
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 Config - Open
claude_desktop_config.json - Add the QA Sphere configuration to the
mcpServersdictionary
Cursor
Option 1: Manual Configuration
- Go to
Settings...→Cursor settings→Add new global MCP server - Add the QA Sphere configuration
Option 2: Quick Install
Click the button below to automatically instal
a505df160f33OBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add qasphere-mcp --env QASPHERE_API_KEY=${QASPHERE_API_KEY} -- npx -y [email protected]{
"mcpServers": {
"qasphere-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"QASPHERE_API_KEY": "${QASPHERE_API_KEY}"
}
}
}
}Exposed tools (15)
13 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
create_test_case | write | |
get_project | read | |
get_shared_precondition | read | |
get_shared_step | read | |
get_test_case | read | |
list_custom_fields | read | |
list_folders | read | |
list_projects | read | |
list_requirements | read | |
list_shared_preconditions | read | |
list_shared_steps | read | |
list_test_cases | read | |
list_test_cases_tags | read | |
update_test_case | write | |
upsert_folders | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (7)
import type { ListCustomFieldsOutput } from '../../src/schemas.js'import type { ListFoldersOutput, UpsertFoldersOutput } from '../../src/schemas.js'const REPO_ROOT = path.resolve(__dirname, '../../..')
import type { UpsertFoldersOutput } from '../../../src/schemas.js'import type { GetProjectOutput, ListProjectsOutput } from '../../src/schemas.js'@modelcontextprotocol/sdk, dotenv, zod, @biomejs/biome, @types/node, husky, lint-staged, tsx
> assistant and access level, add an API key, and follow the setup instructions shown
Gates applied: no_behavioural_pass.
a505df160f33full audit observations/trust-audit/mcp-server/hypersequent__qa-sphere.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | a505df160f33 | SAFE | B | 89 | first audit |
Questions
What is the QA Sphere MCP server?
MCP Server for QA Sphere TMS
What tools does QA Sphere expose?
15 in total: 13 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is QA Sphere safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does QA Sphere need?
It reads QASPHERE_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does QA Sphere run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as qasphere-mcp at 0.5.0.
How current is this page?
The grade is for one exact copy of the source (a505df160f33), read on 2026-10-09. The repository is watched and re-audited when it changes.