Build with WorkProcedures

Generate audit-ready SOPs from your own tools: a simple REST API, a native MCP server for Claude and other AI assistants, and Zapier for everything else. One API key, no OAuth dance.

Authentication

Create an API key under Settings → API Keys in your dashboard, with read and/or generate permissions. Send it as a Bearer token:

curl https://www.workprocedures.com/api/v1/me -H "Authorization: Bearer proc_live_your_key"

REST API

Generate an SOP from a plain-language description. Synchronous by default; pass "async": true to get an immediate 202 with the document URL while generation finishes in the background (useful for callers with short timeouts).

curl -X POST https://www.workprocedures.com/api/v1/procedures -H "Authorization: Bearer proc_live_your_key" -H "Content-Type: application/json" -d '{"query": "Daily opening procedure for a small commercial bakery, including oven startup checks and HACCP temperature logging."}'

List and read what you've generated:

GET /api/v1/procedures?page=1&limit=20      # newest first
GET /api/v1/procedures/{id}                # full content
GET /api/v1/usage                          # credits & plan usage
GET /api/v1/me                             # key identity check

Generation consumes one SOP from your plan, credits, or free allowance — the same rules as the app. SOP generation via API requires a paid plan or available credits.

MCP server — use WorkProcedures from your AI assistant

WorkProcedures ships a native Model Context Protocol server, so assistants like Claude can draft, list and read the SOPs in your account mid-conversation — "draft a lockout/tagout SOP for our press brake and save it to WorkProcedures" just works.

Claude Code

claude mcp add workprocedures https://www.workprocedures.com/api/mcp -t http -H "Authorization: Bearer proc_live_your_key"

Cursor / VS Code / any client with custom headers

{
  "mcpServers": {
    "workprocedures": {
      "url": "https://www.workprocedures.com/api/mcp",
      "headers": { "Authorization": "Bearer proc_live_your_key" }
    }
  }
}

Available tools

generate_sop — create a new SOP from a description (consumes a generation)
list_sops — list SOPs, optionally filtered by title keyword
get_sop — fetch one SOP's full markdown
get_usage — check remaining credits and plan usage

Native integrations

Connect apps once under Settings → Integrations in the dashboard, then send any SOP to them from the editor's Send to menu — no code required.

NotionLive

Export SOPs as fully formatted Notion pages — headings, lists and code blocks intact — into any page shared with the WorkProcedures connection.

One-click OAuth

SlackLive

Post SOPs to a channel as a rich card with the title, an excerpt, and an Open SOP button.

Paste an incoming webhook

Microsoft TeamsLive

Share SOPs into channels as Adaptive Cards — no bot install, no admin approval cycle.

Paste a workflow webhook

SoonConfluence & Google Drive — export to a Confluence space or as native Google Docs.

Zapier

Connect WorkProcedures to 7,000+ apps without code: trigger a Zap when a new SOP is created (post it to Slack, file it in Drive, log it in Sheets), or generate SOPs from form submissions and project-management events. The Zapier integration is in review for public listing — if you'd like early access, email us and we'll send an invite link.

Start building in minutes

Free account, 3 free SOPs, API keys included on every plan.