@qamadness/qam-hub-mcp

MCP server for QAM Hub – lets an AI agent work with your test management data: suites, test cases, test runs and executions, checklists, requirements, milestones, tags, custom fields and templates.

Works with any MCP client (Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, …).

Quick start

1. Create a personal API token in QAM Hub under Profile → API & MCP.
2. Add the server to your MCP client.

Claude Code

claude mcp add qam-hub --env QAM_HUB_URL=<your-backend-url> --env QAM_HUB_TOKEN=<your-token> -- npx -y @qamadness/qam-hub-mcp

Any client with a JSON config (Claude Desktop, Cursor, VS Code, Windsurf)

{
  "mcpServers": {
    "qam-hub": {
      "command": "npx",
      "args": ["-y", "@qamadness/qam-hub-mcp"],
      "env": {
        "QAM_HUB_URL": "<your-backend-url>",
        "QAM_HUB_TOKEN": "<your-token>",
        "QAM_HUB_PROJECT": "<default-project-slug>"
      }
    }
  }
}

The exact snippet with your backend URL already filled in is shown in QAM Hub under Profile → API & MCP.

Configuration

| Variable | Required | Description | |---|---|---| | QAM_HUB_TOKEN | yes | Personal API token from Profile → API & MCP. | | QAM_HUB_URL | yes | Your QAM Hub backend URL. Defaults to http://localhost:3001. | | QAM_HUB_PROJECT | no | Default project slug. Every tool also accepts a projectSlug argument, and tms_list_projects discovers the available slugs. |

The older TMS_TOKEN, TMS_BASE_URL and TMS_DEFAULT_PROJECT_SLUG names are still read as aliases.

Permissions

The token acts as you: the agent can do anything your account can do, in every project you are a member of, and every change is recorded in the audit log under your name. Treat the token like a password, keep it out of committed files, and revoke it in Profile → API & MCP when it is no longer needed.

Requirements

• Node.js 18+
• A QAM Hub account

Learn more

See qam-hub.com.