About Qlane
The Qlane plugin connects Qlane MCP to AI coding editors, letting developers view Qlane projects, test targets, and pull-request findings from the editor. The repository also includes marketplace manifests for several editors and offline checks for plugin development.
Key features
- 01Connect Qlane MCP in coding editors
- 02View Qlane projects and test targets
- 03See pull-request test findings
- 04Manifests for multiple editor marketplaces
- 05Offline formatting, lint, schema, and unit checks
Use cases
- 01Review Qlane projects in a coding workflow
- 02Inspect an application’s test targets
- 03Check QA findings on a pull request
- 04Validate plugin files in offline CI
MCP support
The plugin connects Qlane MCP to AI coding editors so agents can access Qlane projects, test targets, and pull-request test findings.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp-eu.qlane.ai/api/mcpclaude mcp add --transport http ai-qlane-qlane https://mcp-eu.qlane.ai/api/mcp{"mcpServers":{"ai-qlane-qlane":{"type":"http","url":"https://mcp-eu.qlane.ai/api/mcp"}}}Open in Cursor{"servers":{"ai-qlane-qlane":{"type":"http","url":"https://mcp-eu.qlane.ai/api/mcp"}}}Open in VS Code{"mcpServers":{"ai-qlane-qlane":{"type":"http","url":"https://mcp-eu.qlane.ai/api/mcp"}}}{"mcpServers":{"ai-qlane-qlane":{"serverUrl":"https://mcp-eu.qlane.ai/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://mcp-eu.qlane.ai/api/mcphttps://mcp-us.qlane.ai/api/mcpTools
Details
From the project READMEQlane 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 tooling
check 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 fixes
Two 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 be
The 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.