# purchase requisition [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/theluckystrike/mcp-purchase-requisition  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/purchase-requisition

## Description
Reusable purchase-requisitions and dated runs: pass, fail, n/a, and a sign-off.

## Tools
Capabilities this server exposes over MCP:

- **purchase-requisition_create** — Create a reusable purchase-requisition: a name, a category, a description
- **purchase-requisition_item_add** — Add a step: the text, a section heading, and whether it is required
- **purchase-requisition_item_remove** — Remove a step and bump the version. Runs already under way keep it
- **purchase-requisition_show** — One purchase-requisition, grouped by section, with a blank printable copy on request
- **purchase-requisition_list** — Every purchase-requisition with its version, step count and how many runs came from it
- **purchase-requisition_delete** — Delete a purchase-requisition. Its runs stay readable, because each carries its own copy
- **run_start** — Start a dated run against a job. The steps are copied into it at this point
- **run_check** — Mark one step pass, fail or na, with who and when and what was found
- **run_show** — The run: every step with its answer, the counts, the failures, and what blocks sign-off
- **run_list** — Runs newest first, filtered by purchase-requisition, status, reference, or only those with failures
- **run_sign_off** — Sign off with a name and a date, which freezes the run
- **run_status** — Reopen a complete run, or abandon one when the job did not happen
- **run_report** — The run as text on every tier. Pro also writes it to `out_path` as a .txt file
- **run_delete** — Delete a run. A signed-off one is refused
- **license_status** — Which tier this install is on and where the key came from
- **license_activate** — Store a Pro key for this server

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "purchase-requisition": {
    "command": "npx",
    "args": ["-y","@theluckystrike/mcp-purchase-requisition"]
  }
}
```

## Documentation

## What purchase requisition MCP server does

The purchase requisition MCP server stores reusable lists of checks and the dated runs created from them. Each requisition has a name, category, description, version, and ordered steps. Steps may be grouped under section headings and marked as required or optional.

A run applies one requisition to a specific job. It records an answer for each step as pass, fail, or not applicable, along with who checked it, when they checked it, and what they found. The run also exposes counts, failures, unanswered items, and the conditions preventing sign-off. A signed run is frozen, while its report preserves any exceptions when forced sign-off is used.

## How it works

Starting a run copies the requisition’s current steps and version into that run. If the source requisition later gains or loses steps, an active run continues to represent the version that was actually used. Deleting the source requisition does not remove its historical runs, because those runs contain their own copies.

Derived values are calculated when requested rather than saved as independent flags. Not-applicable answers count as answered but do not count as passes. Sign-off is blocked by unanswered required steps, failed required steps, unanswered optional steps, or a run with no steps. A forced sign-off keeps those exceptions visible in the record and report.

## Setup and configuration

You can use the hosted streamable-HTTP endpoint at `https://mcp.zovo.one/mcp/purchase-requisition` with a bearer token. If an MCP client cannot set headers, the token can be included in the endpoint path. The hosted endpoint requires a token for tool calls.

For local use, clone the repository, install dependencies, and build it with `npm install && npm run build`. Configure the client to start `dist/index.js` with Node. The repository vendors its `@theluckystrike/*` dependencies. A Claude Desktop package is also available from the project’s latest release.

The data directory is local by default at `${XDG_DATA_HOME:-~/.local/share}/mcp-servers/purchase-requisition/`. The server does not require an API key or account for local operation and does not make network calls. The package is not published on npm, so an `npx` install command is not currently a working setup path.

## Tools and capabilities

The purchase requisition MCP server provides tools to:

- Create, list, inspect, update by adding or removing steps, and delete requisitions.
- Start runs and record pass, fail, or not-applicable checks with evidence details.
- Show runs, list them with filters, reopen or abandon them, sign them off, and delete them when permitted.
- Produce a text report; Pro can also write that report to a specified `.txt` path.
- Inspect the installed license tier and activate a Pro key.

It also provides a contract resource describing snapshot behavior, item states, run statuses, sign-off rules, and storage, plus a prompt that guides an agent through a complete run.

## Limitations and notes

The free tier allows three stored requisitions, while Pro removes that limit. Both tiers allow unlimited runs and up to 500 steps per requisition. File output through `run_report` requires Pro. Deleting a requisition frees a free-tier slot.

A signed-off run cannot be deleted. Reopening a completed run or abandoning a job changes its status, while signed records retain the information needed to review what was checked. The tool does not treat not-applicable items as successful checks, which matters when interpreting completion counts and reports.

_Full upstream README: https://allmcps.com/mcp/purchase-requisition/readme_