Home · Setup · Cursor

MCP Purchase Requisition in Cursor

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.

run_report and the list tools are free, unlimited and write nothing, so leave them enabled permanently and read runs as often as you like. run_check and run_sign_off are the deliberate ones: a required step failed blocks sign-off, and na counts as answered, never as passed.

What you get in Cursor

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 Cursor

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

Scope	Path
This project only	`<project>/.cursor/mcp.json`
Every project	`~/.cursor/mcp.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. Cursor reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "purchase-requisition": {
      "type": "stdio",
      "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-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:

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

The Customize page shows the server and its tools once it has started.

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.

{
  "mcpServers": {
    "purchase-requisition": {
      "url": "https://mcp.zovo.one/mcp/purchase-requisition",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

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

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Purchase Requisition pasting the config block above is the supported route.

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