Add Agent QA MCP server - #45
Open
pranshuchittora wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add Agent QA as a structured local stdio MCP server.
The definition pins the published
agent-qa@0.1.21package, starts its documentedmcpsubcommand with NPX, records the Node.js 24 prerequisite, and labels the licenseFSL-1.1-ALv2. It leaves both maintainer-controlled quality flags false.Validation
npm testpasses all 20 testsnpm run validatereports all server definitions validnpm run buildprocesses Agent QA and builds 38 serversnpx -y agent-qa@0.1.21 mcpstarts and remains available for stdio client messagesgit diff --checkpassesDisclosure: I am affiliated with Agent QA. Agent QA uses the source-available FSL-1.1-ALv2 license, not an OSI-approved open-source license; each release converts to Apache-2.0 after two years. The CLI has no software fee for permitted use, while configured model, browser, or device-provider usage may cost money.