QA-Path MCP Server

QA-Path is a Model Context Protocol (MCP) server that provides comprehensive test case management capabilities for the QA-Path Test Management System. It allows you to manage test cases, modules, components, and subcomponents directly from Cursor, VS Code, Claude, or any MCP-compatible client.

Quick links: Install from npm · All tools

Features

• qa-path-test-planner agent: Standard, repeatable test planning via an MCP prompt that uses embedded context (no manual context file required)
• Module Management: Create, update, delete, and list modules, components, and subcomponents
• Test Case Management: Full CRUD operations for test cases
• Test Case Operations: Clone, move, and bulk create test cases
• Export/Import: Export test cases to Excel and import from Excel files
• Permission-Aware: Respects the same permissions as the web application
• API key auth: Authenticate with your QA-Path API key

Installation

Prerequisites

• Node.js 18.0.0 or higher
• Access to a QA-Path Test Management System instance
• An API key from your QA-Path profile (API tokens)

Quick Install (Recommended)

Option 1: Using npx (No installation required)

Simply use npx in your MCP configuration - it will download and run the package automatically:

{
  "mcpServers": {
    "qa-path": {
      "command": "npx",
      "args": ["-y", "@alternative-path/qa-path-mcp"],
      "env": {
        "QA_PATH_API_URL": "https://api.qa-path.com/api/",
        "QA_PATH_API_KEY": "your-api-key"
      }
    }
  }
}

Option 2: Global Installation

npm install -g @alternative-path/qa-path-mcp

Then use in your MCP configuration:

{
  "mcpServers": {
    "qa-path": {
      "command": "qa-path-mcp",
      "env": {
        "QA_PATH_API_URL": "https://api.qa-path.com/api/",
        "QA_PATH_API_KEY": "your-api-key"
      }
    }
  }
}

Option 3: Local Installation

npm install @alternative-path/qa-path-mcp

Then use the full path:

{
  "mcpServers": {
    "qa-path": {
      "command": "node",
      "args": ["./node_modules/@alternative-path/qa-path-mcp/dist/index.js"],
      "env": {
        "QA_PATH_API_URL": "https://api.qa-path.com/api/",
        "QA_PATH_API_KEY": "your-api-key"
      }
    }
  }
}

Install from Source (Development)

git clone <repository-url>
cd qapath-mcp
npm install
npm run build

Configuration

QA-Path requires configuration via environment variables (e.g. in your MCP config or shell).

Required Configuration

# API base URL (e.g. https://api.qa-path.com/api/)
QA_PATH_API_URL=https://api.qa-path.com/api/

# API key (required) — from your QA-Path profile / API tokens
QA_PATH_API_KEY=your-api-key-here

Optional Configuration

# Project can be set at runtime via set_active_project; optional default:
# QA_PATH_PROJECT_ID=your-project-id-here

Example .env file

# API Configuration
QA_PATH_API_URL=https://api.qa-path.com/api/
QA_PATH_API_KEY=your-api-key-here

Usage with Cursor

1. Open Cursor settings
2. Navigate to MCP settings
3. Add the following configuration:

{
  "mcpServers": {
    "qa-path": {
      "command": "npx",
      "args": ["-y", "@alternative-path/qa-path-mcp"],
      "env": {
        "QA_PATH_API_URL": "https://api.qa-path.com/api/",
        "QA_PATH_API_KEY": "your-api-key"
      }
    }
  }
}

Usage with VS Code

1. Install the MCP extension for VS Code
2. Configure the MCP server in your VS Code settings:

{
  "mcp.servers": {
    "qa-path": {
      "command": "npx",
      "args": ["-y", "@alternative-path/qa-path-mcp"],
      "env": {
        "QA_PATH_API_URL": "https://api.qa-path.com/api/",
        "QA_PATH_API_KEY": "your-api-key"
      }
    }
  }
}

Tools and Prompts

For a complete list of all MCP tools and prompts, including parameters, sample prompts, and examples, see TOOLS_DOCUMENTATION.md.

Permissions

QA-Path respects the same permission system as the web application. Users can only perform actions they have permission for. If you receive a 403 Forbidden error, check your user permissions in the web application.

Security

• Authentication is token-based (API key). The MCP server has the same permissions as the credentials you provide; use scoped or least-privilege tokens where your backend supports them.
• Authorization and multi-tenant isolation are enforced entirely on the server. This client does not perform access control; it only forwards authenticated requests.
• Do not commit secrets. Never put QA_PATH_API_KEY or other credentials in version control, shared configs, or screenshots. Use environment variables or a local .env file that is listed in .gitignore.

Troubleshooting

Authentication Errors

• 401 Unauthorized: Check your QA_PATH_API_KEY
• 403 Forbidden: You don't have permission for this action. Check your user role and permissions.

Connection Errors

• Network error: Verify that QA_PATH_API_URL is correct and the server is accessible
• Timeout: The server might be slow. Try increasing the timeout in the API client.

Project ID Errors

• Set an active project via the set_active_project tool (after list_projects), or pass projectId to individual tool calls
• Optionally set QA_PATH_PROJECT_ID in the environment as a default

Development

Building from Source

npm install
npm run build

Running in Development Mode

npm run dev

Testing

npm test

License

MIT — Copyright (c) 2026 Alternative Path

Support

For issues and questions, please contact the Alternative Path team or open an issue in the repository.