Oprocess
Classify business and IT processes and pull APQC, ITIL, and SCOR-aligned KPIs while scoping products or documenting how you operate.
Overview
O-Process is a MCP server for the Build phase that classifies work against 2436 standard processes and 3284 KPIs from APQC, ITIL, and SCOR.
What is this MCP server?
- 2436 classified processes and 3284 KPIs from APQC, ITIL, and SCOR
- AI-native process classification over stdio MCP (PyPI package oprocess)
- Supports scoping, SOP design, and agent workflow naming with standard frameworks
- stdio transport for local Claude Desktop-style or CLI MCP hosts
- 2436 processes in the classification corpus
- Server version 0.4.0 (PyPI oprocess, stdio)
Community signal: 1 GitHub stars.
What problem does it solve?
You scope automation or SaaS workflows without a shared process vocabulary, so specs and agent prompts sound ad hoc to stakeholders.
Who is it for?
Builders documenting B2B workflows, ops playbooks, or agent automations who want APQC/ITIL/SCOR anchors without manual framework PDFs.
Skip if: Hobbyists shipping a single landing page with no process modeling needs, or teams that only want Jira ticket CRUD via MCP.
What do I get? / Deliverables
Your agent returns framework-aligned process IDs and KPI references you can paste into plans, skills, and runbooks.
- Framework-aligned process classifications
- KPI references drawn from 3284 indexed metrics
- Agent-ready process vocabulary for docs and skills
Recommended MCP Servers
Journey fit
Process and KPI lookup first helps builders name workflows and metrics while planning features; the same taxonomy stays useful when you refine operations later. PM subphase is the canonical shelf for structured process libraries that inform specs, runbooks, and agent automation design.
How it compares
Process taxonomy and KPI reference MCP, not a project-management task runner or generic brainstorming skill.
Common Questions / FAQ
Who is O-Process for?
Solo and small-team builders who write specs, SOPs, or agent workflows and need standard process and KPI language from APQC, ITIL, and SCOR.
When should I use O-Process?
Use it while scoping a product, drafting PM artifacts, or iterating operations whenever you need classified processes or KPI definitions instead of inventing names.
How do I add O-Process to my agent?
Install the oprocess package from PyPI (v0.4.0), configure stdio MCP in your client pointing at that server, then query classification tools locally without a separate API key in the published manifest.