Purchase requisitions you build once and run per order, with a signed record of each run. You hold a requisition as a named, versioned list of steps, optionally grouped into sections, each required or optional, and run it against an order as many times as you like. A run copies its requisition's steps when it starts and records the version, so editing the requisition afterwards never changes a run already under way. run_check marks steps pass, fail or na with who and when (na counts as answered, never as passed; a required step failed blocks sign-off), run_report gives the whole run with failures in full, and run_sign_off puts a name and a date on it and freezes it. RUN-YYYY-NNNN ids are sequential and never reissued.
Fourteen tools against Cascade's ceiling of 100, and it pairs naturally with mcp-goods-receipt, which receives what the checked delivery actually brings, and mcp-change-order, which records what changed before it; budget the pair at roughly 23 tools when you decide what else fits alongside them.
| You say | Tool |
|---|---|
| Make a pre-delivery vehicle check requisition: tyres, lights, load secured. | purchase-requisition_create then purchase-requisition_item_add |
| Start a run of it for van BX21 KLM against PO-0031. | run_start |
| The weight step failed at 3620 against a plated 3500. Can it be signed off? | run_check then run_sign_off |
The unit suite is 15 tests, 15 passing, 0 failing (node --test, node v22), covering the snapshot rule, the na-is-not-pass rule and the sign-off freeze; adversarial, concurrency, paths and contract suites sit alongside it.
The file is mcp_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS, Windows and Linux | ~/.codeium/windsurf/mcp_config.json |
If you also run Claude Desktop, the shortest path there is one click: purchase-requisition.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
Windsurf reads its own config, so here it is:
The config block:
{
"mcpServers": {
"purchase-requisition": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/purchase-requisition/dist/index.js"]
}
}
}The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/purchase-requisitionThat writes servers/purchase-requisition/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
{
"mcpServers": {
"purchase-requisition": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-purchase-requisition"]
}
}
}Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/purchase-requisition over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"purchase-requisition": {
"url": "https://mcp.zovo.one/mcp/purchase-requisition",
"headers": { "Authorization": "Bearer <token>" }
}
}
}Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.
Free: Three requisitions, and unlimited runs of them on every tier, because capping the running of a requisition would cap the only thing a requisition is for. Deleting a requisition frees its slot and every run stays readable. Pro is $19 once, verified offline.
~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.
That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.
Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Purchase Requisition contributes 14 tools, so keep the enabled list short rather than counting servers.
MCP Purchase Requisition in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs · Buy Pro