Qlane MCP server
{
"mcpServers": {
"qlane": {
"type": "http",
"url": "https://mcp-eu.qlane.ai/api/mcp"
}
}
}{
"mcpServers": {
"qlane": {
"type": "http",
"url": "https://mcp-eu.qlane.ai/api/mcp"
}
}
}{
"mcpServers": {
"qlane": {
"type": "http",
"url": "https://mcp-eu.qlane.ai/api/mcp"
}
}
}{
"servers": {
"qlane": {
"type": "http",
"url": "https://mcp-eu.qlane.ai/api/mcp"
}
}
}{
"mcpServers": {
"qlane": {
"type": "http",
"url": "https://mcp-eu.qlane.ai/api/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
Qlane MCP exposes Qlane QA project data—projects, test targets, and test-case counts—to AI coding editors via two regional HTTP endpoints. It is aimed at developers who use Qlane for browser-based automated QA and want their agent to read and plan tests without leaving the editor.
- List your Qlane projects and test targets from within an AI coding editor during development.
- Check test-case counts for a target before opening a pull request.
- Plan tests against a local diff before a pull request exists, consuming Qlane credits.
Tools this server exposes
| Tool | Does |
|---|---|
| list_projects | Returns the Qlane projects accessible to the authenticated account. |
| list_test_targets | Returns test targets associated with a given project. |
| get_test_case_counts | Returns the number of test cases for a given test target. |
| plan_tests | Plans tests for a local diff against a Qlane target, consuming credits. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.