Home · Setup · Claude Code

MCP Purchase Requisition in Claude Code

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.

`claude mcp add purchase-requisition` at user scope is the level that matches the data: one store per machine holds the standing requisitions and every run of them, and a run copies its steps and version when it starts, so editing the requisition never rewrites history. There is no network call in the server, so it works identically offline.

What you get in Claude Code

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.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

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. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user purchase-requisition -- node /absolute/path/to/mcp-servers/servers/purchase-requisition/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

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-requisition

That 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:

claude mcp add purchase-requisition -- npx -y @theluckystrike/mcp-purchase-requisition

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

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.

No install: the hosted endpoint

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.

claude mcp add --transport http purchase-requisition https://mcp.zovo.one/mcp/purchase-requisition \
  --header "Authorization: Bearer <token>"

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

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.

Questions

Which scope should I use for MCP Purchase Requisition?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Purchase Requisition without installing anything?

Yes: claude mcp add --transport http purchase-requisition https://mcp.zovo.one/mcp/purchase-requisition --header "Authorization: Bearer <token>". Mint a free token at https://mcp.zovo.one/mcp/token or use a Pro key. -t and -H are the short forms.

MCP Purchase Requisition in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro