stripe / link-cli

The package is a single skill, create-payment-credential, wrapping Stripe's link-cli npm package: authenticate once with link-cli auth login, then let an agent list saved payment methods and shipping addresses, create a spend request against a merchant, push an approval notification to the user's phone, and read back either a one-time virtual card or a Shared Payment Token once it is approved. The same commands are also reachable as MCP tools — link-cli --mcp for a local server, link-cli serve for an HTTP one — so an agent that can't spawn a subprocess still gets the full command set, and an optional report command sends Stripe a success/blocked/abandoned outcome tag after each attempt.

This is for an agent that needs to actually spend money on a live checkout page on the user's behalf, not for testing card acceptance in your own app, and not for anyone without an existing Stripe Link account. It only covers US Link accounts today, spend requests cap at $5,000 each against a $5,000 daily and $20,000 rolling-60-day ceiling, and every purchase needs a human to approve a push notification within ten minutes — nothing here runs unattended.

READ THE FULL ANALYSIS＋

What "one skill" really means here. The whole package is one skill file describing one CLI, and everything folds into that single command surface — authentication, payment methods, spend requests, the Machine Payments Protocol path, and outcome reporting. If you came expecting a library of separate skills the way most packages on this hub are, there is exactly one entry point, not a toolkit of them.

Checked 19 September 2026 against stripe/link-cli's own README; the payment limits and account requirements above are Stripe's stated numbers, not independently tested.