Qlane
AI QA that runs your app in a browser on every pull request: projects, test targets, test cases.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http qlane 'https://mcp-eu.qlane.ai/api/mcp'{
"mcpServers": {
"qlane": {
"type": "http",
"url": "https://mcp-eu.qlane.ai/api/mcp"
}
}
}claude mcp add --transport http qlane 'https://mcp-us.qlane.ai/api/mcp'{
"mcpServers": {
"qlane": {
"type": "http",
"url": "https://mcp-us.qlane.ai/api/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Qlane agent plugin
Installs Qlane MCP into your AI coding editor, so your agent can reach your Qlane projects, test targets and what Qlane found on your pull requests without leaving the editor.
To install and use it, see the plugin's README.
Repository layout
| Path | What it is |
|---|---|
plugins/qlane/ | The plugin: everything that ships to an editor, and the folder Anthropic's directory reviews. |
.claude-plugin/marketplace.json | The marketplace Claude Code, Codex and VS Code install from. It points at ./plugins/qlane. |
.cursor-plugin/marketplace.json | Cursor's marketplace, pointing at the same folder. |
server.json | The server's entry in the official MCP Registry, as ai.qlane/qlane. |
glama.json | Maintainer claim for the server's listing on Glama. |
tooling/ | Development tooling: formatting, linting, schema validation, tests. None of it ships. |
Development
The development tooling lives in tooling/, its own npm package, outside the plugin folder, so
none of it ships. A test pins the plugin folder to the files that do.
npm ci --prefix tooling
npm run check --prefix toolingcheck runs Prettier, markdownlint, JSON Schema validation of the portable manifests, and the
unit tests, over the whole repository. It makes no network calls, so it works offline and in a
sandboxed CI runner.
npm run format --prefix tooling # apply Prettier
npm run lint:md:fix --prefix tooling # apply markdownlint's safe fixesTwo checks need the Claude Code CLI and so are not part of check, which has to run on a
runner that does not have it:
claude plugin validate --strict . # the marketplace; --strict makes warnings fatal
claude plugin validate --strict plugins/qlane # the plugin itself
claude plugin tag --dry-run plugins/qlane # what the next release tag would beThe version lives in the plugin's manifests only. The marketplace entry deliberately declares no
version of its own: plugin.json wins at install time, so a second copy could only ever
agree or be silently ignored.
No manifest may contain a placeholder. Both regional URLs are literal strings in every
manifest. ${user_config.*} resolves only in the Claude Code CLI — the portable Agent Plugins
schema cannot even express userConfig (additionalProperties: false), and claude.ai treats
an MCP url as an opaque connector identity, so a templated host reaches registration verbatim
and fails to resolve. A test enforces this.
License
MIT.
Frequently asked questions
What is Qlane?
AI QA that runs your app in a browser on every pull request: projects, test targets, test cases.
How do I install Qlane?
It runs as a remote server. In Claude Code: claude mcp add --transport http qlane 'https://mcp-eu.qlane.ai/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Qlane need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Qlane open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Qlane?
It is published by qlaneai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.