Link CLI
A Stripe command line and MCP server: the agent pays with credentials from a Link wallet only after you approve
- 904 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent receives card credentials and spends real money, even if after approval
- Login requests reading transactions and balances at connected banks by default
- The `serve` command with the `--host` flag exposes the Link session to anyone who reaches the port
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/link-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent receives card credentials and spends real money, even if after approval
- Login requests reading transactions and balances at connected banks by default
- The `serve` command with the `--host` flag exposes the Link session to anyone who reaches the port
This is third-party code. Review the repository files before installing.
What it does
Link CLI gives an agent payment credentials from a Link wallet, and the agent never sees your real card details. Through `spend-request create` the agent files a spend request: merchant, amount, line items and a justification. An approval request arrives in the Link app, and only after it does the CLI hand over the credentials. There are three credential kinds: a virtual card for an ordinary checkout form on any site, a Link Pay Token for supported Stripe pages and a Shared Payment Token for merchants that accept programmatic payments over the MPP protocol. For a card you can write the data to a file with 0600 permissions using `--output-file`, so the number stays out of the chat history. A separate Financial Insights module reads transactions, balances and connected accounts through Financial Connections. The `identity` commands issue signed user data and anonymous attestation tokens. The CLI works as an ordinary utility and as a local MCP server.
Who it is for. Developers of shopping agents and Link account holders in the US and Canada who let an agent pay for one-off and recurring purchases with every spend confirmed.
Good fit when
- A shopping agent places an order in an ordinary web store and needs a one-time virtual card
- A subscription or recurring payment has to be set up so the real card details stay with Link
- A merchant accepts programmatic payments and the agent pays with an SPT token without filling a form
- An assistant answers personal finance questions and reads transactions and balances from connected accounts
- A service needs proof that a request came from an agent with a Link wallet, without revealing personal data
Not a fit when
- The Link account is outside the US and Canada: the service is limited to them for now
- A single purchase exceeds the equivalent of 500 dollars: a request for a larger spend will not pass
- You need fully autonomous payment with no human approval: the scheme is built on confirming every spend, and exceptions come only from an approval policy on the account
- The agent runs in an environment where `link-cli` cannot be installed as a binary in advance
Example request
Buy the book "Working in Public" from Stripe Press for 35 dollars: file a spend request through Link, wait for my approval and payLimitations
The service works only for Link accounts in the US and Canada. A request needs a justification of at least 100 characters, the amount is capped at the equivalent of 500 dollars, the user has 30 minutes to approve and issued credentials stay valid for 48 hours from request creation. Agent integrations and plugins run the installed `link-cli` binary and download nothing at startup, so it must be installed beforehand. The `identity` commands are in beta and excluded from MCP. The `link-cli serve` command listens on 127.0.0.1 only, and with `--host 0.0.0.0` anyone who reaches the port gets access to your Link session.
How to disable. Run `link-cli auth logout` to close the session and remove the package with `npm uninstall -g @stripe/link-cli`. Delete the `link` block from the MCP client config.
FAQ
How do I connect Link CLI to Claude Code or Cursor?
Install the CLI with `npm i -g @stripe/link-cli`, then add the skills through `npx skills add stripe/link-cli`. For MCP put a `link` server with the `link-cli` command and the `--mcp` argument into the config. The repository also ships ready plugins for Claude Code, Cursor and Codex.
Will the agent see my real card number?
No, the agent works with a virtual card that Link issues for a specific request. To keep that card number out of the chat history, fetch it with `spend-request retrieve --include card --output-file <path>`: the output then shows only brand, last four digits and expiry.
What does the user see during a purchase?
The `--request-approval` flag sends a push notification to the Link app with the merchant, amount and justification. Credentials are not issued before the user approves. The agent waits for the answer in polling mode with the `--interval` and `--max-attempts` flags.
Can I limit what the agent reads?
Yes. At login `--no-financial-insights` turns off reading financial data and `--no-agentic-payments` turns off payments. Rights can be widened later with `auth upgrade` without losing the current session.
Where do I check wallet limits?
The `link-cli user-info retrieve` command shows per-transaction, daily and 30-day limits as well as the identity verification status. Amounts there are in minor currency units such as cents.
Discussion
No questions or reviews yet.
Related
CLI toolsStripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data
A CLI with an MCP server and a skill: the agent calls paid APIs while the user approves each HTTP 402 stablecoin payment with Touch ID
Mastercard plugin with a skill and an MCP server: the agent checks the service catalog and integration guides.
A skill that connects an agent to EasyPay: Stripe products and invoices, SBP and T-Bank payout links, crypto and Mercury in natural language
0 Finance CLI (agent-bank)
agent-bank
Command-line banking for agents: balance, client invoices, transfer proposals and receipt matching in one zero utility
SolidInvoice's built-in MCP server: an agent reads invoices, clients and payments and, once allowed, creates new invoices.
README in short
The README starts with the three credential types and a table of contents, then shows installation, login and the first wallet commands. After that come spend requests, financial data, identity proof, limits, environment variables and development.