Qlane

ai.qlanePublished by qlane.aiOfficial publisherv1.0.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Qlane connects an AI coding editor to Qlane's AI QA service, so the agent can reach your projects, test targets and pull-request findings.

What you can do
  • Reach your Qlane projects, test targets and test cases from inside the editor.
  • See what Qlane found when it ran your app in a browser on pull requests.
  • Work with Qlane's AI QA results without leaving the coding agent.
When to use it
Useful when your team runs Qlane's browser-based AI QA on pull requests and you want the coding agent to consult projects, test targets and findings while working in the editor.
Requirements
A remote MCP endpoint at mcp-eu.qlane.ai over streamable HTTP, with OAuth sign-in required. A Qlane account with existing projects is implied. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Qlane account, so the assistant can read your projects, test targets and pull-request findings. Review what the connection is allowed to see before authorizing it.

Installation

In SourceWeft

  1. Open Qlane in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.qlane%2Fqlane/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "qlane": {
      "type": "http",
      "url": "https://mcp-eu.qlane.ai/api/mcp"
    }
  }
}

README

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

PathWhat it is
plugins/qlane/The plugin: everything that ships to an editor, and the folder Anthropic's directory reviews.
.claude-plugin/marketplace.jsonThe marketplace Claude Code, Codex and VS Code install from. It points at ./plugins/qlane.
.cursor-plugin/marketplace.jsonCursor's marketplace, pointing at the same folder.
server.jsonThe server's entry in the official MCP Registry, as ai.qlane/qlane.
glama.jsonMaintainer 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.

bash
npm ci --prefix toolingnpm 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.

bash
npm run format --prefix tooling      # apply Prettiernpm 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:

bash
claude plugin validate --strict .               # the marketplace; --strict makes warnings fatalclaude plugin validate --strict plugins/qlane   # the plugin itselfclaude 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.

Source: README.md at commit fb5d16a

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts