QASE MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QASE_API_TOKEN | Yes | Your Qase API token for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsD | Get All Projects |
| get_projectC | Get project by code |
| create_projectC | Create new project |
| get_resultsC | Get all test run results for a project |
| get_resultC | Get test run result by code and hash |
| create_resultD | Create test run result |
| create_result_bulkC | Create multiple test run results in bulk |
| update_resultC | Update an existing test run result |
| get_casesC | Get all test cases in a project |
| get_caseC | Get a specific test case |
| create_caseC | Create a new test case |
| update_caseC | Update an existing test case |
| get_runsC | Get all test runs in a project |
| get_runC | Get a specific test run |
| get_plansC | Get all test plans in a project |
| get_planC | Get a specific test plan |
| create_planC | Create a new test plan |
| update_planC | Update an existing test plan |
| get_suitesC | Get all test suites in a project |
| get_suiteC | Get a specific test suite |
| create_suiteC | Create a new test suite |
| update_suiteC | Update an existing test suite |
| get_shared_stepsC | Get all shared steps in a project |
| get_shared_stepC | Get a specific shared step |
| create_shared_stepD | Create a new shared step |
| update_shared_stepC | Update an existing shared step |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Each tool has a clearly distinct purpose targeting specific resources (cases, plans, projects, results, shared steps, suites, runs) with unambiguous actions (create, get, update, list). No overlapping functionality exists between tools, making selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with perfect uniformity (e.g., create_case, get_cases, update_suite). The naming convention is predictable across all 26 tools, using snake_case consistently without any deviations or mixed styles.
With 26 tools, the count is borderline high for typical MCP servers, which often have 3-15 tools. While the tools are well-organized, the number may feel heavy and could overwhelm agents, though it aligns with comprehensive test management coverage.
The tool set provides complete CRUD/lifecycle coverage for test management, including create, get, update, and list operations for all core resources (cases, plans, projects, results, shared steps, suites, runs). No obvious gaps exist, ensuring agents can handle full workflows without dead ends.