Schema | QASE MCP Server

QASE MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`QASE_API_TOKEN`	Yes	Your Qase API token for authentication

Server capabilities have not been inspected yet.

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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rikuson/mcp-qase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server