Mintqa Mcp

io.github.adamguskyPublished by GitHub account adamguskyv0.1.1Updated Oct 24, 2026

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

The publisher's own server: Blawgy

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Mint's MCP server connects an assistant to Mint, an AI-powered QA service that runs your app in a real browser on every pull request.

What you can do
Connect an assistant to the Mint QA service for AI-driven testing of an app in a real browser, triggered on pull requests. The manifest lists no individual tools, so the exact operations are not documented here. It can be reached either as a hosted remote endpoint or as a local npm package run with npx.
When to use it
Consider it when a team uses Mint for automated QA and wants an assistant to work with that testing setup from a chat session, for example around pull request checks.
Requirements
A Mint account and a Mint API key supplied through the MINT_API_KEY environment variable, or OAuth authentication for the remote endpoint. Either the hosted endpoint at mintqa.dev or a local Node.js runtime to run the npm package with npx. The endpoint can be overridden with MINT_MCP_URL.
Before you install
The server requires an API key or OAuth credentials, so treat the key as a secret. It is tied to a QA service that runs your app in a real browser, so code and app data may be sent to Mint's servers. Writing actions are not documented in the manifest.

Installation

In SourceWeft

  1. Open Mintqa Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.adamgusky%2Fmintqa-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mintqa": {
      "type": "http",
      "url": "https://mintqa.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Blawgy integrations

Blawgy

com.blawgyOfficial publisher

Blawgy's remote MCP server lets an agent research keywords, plan, write, update and publish SEO blog posts on connected sites.

Streamable HTTPWeb executableAuth
Productivity & WorkflowCredential requiredNov 1, 2026