Q
qualienai/qualien-mcp
A composite MCP gateway that aggregates multiple MCP servers behind one connection — curated for SDET/QE workflows.
无 SECURITY.md
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项(本地服务器用 command + args,示例见 客户端接法) - 重启客户端
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"qualienai-qualien-mcp": {
"command": "npx",
"args": ["-y", "qualien-mcp"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"qualienai-qualien-mcp": {
"command": "npx",
"args": ["-y", "qualien-mcp"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio qualienai-qualien-mcp -- npx -y qualien-mcp
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 1 ★ · qualienai/qualien-mcp · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 1 ★ · 23 个来源 · mcp
- 安装
npx -y qualien-mcp
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
npx -y qualien-mcp。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
qualienai/qualien-mcp;我们收录于 2026-10-23;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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:
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/qualienai-qualien-mcp/)
- 来源
- awesome · https://github.com/qualienai/qualien-mcp
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 我们没在该仓库根目录找到
SECURITY.md(这不代表不安全)
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。