mintqa-mcp

mintqa-mcp

MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR and posts video proof.

Mint handles the test logic; this MCP gives your AI assistant the keys.

What you get

• One tool call to set Mint up on a new repo (replaces a 300-line paste-prompt)
• Trigger Mint runs from your IDE: "test this PR"
• Inspect run results without leaving your terminal

Install

You need a Mint API key. Get one free at mintqa.dev/settings/keys.

Claude Code

claude mcp add mintqa --env MINT_API_KEY=mint_xxx npx mintqa-mcp

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "mintqa": {
      "command": "npx",
      "args": ["mintqa-mcp"],
      "env": { "MINT_API_KEY": "mint_xxx" }
    }
  }
}

Codex CLI / generic MCP client

Run npx mintqa-mcp with MINT_API_KEY in env.

How it works

This package is a thin stdio shim. It speaks the MCP stdio transport on one side and proxies every request/notification to the hosted Mint MCP server at https://mintqa.dev/mcp (Streamable HTTP transport, Bearer auth) on the other.

All tool logic lives server-side, which means:

• New tools show up immediately — no npx mintqa-mcp upgrade needed.
• The shim itself is ~150 lines and almost never republishes.

If your MCP client speaks Streamable HTTP directly, skip this package and point it at https://mintqa.dev/mcp with an Authorization: Bearer … header.

Tools

The hosted server is the source of truth for tool definitions. Ask your client to list tools after connecting (tools/list), or visit mintqa.dev/mcp for the current catalog.

Configuration

Env var	Default	Purpose
MINT_API_KEY	(required)	Bearer token from mintqa.dev
MINT_MCP_URL	https://mintqa.dev/mcp	Override for self-hosted Mint

Submitting to the MCP registry

This package ships with server.json for the official MCP registry. To publish there after npm publish:

mcp-publisher publish

(See the registry docs for the current CLI; the registry verifies the io.github.<owner>/... name against the linked GitHub repo.)

License

MIT