Capabilities (--caps)

Tools are grouped into capabilities. The core group is always available; others are enabled by passing a comma-separated list to --caps (or TESTRELIC_MCP_CAPS).

Capability	What you get
core	Projects, recent runs, resolved config, health, integration status.
coverage	User journeys, test map, coverage gaps, coverage report, cached payloads.
creation	Plan → generate tests, templates, dry-run, assertion helpers.
healing	Patch proposals, locator suggestions, replay plans for failures.
impact	Diff analysis, risk score, MUST/SHOULD/OPTIONAL test selection.
triage	Diagnose runs, flaky audit, compare runs, RCA, Jira create/dedupe, dismiss flaky, search failures.
signals	User impact, production logs (Loki), affected sessions.
devtools	Project trends, alerts, semantic code search, repo indexing, cache stats.

Suggested bundles

• Day-to-day authoring: core,coverage,creation,healing,impact
• On-call / failures: add triage,signals
• Repo-wide exploration: add devtools

Example:

--caps core,coverage,creation,healing,impact,triage

Enable only what you need so your assistant sees a smaller tool schema.

Next steps

→ Tools reference · Testing workflow