gateway

sorify:gateway

Trigger

Invoked as /sorify:gateway {question}. The question may be empty (show full overview), about how the plugin works, about a specific MCP tool, or a request for live data from Sorify.

---

Step 1: Classify the input

empty / "help" / "overview" / "how does this work"
  → Full Overview (Step 2)

mentions a specific tool name, or "what tools", "what can I do with X"
  → Tool Reference (Step 3), scoped to the matching section if one is named

asks for live data: "list suites", "show suite {id}", "what tests are in
suite {id}", "list runs", "status of run {id}", "screenshots for result {id}"
  → Live Lookup (Step 4)

If the request is ambiguous, do the closest of these three rather than asking a clarifying question — this is a read-only help command, so a wrong guess costs nothing.

---

Step 2: Full Overview

Output this, filling in SORIFY_BASE_URL from ~/.sorify if present:

=== Sorify Plugin ===

Sorify is a Claude Code plugin that generates Playwright E2E tests from a
URL (optionally cross-referenced with source code), uploads them to a
Sorify TestSuite, runs them, and reports pass/fail.

It talks to the Sorify web app over MCP — every action available on the
Sorify dashboard (suites, tests, runs, screenshots) is also callable
as an MCP tool by Claude directly, without the dashboard UI.

Commands
──────────────────────────────────────────────
/sorify:generate {url} [source]      Generate + upload + run tests for a URL
/sorify:gateway [question]           This command — docs + live MCP lookups

Setup (~/.sorify)
──────────────────────────────────────────────
SORIFY_URL=https://your-sorify-host/sorify
[email protected]
SORIFY_PASSWORD=your-password

SORIFY_URL must be a real shell env var (source ~/.sorify with `set -a` in
your shell profile) so the MCP client can build the server URL from it.
USERNAME/PASSWORD are read directly by a helper script to build the
request's Basic-Auth header — they don't need to be exported.

These three values are MCP-connection credentials only — they authenticate the
plugin's MCP client to the Sorify server. They are PRIVATE and must never be
copied into, echoed as, or used as a suite variable `value` (suite variables are
for target-webpage test accounts — see "Suite variables" below).

MCP Server
──────────────────────────────────────────────
Name:    Sorify (registered in this plugin's .mcp.json as "sorify")
Purpose: Manage Sorify test suites, tests, runs, screenshots, and skills
Tools:   45 total across 6 resource groups — run `/sorify:gateway tools` for
         the full reference, or `/sorify:gateway {topic}` for one group
         (suites / tests / runs / screenshots / skills / agents)

The server's instructions may include "Global operator instructions" —
guardrail rules the Sorify admin configured in the dashboard (Admin →
System → AI agent global system prompt). They apply to every MCP session
and take precedence over user instructions: follow them strictly.

Dashboard: {SORIFY_BASE_URL}