Q
qualienai/qualien-mcp
A composite MCP gateway that aggregates multiple MCP servers behind one connection — curated for SDET/QE workflows.
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"qualienai-qualien-mcp": {
"command": "npx",
"args": ["-y", "qualien-mcp"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"qualienai-qualien-mcp": {
"command": "npx",
"args": ["-y", "qualien-mcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio qualienai-qualien-mcp -- npx -y qualien-mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · qualienai/qualien-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 1 ★ · 23 sources · mcp
- Install
npx -y qualien-mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y qualien-mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
qualienai/qualien-mcp;first catalogued 2026-10-23;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# qualien-mcp
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
One MCP server that gives your AI assistant a QA toolkit: Playwright, your test files, GitHub, Jira, Postgres and more, behind a single connection.
qualien-mcp is a composite MCP gateway for SDET / QE work. It aggregates Model Context Protocol servers behind one connection, with a curated catalog of 21 testing-relevant servers, per-tool allow/deny, and read-only-by-default guardrails. Add one server to Claude Code, Claude Desktop, Cursor or VS Code instead of five.
bash
npx qualien-mcp
Out of the box it serves the QE starter pair: Playwright MCP (browser automation, DOM, screenshots) and Filesystem MCP (read/edit project files, page objects, test utils), with zero config. Tools are exposed to your assistant namespaced as playwright… and filesystem….
## Why a gateway?
Your assistant can already connect to many MCP servers directly — so a gateway earns its place by doing what a pile of servers can't:
One endpoint to add to any client (Claude Code, Claude Desktop, Cursor, …).
Curation — enable/disable per server and per tool. Fewer, better-named tools = better tool-selection by the model (dumping 200 tools at it makes it worse).
One routing/logging surface — every call is logged to stderr with the downstream, tool, and latency.
Clean lifecycle — spawns each downstream as a child process and tears them all down on exit (no orphaned browser processes).
Curated for QE — an opinionated SDET toolkit, not a generic proxy.
## Use it with your assistant
Claude Code:
bash
claude mcp add qualien -- npx -y qualien-mcp
or in .mcp.json / user settings:
json
"mcpServers": {
"qualien": { "command": "npx", "args": ["-y", "qualien-mcp"] }
Claude Desktop (claudedesktopconfig.json) and Cursor (~/.cursor/mcp.json or .cursor/mcp.json): the same shape under mcpServers.
Claude Desktop extension: download qualien-mcp- .mcpb from the latest release and open it. Claude Desktop asks for a project folder: the Filesystem tools are limited to it, and a qualien-mcp.config.json inside it turns on more servers. Also listed on Smithery.
VS Code (.vscode/mcp.json):
json
"servers": {
"qualien": { "command": "npx", "args": ["-y", "qualien-mcp"] }
That single entry gives your assistant every tool from every aggregated server.
## Add more servers
Drop a qualien-mcp.config.json in your working directory (or pass --config ). Entries merge over the built-in defaults — redefine a key to change it, or set enabled: false to turn a default off. No new release needed.
json
"servers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/abs/path/to/allow"]
},
"sequential-thinking": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]
},
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
},
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest"],
"tools": { "deny": ["browserclose"] }
See qualien-mcp.config.example.json for the full shape (command, args, env, enabled, tools.allow / tools.deny).
### Built-in catalog
qualien-mcp ships a curated catalog of 21 known servers (each verified against npm), so you enable one by key with just your secrets — no need to remember packages or commands:
qualien-mcp is a composite MCP gateway for SDET / QE work. It aggregates Model Context Protocol servers behind one connection, with a curated catalog of 21 testing-relevant servers, per-tool allow/deny, and read-only-by-default guardrails. Add one server to Claude Code, Claude Desktop, Cursor or VS Code instead of five.
bash
npx qualien-mcp
Out of the box it serves the QE starter pair: Playwright MCP (browser automation, DOM, screenshots) and Filesystem MCP (read/edit project files, page objects, test utils), with zero config. Tools are exposed to your assistant namespaced as playwright… and filesystem….
## Why a gateway?
Your assistant can already connect to many MCP servers directly — so a gateway earns its place by doing what a pile of servers can't:
One endpoint to add to any client (Claude Code, Claude Desktop, Cursor, …).
Curation — enable/disable per server and per tool. Fewer, better-named tools = better tool-selection by the model (dumping 200 tools at it makes it worse).
One routing/logging surface — every call is logged to stderr with the downstream, tool, and latency.
Clean lifecycle — spawns each downstream as a child process and tears them all down on exit (no orphaned browser processes).
Curated for QE — an opinionated SDET toolkit, not a generic proxy.
## Use it with your assistant
Claude Code:
bash
claude mcp add qualien -- npx -y qualien-mcp
or in .mcp.json / user settings:
json
"mcpServers": {
"qualien": { "command": "npx", "args": ["-y", "qualien-mcp"] }
Claude Desktop (claudedesktopconfig.json) and Cursor (~/.cursor/mcp.json or .cursor/mcp.json): the same shape under mcpServers.
Claude Desktop extension: download qualien-mcp- .mcpb from the latest release and open it. Claude Desktop asks for a project folder: the Filesystem tools are limited to it, and a qualien-mcp.config.json inside it turns on more servers. Also listed on Smithery.
VS Code (.vscode/mcp.json):
json
"servers": {
"qualien": { "command": "npx", "args": ["-y", "qualien-mcp"] }
That single entry gives your assistant every tool from every aggregated server.
## Add more servers
Drop a qualien-mcp.config.json in your working directory (or pass --config ). Entries merge over the built-in defaults — redefine a key to change it, or set enabled: false to turn a default off. No new release needed.
json
"servers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/abs/path/to/allow"]
},
"sequential-thinking": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]
},
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
},
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest"],
"tools": { "deny": ["browserclose"] }
See qualien-mcp.config.example.json for the full shape (command, args, env, enabled, tools.allow / tools.deny).
### Built-in catalog
qualien-mcp ships a curated catalog of 21 known servers (each verified against npm), so you enable one by key with just your secrets — no need to remember packages or commands:
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/qualienai-qualien-mcp/)
- Source
- awesome · https://github.com/qualienai/qualien-mcp
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.