v0.5.0

Final release of the standalone qasphere-mcp package.

This package is now archival. QA Sphere serves an MCP server directly, which tracks the API as it changes and needs nothing installed locally. To switch, go to Settings ⚙️ → MCP Server in QA Sphere. The standalone server now points you there on startup.

Breaking

• API authentication uses the Authorization: Bearer <key> scheme. Requires a QA Sphere backend that accepts bearer tokens. (#28)

Changed

• Listing endpoints moved to offset + limit pagination, and the pagination ceiling was raised to 5000. (#28)
• The server now surfaces the hosted-MCP migration notice on three surfaces: the MCP instructions field, the first successful tool result of each process, and a one-line startup banner on stderr. Set QASPHERE_MCP_HIDE_MIGRATION_NOTICE=1 to silence all three. (#30)

Fixed

• The server reported the wrong version in the MCP initialize handshake. It read npm_package_version, which under npx qasphere-mcp is the consuming project's version and is unset on a direct launch (falling back to 0.0.0). It now reads its own package.json. (#31)
• Cleared all 8 open Dependabot alerts by bumping @modelcontextprotocol/sdk to ^1.30.0; every alert was transitive through the SDK. npm audit reports 0 vulnerabilities. (#29)

Testing

• Added an end-to-end suite covering all 15 tools against a live tenant. (#24, #30, #31)

Full changelog: v0.4.1...v0.5.0