Skip to main content
Glama

sop-mcp

PyPI Python License

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

Add to Kiro

Install MCP Server

Install on VS Code

Or add manually:

{
  "mcpServers": {
    "sop-mcp": {
      "command": "uvx",
      "args": ["sop-mcp"],
      "env": { "SOP_STORAGE_DIR": "/path/to/your/sops" }
    }
  }
}

Related MCP server: aegis

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

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
5dRelease cycle
18Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ValueArchitectsAI/sop-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server