Start or advance a Standard Operating Procedure step by step. Use list_resources to discover available SOPs, then call this tool with the SOP name.

Each call returns one step. Execute the step, then call again with current_step incremented to advance.

IMPORTANT: You MUST execute ALL actions described in the returned step content. Do NOT just read or summarize the step — perform the actions using your available tools.

When continuing (current_step >= 1), you MUST provide step_output with the concrete output you produced for the completed step.

Publish a new or updated Standard Operating Procedure document.

The content parameter MUST contain the complete SOP markdown string with YAML frontmatter declaring:

• name (required, snake_case, ≥3 underscore segments — the SOP's identity)

• owner (required, non-empty string — team, alias, or email. This is the point of contact surfaced when feedback is submitted or a mismatch is detected during review. Pick a name you want pinged.)

• stage (required, 'preprod' or 'prod' — informational lifecycle label; see the stage argument below for mismatch behaviour)

• version (required, positive integer — advisory revision counter. The tool auto-bumps on each publish (+1), but we ask authors to declare it explicitly so a mismatch between the file on disk and what the author thinks they are updating is visible in the response)

• description (optional — when omitted, the SOP's ## Overview section is used for short summaries)

Version & stage mismatch: the tool never trusts the frontmatter values blindly. The stage argument wins over the frontmatter stage, and the version is computed server-side (max existing + 1). Both values are overwritten in the stored content so the file on disk always reflects what actually happened. If you pass a version or stage that disagrees with the final stored values, the response surfaces the difference under warning so you can decide whether you were editing the right version.

Example call: {"content": "---\nname: my_sop_name\nversion: 1\nowner: my-team\nstage: preprod\n---\n\n# My SOP\n\n## Overview\nOverview text.\n\n### Step 1: First step\nDo the thing."}

Versioning: plain positive integers — 1, 2, 3, 4, … New SOPs start at 1; each subsequent publish increments by one. No semver.

Lint enforcement: every publish runs the same rule engine as the standalone sop-lint CLI. Errors (SOP rules at severity=error) BLOCK the publish — the tool raises and nothing is written. Warnings are returned under the warning field but do not block. Iterate locally with sop-lint <file> before calling publish_sop to avoid MCP round-trip latency.

Submit improvement feedback for a specific SOP.

Feedback is appended as a single JSON line to {sop_name}.feedback.jsonl inside the SOP's folder. Each entry captures the SOP version, a UTC timestamp, and the feedback text — ready for review when the SOP is next revised.

List all available resources with their URIs and descriptions.

Read a resource by its URI.