sparq:testrail-api

Access TestRail REST API v2 endpoints via curl when MCP is unavailable.

27|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-testrail-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq:testrail-api
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-testrail-api
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-testrail-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Direct TestRail REST API v2 reference for HTTP calls via curl/Bash. Use when TestRail MCP server is unavailable, broken, or returning errors and direct API interaction is needed. Covers all endpoint groups (projects, suites, sections, cases, tests, runs, results, plans, milestones, users, priorities, statuses, case types/fields, configs, attachments) with curl examples. Project ID: from outputs.tms.testrail.projectId in sparq.config.json (env: TESTRAIL_PROJECT_ID). Triggered by: MCP broken, use TestRail API directly, curl TestRail, bypass MCP, or when mcp__testrail__ tools fail and TestRail operations are needed.

Core Features & Use Cases

  • Comprehensive curl/Bash references for all TestRail entities (projects, suites, sections, cases, tests, runs, results, plans, milestones, users, priorities, statuses, case types/fields, configs, attachments) with practical examples.
  • Operational guidance on resolving project context from sparq.config.json and environment variables, plus error-handling notes and web fallback guidance.
  • Real-world usage scenarios showing how to compose requests and interpret responses in automated test pipelines.

Quick Start

Run the Quick Start guide to access the API references and begin calling TestRail endpoints directly.

Frequently Asked Questions about sparq:testrail-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I call the TestRail API directly with curl when the MCP server is unavailable?

Call the TestRail API directly with curl to bypass the MCP server when it fails, using provided curl examples for all endpoint groups including projects, suites, cases, runs, and results.

What TestRail API endpoints can I access via curl for QA automation?

Access TestRail REST API v2 endpoints for projects, suites, sections, cases, tests, runs, results, plans, milestones, users, priorities, statuses, case fields, configs, and attachments using curl.

How do I resolve the TestRail project ID for curl API requests?

Resolve the TestRail project ID from the outputs.tms.testrail.projectId field in sparq.config.json or by using the TESTRAIL_PROJECT_ID environment variable for curl requests.

When should I bypass the TestRail MCP server and use curl instead?

Bypass the TestRail MCP server and use curl when mcp__testrail__ tools fail, return errors, or are unavailable and direct API interaction is needed for TestRail operations.

Does this approach support adding test results and attachments to TestRail runs?

Yes, curl references cover adding test results and attachments to TestRail runs, along with practical examples for composing requests and interpreting responses in automated test pipelines.

What should I do if a curl request to the TestRail API returns an error?

Handle TestRail API curl errors by following the error-handling notes and web fallback guidance provided in the reference files to diagnose and resolve endpoint failures.