sop-mcp
An MCP server that brings process automation to AI agents through Standard Operating Procedures.
LLMs are powerful but unpredictable when executing multi-step processes — they skip steps, summarize instead of act, and lose track of where they are. sop-mcp solves this by delivering procedures one step at a time, forcing the agent to execute each step and provide concrete output before advancing. This turns SOPs into a control mechanism that makes LLM behavior predictable and auditable.
The result: agents that follow processes the way humans do — step by step, with reasoning enforced at each level.
This approach aligns with Agent SOPs — a standardized markdown format for defining AI agent workflows using RFC 2119 requirement levels (MUST, SHOULD, MAY). sop-mcp adds the execution layer: an MCP server that delivers these procedures one step at a time and enforces completion before advancing.
Install
| Kiro | Cursor | VS Code |
|---|---|---|
Or add manually:
{
"mcpServers": {
"sop-mcp": {
"command": "uvx",
"args": ["sop-mcp"],
"env": { "SOP_STORAGE_DIR": "/path/to/your/sops" }
}
}
}
How It Works
Every session starts the same way — discover what's available, then execute.
list_resources() → catalog of sop:// URIs
run_sop(sop_name="sop_creation_guide") → Step 1 + instructions
run_sop(..., current_step=1, step_output="...") → Step 2
run_sop(..., current_step=2, step_output="...") → Step 3
...
run_sop(..., current_step=N, step_output="...") → Completion
Each response tells the agent to execute the step — not just read it.
Bundled SOPs
Four SOPs ship with the server so new users can try run_sop immediately:
| SOP | What it does |
|---|---|
sop_creation_guide |
Step-by-step guide for authoring new SOPs with RFC 2119 requirements |
code_review_process |
Standard code review workflow — prepare, review, address feedback, merge |
employee_onboarding_setup |
IT setup for a new hire — alias, email, hardware selection |
user_onboarding_process |
Provision identity, application access, and welcome package |
Storage default: ~/.sop_mcp (seeded from the bundled SOPs on first run). Override with SOP_STORAGE_DIR.
Tools
| Tool | Purpose |
|---|---|
list_resources |
Discover available SOPs (built in to every MCP client) |
read_resource |
Read an SOP's full content before executing it |
run_sop |
Execute an SOP step by step |
publish_sop |
Create or update an SOP |
submit_sop_feedback |
Record improvement suggestions |
Full parameter reference: docs/mcp-reference.md
Documentation
| Audience | Resource |
|---|---|
| AI tools | llms.txt — auto-discovered server description |
| Users | skills/sop-mcp-usage/ — how to use |
| Operators | skills/sop-mcp-configuration/ — install, configure, hooks |
| Developers | CONTRIBUTING.md — build, test, design decisions |
| Reference | docs/mcp-reference.md — full tool schemas |
Development
uv sync # install dependencies
uv run pytest # run tests
uv run sop-mcp # start server locally
uv run python scripts/generate_docs.py # regenerate docs
License
MIT
Metadata
Release files for sop-mcp 0.12.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sop_mcp-0.12.2.tar.gz | 196.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sop_mcp-0.12.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 269.1 kB
Release files / sop_mcp-0.12.2.tar.gz
| Download URL | sop_mcp-0.12.2.tar.gz |
|---|---|
| Size | 196.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e3d650c319673bd638ded30d013455f71dab96fa08559602c20389a136b58db
|
|
BLAKE2b-256 checksum How to use checksums |
4be1c29d7661ef6813278e10160f67f0d60c8b75464ba0a56804262f68634df3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 13, 2026.
Transparency logRelease files / sop_mcp-0.12.2-py3-none-any.whl
| Download URL | sop_mcp-0.12.2-py3-none-any.whl |
|---|---|
| Size | 72.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa98913d8abf29882a68cf3182c5a44e4971ae56389314ef14857c95df773fbc
|
|
BLAKE2b-256 checksum How to use checksums |
c2bf05b669ff6eeb5e7afcc16fd4d798f269ac727b59444b65220cfe17c46f79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 13, 2026.
Transparency log