What we learned shipping 83 MCP tools, and why v2 has 30

Qase rebuilt its MCP server from an API-mirroring v1 with 83 tools to a task-oriented v2 with 30 tools, aiming to reduce AI context usage and mistaken tool selections while retaining access to the same underlying platform. The new design combines create and update actions into entity-specific upsert tools, keeps 13 frequently used tools loaded by default, and makes 17 less common or potentially destructive tools discoverable on demand, though API token permissions remain the actual access-control mechanism. V2 also adds a cached project-context call for faster orientation, composite tools for workflows such as CI reporting, regression runs, and defect triage, QQL-based cross-resource search with syntax help, and a direct REST API fallback for unsupported endpoints. Qase does not claim benchmarked performance improvements, but suggests users assess whether assistants need fewer corrections to complete tasks, while noting that v1 prompts and scripts require migration because tool names and response formats have changed.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.