
A composite MCP gateway that aggregates multiple MCP servers behind one connection — curated for
A composite MCP gateway that aggregates multiple MCP servers behind one connection — curated for SDET/QE workflows.
·
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.
npx qualien-mcpOut 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__….
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:
Claude Code:
claude mcp add qualien -- npx -y qualien-mcpor in .mcp.json / user settings:
{
"mcpServers": {
"qualien": { "command": "npx", "args": ["-y", "qualien-mcp"] }
}
}Claude Desktop (claude_desktop_config.json) and Cursor (~/.cursor/mcp.json or .cursor/mcp.json): the same shape under mcpServers.
Claude Desktop extension: download qualien-mcp-<version>.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):
{
"servers": {
"qualien": { "command": "npx", "args": ["-y", "qualien-mcp"] }
}
}That single entry gives your assistant every tool from every aggregated server.
Drop a qualien-mcp.config.json in your working directory (or pass --config <path>). 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.
{
"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": ["browser_close"] }
}
}
}See qualien-mcp.config.example.json for the full shape (command, args, env, enabled, tools.allow / tools.deny).
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:
{
"servers": {
"chrome-devtools": { "enabled": true },
"postgres": { "enabled": true, "env": { "DATABASE_URI": "postgres://…" } },
"slack": { "enabled": true, "env": { "SLACK_MCP_XOXP_TOKEN": "xoxp-…" } }
}
}Run npx qualien-mcp catalog to list them all with what each needs. Current catalog:
| Key | What | Needs |
|---|---|---|
playwright (default) | Browser automation, DOM, screenshots | — |
filesystem (default) | Read/edit project files | a dir to allow (default cwd) |
github | PRs, issues, code review | login github (see below) |
sequential-thinking | Structured reasoning / debugging | — |
memory | Persistent knowledge graph | — |
chrome-devtools | Network, console, perf, storage | — |
postgres | SQL / validate backend data | DATABASE_URI |
mysql | SQL / validate backend data | MySQL env |
slack | Read/post Slack | SLACK_MCP_XOXP_TOKEN |
docker | Manage containers | Docker daemon |
kubernetes | Inspect/operate a cluster | kubeconfig |
openapi | Drive any REST API from its spec | API_BASE_URL, OPENAPI_SPEC_PATH |
jira | Read/update Jira issues | Atlassian API token env |
figma | Read Figma designs | FIGMA_API_KEY |
confluence | Test plans, release notes, living docs | Atlassian API token env |
azure-devops | Work items, repos, pipelines, test plans | your ADO org as an arg + sign-in |
selenium | Drive a browser via Selenium WebDriver | a browser + driver on PATH |
webdriverio | Browser and native-mobile automation | — (cloud creds optional) |
browserstack | Real browser/device cloud; read test runs | BROWSERSTACK_USERNAME, BROWSERSTACK_ACCESS_KEY |
ms-365 | Excel, Word, Outlook, Teams, SharePoint | AZURE_CLIENT_ID, AZURE_TENANT_ID |
sentry | Real user-facing errors → new tests | a Sentry auth token |
use mounts a catalog server under a different key (e.g. two databases): { "db-prod": { "use": "postgres", "enabled": true, "env": {…} } }. Anything not in the catalog you still define in full (command/args or type/url).
Downstreams can be remote (Streamable HTTP) as well as local. A remote server is { "type": "http", "url": "…" }, and if it needs OAuth, each user logs in with their own account — tokens are stored per user at ~/.qualien-mcp/credentials.json (0600), on that user's own machine, and are never bundled, shared, or sent anywhere by qualien-mcp.
GitHub's hosted MCP is the reference case, and it needs no setup beyond one command:
qualien-mcp.config.json:
{ "servers": { "github": { "enabled": true } } }npx qualien-mcp login githublogin prints a short code and a URL; you approve it on github.com and you're done. There is no OAuth App to register and no client secret anywhere.
GitHub requires a client_secret to exchange an authorization code — PKCE does not lift that, because GitHub does not distinguish public from confidential clients. qualien-mcp ships on npm, so a secret in the package would be a published secret. The device flow is the one grant GitHub allows without a secret, and it's the grant GitHub recommends for CLIs. So qualien-mcp ships only a public client id — an identifier, not a credential — and every user's tokens are minted on, and stay on, their own machine.
To use your own GitHub OAuth App instead of the shipped one, set clientId (and enable the device flow on it under Settings → Developer settings → OAuth Apps):
{
"servers": {
"github": { "clientId": "<your client id>", "enabled": true }
}
}If a remote server isn't logged in yet, the gateway skips it with a hint (run: npx qualien-mcp login github) and still serves everything else — it never blocks startup. Servers that support dynamic client registration need no clientId at all.
qualien-mcp enforces guardrails centrally, before forwarding a call — so they hold no matter what the downstream permits, and composite tools can't bypass them either:
postgres/mysql calls containing write/DDL SQL (INSERT/UPDATE/DELETE/DROP/…) are refused. Opt in with { "postgres": { "readOnly": false } }.{ "filesystem": { "roots": ["./src", "./tests"] } } refuses any call whose path argument escapes those directories.docker/kubernetes tools whose name looks destructive (delete/remove/prune/kill/…) are refused unless { "allowDestructive": true }.tools.deny / tools.allow curation.Honest scope: these stop an LLM from accidentally doing damage. The SQL check is keyword-based (heuristic), not a parser — it is not adversarial sandboxing. Real isolation needs the downstream's own permissions or a container.
Beyond passthrough, qualien-mcp ships tools it implements itself (namespace qe__) that orchestrate several downstreams in one call — the QE payoff of a gateway.
qe__verify_api_vs_db — end-to-end API↔DB consistency in one call. Give it two sub-calls (namespaced tools you can discover via tools/list); it runs both and diffs the payloads:
{
"api": { "tool": "openapi__getUser", "arguments": { "id": 1 } },
"db": { "tool": "postgres__query", "arguments": { "sql": "select id, name from users where id = 1" } },
"match": "subset" // every field the DB returns must match the API (default)
}
// → { "match": false, "differences": [ { "path": "name", "api": "Ann", "db": "Bob" } ], … }Composite tools appear only when their required downstreams are connected (qe__verify_api_vs_db needs a database server). More to come (repro-from-Jira, page-object-from-URL, flaky triage).
In one process, qualien-mcp is both an MCP server to your assistant and an MCP client to each downstream:
assistant ⇄ qualien-mcp ⇄ playwright-mcp
⇄ filesystem-mcp
⇄ …tools/list fans out to every downstream, filters by your curation rules, and namespaces each as <server>__<tool>.tools/call routes by that prefix to the owning server and passes the response straight through.qe__verify_api_vs_dbFound a bug, want a server added to the catalog, or have an idea? Email [email protected] or open an issue. qualien-mcp is part of qualien.ai, which also builds AI agents that test web apps (Olympus) and native Android apps (Pulse) from plain English.
MIT
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add qualien -- npx -y qualien-mcp{
"mcpServers": {
"qualien": {
"args": [
"-y",
"qualien-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"qualien","args":["-y","qualien-mcp"],"command":"npx"}'[mcp_servers.qualien]
command = "npx"
args = ["-y", "qualien-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/qualien-mcp to learn what the "Qualien Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx qualien-mcp
npx qualien-mcp login githubclaude mcp add qualien -- npx -y qualien-mcpThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/qualien-mcp)Nothing comparable is listed yet.
v0.6.2qualien-mcp 0.6.2Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "qualien-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.