Qase MCP Server

Created By
raksula year ago
Overview

What is Qase MCP Server?

Qase MCP Server is a Model Context Protocol (MCP) server designed to integrate with the Qase test management platform, providing functionalities for creating, retrieving, and managing test cases and test executions.

How to use Qase MCP Server?

To use Qase MCP Server, set up the environment by installing Node.js and TypeScript, and configure the MCP settings file with your Qase API token. After installation, you can run the server and utilize its tools to manage your test cases.

Key features of Qase MCP Server?

  • Create and manage test cases and test suites.
  • Retrieve lists of projects and test cases.
  • Execute test runs and manage test execution results.
  • Bulk creation of test cases for efficient management.

Use cases of Qase MCP Server?

  1. Managing test cases for software development projects.
  2. Automating the testing process in CI/CD pipelines.
  3. Collaborating with teams on test case management and execution.

FAQ from Qase MCP Server?

  • What are the prerequisites for using Qase MCP Server?

You need Node.js v23.5.0, a Qase API token, and TypeScript installed.

  • Is there a way to bulk create test cases?

Yes! You can use the create_test_cases_in_bulk tool to create multiple test cases at once.

  • How do I handle errors in Qase MCP Server?

The server provides error messages for authentication issues, parameter errors, and API errors, along with suggested solutions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
raksul
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago