MCP
Every install serves one MCP endpoint, at /mcp on its address:
https://example.com/mcpSigning in
Section titled “Signing in”- A personal access token, created in the admin console
- OAuth, for clients that support it. The protected-resource metadata is at
/.well-known/oauth-protected-resource/mcp.
What an agent can do
Section titled “What an agent can do”A tool call runs as the person who owns the token, with that person’s role in the product the tool belongs to. It meets the same permission checks and approval steps as the product’s own pages, so a change that needs a second person’s approval still waits for one. Every call is written to the audit log.
The design is recorded in ADR-006.
Sigmatic rule test evidence
Section titled “Sigmatic rule test evidence”sigmatic_test_rule accepts optional ruleId and expectedMatches. To record
positive expected-match evidence for a saved rule version, supply its UUID and
the zero-based sample indices you expect to match, such as [0]. The tested
YAML and data source must match the saved rule. Omitting expectedMatches or
passing [] keeps the test exploratory.
sigmatic_test_rule_historical accepts optional minExpectedMatches, an integer
of at least 1. It still requires ruleId, startDate and endDate; the dates
must be absolute timestamps, with the end after the start. Omitting the
minimum keeps the historical test exploratory.
Both tools return Sigmatic’s native evidence_id when evidence is recorded.
Passing evidence satisfies the normal deploy validation floor for the tested
rule version. The caller still needs the normal permissions, and deployment
still goes through the configured approval gates.