# Qlane [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/qlaneai/agent-plugin  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/qlane

## Description
AI QA that runs your app in a browser on every pull request: projects, test targets, test cases.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "qlane": {
    "url": "https://mcp-eu.qlane.ai/api/mcp"
  }
}
```

## Documentation

## What Qlane MCP server does

The Qlane MCP server gives an AI coding editor access to Qlane projects, test targets, and findings from pull-request test runs. It can show run verdicts, failed or blocked test cases, detected defects, reproduction steps, and supporting evidence.

Three included skills cover the main workflows:

- `/qlane:setup-env` finds or creates the Qlane project for a repository, prepares the repository using Qlane’s published setup guidance, and creates a test target after configuration checks pass.
- `/qlane:bugs` reviews a pull request or recent run, investigates likely causes in the repository, and proposes a code fix. It reads Qlane data and only changes code after approval.
- `/qlane:test-local-changes` plans tests for an unsubmitted local diff and runs them against the developer’s running application.

## How it works

Qlane provides two independent regional MCP services. The EU endpoint is `https://mcp-eu.qlane.ai/api/mcp`, while the US endpoint is `https://mcp-us.qlane.ai/api/mcp`. Connect only the endpoint hosting the organization. Connecting the other endpoint returns a 403 that identifies the correct host.

The Qlane MCP server uses HTTPS and editor-managed authentication. An account is required, and the editor prompts for sign-in when the server is first called. The setup workflow directs developers to enter test-target variables and test credentials on a Qlane page; these values do not pass through the editor. Repository and Qlane configuration changes require confirmation.

## Setup and configuration

Claude Code can install the plugin from the Qlane marketplace and then authenticate either regional server. VS Code and GitHub Copilot load it after the repository is added to `chat.plugins.marketplaces`; `chat.plugins.enabled` must be enabled if the plugin does not appear. Cursor imports the full GitHub repository URL, and Kiro loads the root plugin manifest. Codex registers the marketplace through its CLI but installs the plugin from the Plugins Directory in the ChatGPT desktop app.

The server can also be added directly in an MCP client. For Claude Code, use the HTTP transport with the appropriate regional URL. There is no documented environment-variable configuration or value substitution for the regional endpoints.

## Limitations and notes

The plugin registers both regional servers, but only the organization’s region supplies tools after authentication. The other remains unconnected and contributes no Qlane tools. When opening the plugin repository in Claude Code, its root `.mcp.json` may appear as pending project configuration; that file is the plugin manifest, so it should be declined in that context and the plugin installed normally.

The setup skill can modify repository and Qlane configuration only after asking for approval. The bug-investigation skill does not change code without approval. Local-change testing requires the application to be running. Qlane’s regional endpoints are static, and the repository states that any MCP client may connect directly to an endpoint.

_Full upstream README: https://allmcps.com/mcp/qlane/readme_