Qase is automatable through its API

Qase is automatable today through its REST API. developers.qase.io documents projects, cases, runs, results, defects, plans, milestones, suites, and Qase Query Language search. Every request sends the API token in a Token header over HTTPS. The token has the same rights as the user's role. A missing permission returns 403. Rate limits are per workspace and depend on the plan: the opened table lists 150 requests per minute on Free, 300 on Startup, 600 on Teams or Business, and 1,000 or a custom limit on Enterprise, plus a shorter burst limit. HTTP 429 includes Retry-After. Qase also publishes an official MCP server. The help center and the qase-tms repository, pushed on 2026-10-15, agree that the hosted servers at https://mcp.qase.io/mcp and https://mcp-eu.qase.io/mcp accept OAuth on paid plans and trials, and that Free-plan calls are refused even though sign-in succeeds. Running @qase/mcp-server with QASE_API_TOKEN works on every plan. The server lists 42 tools, including writes and a REST escape hatch. Deletes ask the client to confirm. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API and the MCP server each score 7. The API is the best path because it works on the Free plan without a local MCP process.

Best path today: api · Overall automatability: 7/10