MCP Qase MCP Server

MCP server implementation for Qase API

Local serverstdioTypeScript

What is the MCP Qase MCP server?

Mcp qase mcp server connects MCP Qase to AI assistants that speak the Model Context Protocol. MCP server implementation for Qase API.

What MCP Qase does

This is a TypeScript-based MCP server that provides integration with the Qase test management platform. It implements core MCP concepts by providing tools for interacting with various Qase entities.

Tools it exposes

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

  • Tools — The server provides tools for interacting with the Qase API, allowing you to manage the following entities:
  • Projects — The Projects tool exposed by this server
  • Cursor — The Cursor tool exposed by this server

Installing the mcp qase mcp server

The server is distributed via npm as @modelcontextprotocol/inspector, 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: QASE_API_TOKEN, YOUR_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

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. MCP Qase sits in that group, and the shape of its toolset — Tools, Projects, 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.
  • Maintained by rikuson, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp qase 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
ToolsThe server provides tools for interacting with the Qase API, allowing you to manage the following entities:
ProjectsThe Projects tool exposed by this server.
CursorThe Cursor tool exposed by this server.

How to install the MCP Qase MCP server

{
  "mcpServers": {
    "qase": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "QASE_API_TOKEN": "your-value",
        "YOUR_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
QASE_API_TOKENCredential the server authenticates with.Yes
YOUR_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Qase to Tools.
  • Use MCP Qase to Projects.
  • Use MCP Qase to Cursor.

Frequently asked questions

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