QA Sphere

by hypersequent

13 stars

410 downloads

Not rated

GitHub Website

About

Integration with [QA Sphere](https://qasphere.com/) test management system, enabling LLMs to discover, summarize, and interact with test cases directly from AI-powered IDEs

Details

Author: hypersequent
Repository: Hypersequent/qasphere-mcp
GitHub stars: 13
Downloads: 410
License: MIT License
Categories: Developer Tools, Project Management, API, Other, Productivity, Design, Workplace, AI, Search, Frontend
Tags: #integration

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below
Plugin Name QA Sphere

Command (node, npx, python, etc.) npx
Arguments
- Argument 1 -y
- Argument 2 qasphere-mcp
Environment
- QASPHERE_API_KEY your-api-key
- QASPHERE_TENANT_URL your-company.region.qasphere.com
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

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

JSON

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

JSON

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

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

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

JSON

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

JSON

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

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

From the repository

This server is compatible with any MCP client. Configuration instructions for popular clients are provided below.

1. Go to Settings... → Cursor settings → Add new global MCP server
2. Add the QA Sphere configuration

Click the button below to automatically install and configure the QA Sphere MCP server:

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.

`list_custom_fields`

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.

`list_folders`

List folders for test cases within a specific QA Sphere project. Allows pagination and sorting.

`upsert_folders`

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.

`get_project`

Get a project information from QA Sphere using a project code (e.g., BDI). You can extract PROJECT_CODE from URLs https://your-company.region.qasphere.com/project/%PROJECT_CODE%/...

`list_projects`

Get a list of all projects from current QA Sphere TMS account (qasphere.com)

`list_requirements`

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.

`list_shared_preconditions`

List reusable shared preconditions for a project. Supports sorting by title or creation date and can include test case usage counts. Use the returned `id` as `sharedPreconditionId` when referencing a shared precondition from create_test_case / update_test_case.

`get_shared_precondition`

Fetch details for a single shared precondition by ID.

`list_shared_steps`

List reusable shared steps for a project. Supports sorting by title or creation date and can include test case usage counts. Use the returned `id` as `sharedStepId` when referencing a shared step from create_test_case / update_test_case.

`get_shared_step`

Fetch details for a single shared step by ID.

`list_test_cases_tags`

List all tags defined within a specific QA Sphere project.

`get_test_case`

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://your-company.region.qasphere.com/project/%PROJECT_CODE%/tcase/%SEQUENCE%?any Extract %PROJECT_CODE% and %SEQUENCE% from the URL and use them as the marker.

`list_test_cases`

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.

`create_test_case`

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.

`update_test_case`

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.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

Linux

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

Macos

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

Windows

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

- Search test cases— Find test cases by title or other criteria usingsearch_cases.
- Retrieve a specific test case— Fetch full details of a test case by its ID withget_case.
- Summarize test coverage— Ask the assistant to summarize what a set of test cases covers based on search results.

AModel Context Protocolserver for the QA Spheretest 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.

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

This server is compatible with any MCP client. Configuration instructions for popular clients are provided below.
- Navigate toClaude→Settings→Developer→Edit Config
- Openclaude_desktop_config.json
- Add the QA Sphere configuration to themcpServersdictionary
- Go toSettings...→Cursor settings→Add new global MCP server
- Add the QA Sphere configuration

Click the button below to automatically install and configure the QA Sphere MCP server:
- Open 'Tools' and press 'New'
- Complete the form with:

- Tool key:qasphere
- Command:npx -y qasphere-mcp
- Environment variables (see below)

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.

This project is licensed under the MIT License - see theLICENSEfile for details.

If you encounter any issues or need assistance, please file an issue on the GitHub repository.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

An MCP server for interacting with the Qase test management platform.

Interact with TestRail's core entities such as test cases, runs, and results using a standardized protocol.

An MCP server for interacting with the Postman API, requiring an API key.

Adds possibility to work with testing management via MCP

An enhanced Apifox MCP service providing comprehensive API management capabilities for Claude Desktop and Cursor.

This MCP Server accepts swagger/postman documents as input. It then generates API & Load test scenarios, executes the tests and generates the execution report.

A Model Context Protocol (MCP) server for creating, managing, and executing Bruno API testing collections. Supports both .bru and .yml (opencollection) formats with built-in security hardening.

Execute Bruno collections using the Bruno CLI, with support for environment files and detailed test results.

An MCP server for Factifai, enabling integration with any MCP-compatible AI tool to create and retrieve test results asynchronously.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

list_custom_fields

list_folders

upsert_folders

get_project

list_projects

list_requirements

list_shared_preconditions

get_shared_precondition

list_shared_steps

get_shared_step

list_test_cases_tags

get_test_case

list_test_cases

create_test_case

update_test_case

Claude Desktop / Cursor

Linux

Macos

Windows

Install

More like this

Sentry

Github

Git

GitLab

Context 7

Playwright

`list_custom_fields`

`list_folders`

`upsert_folders`

`get_project`

`list_projects`

`list_requirements`

`list_shared_preconditions`

`get_shared_precondition`

`list_shared_steps`

`get_shared_step`

`list_test_cases_tags`

`get_test_case`

`list_test_cases`

`create_test_case`

`update_test_case`