QA Sphere MCP Server

Created By
Hypersequenta year ago
MCP Server for QA Sphere TMS
Overview

what is QA Sphere MCP Server?

QA Sphere MCP Server is a Model Context Protocol server designed for the QA Sphere test management system, enabling Large Language Models (LLMs) to interact with QA Sphere test cases for discovery, summarization, and discussion.

how to use QA Sphere MCP Server?

To use the QA Sphere MCP Server, you need to set it up with a compatible MCP client by configuring it with your QA Sphere account details and API key. Follow the setup instructions for your specific client.

key features of QA Sphere MCP Server?

  • Integration with QA Sphere for test case management
  • Direct interaction with LLMs for enhanced test case discovery and summarization
  • Compatibility with various MCP clients like Claude, Cursor, and 5ire

use cases of QA Sphere MCP Server?

  1. Automating test case management workflows in software development.
  2. Enhancing communication between developers and QA teams through AI-driven insights.
  3. Streamlining the process of referencing test cases within development environments.

FAQ from QA Sphere MCP Server?

  • What are the prerequisites for using QA Sphere MCP Server?

You need Node.js, a QA Sphere account with API access, an API key, and your company's QA Sphere URL.

  • Is there a license for QA Sphere MCP Server?

Yes, it is licensed under the MIT License.

  • Where can I find support for QA Sphere MCP Server?

You can file an issue on the GitHub repository for assistance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Hypersequent
Star
11
Language
JavaScript
License
MIT license

Recommend Servers

View All
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
Crevio

2 days ago