Developer · Local MCP server
Qaskills
Search, inspect, and install 400+ QA testing skills from qaskills.sh into any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.PramodDutta/qaskills- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-09
- Updated
- 2026-07-09
- Publisher
- PramodDutta (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/PramodDutta) · how
- Repository
- github.com/PramodDutta/qaskills
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @qaskills/mcp | 0.1.2 | stdio |
How to connect Qaskills
Qaskills runs locally from a Node.js package published to the npm registry: @qaskills/mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @qaskills/mcp@0.1.2. It reads the environment variable QASKILLS_API_URL; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"qaskills": {
"command": "npx",
"args": [
"-y",
"@qaskills/mcp@0.1.2"
],
"env": {
"QASKILLS_API_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from PramodDutta (GitHub)
| Server | Runs |
|---|---|
| BrowserbashPlain-English browser tests for AI agents: real Chrome, deterministic verdicts. Free, no API keys. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| QA RadarTells AI agents which files to test first - churn, coverage, and test mapping as risk scores. | Local · stdio |
| QACATTranslation QA: automated checks, AI evaluation, linguistic review, and visual in-context testing. | Remote · HTTPLive check: sign-in required |
| Qai Consultant MCPKeyless local MCP server for QA: standards retrieval, effort estimation, doc review, test analysis. | Local · stdio |
| QarunbookShared app-testing runbook: read the plan, record results per platform, raise and fix issues. | Remote · HTTPLive check: sign-in required |
| QatouchMCP Server for software testing, test case management, test execution, and defect tracking. | Local · stdio |
| Qiao-MCP - Bridge Engineering (桥梁工程)Full-lifecycle bridge structural analysis - modeling, staging, code checks. | Local · stdio |
| qiklyGenerates tests from acceptance criteria, then converges code with an agent that never sees them. | Local · stdio |
| QlaneAI QA that runs your app in a browser on every pull request: projects, test targets, test cases. | Remote · HTTPLive check: sign-in required |