Labsco
MCP SERVER · OFFICIAL PROJECT

Link CLI MCP Server

by Stripe ↗

Online purchases by your AI agent from your Link wallet: it requests a specific purchase, you approve it, and it gets a one-time card for checkout.

Payments, Billing & Subscriptions✓ Popular vendor Official
Needed to connect
An account, signed in with OAuth
Setup effort
One command plus a key
Source
Popular vendor Official

Let an agent buy things, with you approving every purchase.

Your agent can take an online purchase from request to checkout, and, in the US, answer questions about your spending from the accounts you choose to share.

What it is

Stripe's Link CLI, which can also run as a local MCP server, connects an agent to a consumer's Link wallet. The agent does not store your real card details. It creates a spend request for a specific purchase; after you approve it, Link returns a payment credential that works once. It can also read financial data from accounts you choose to share.

What you get

  • Spend requests created with the merchant, line items and amounts
  • Your approval asked for by push notification, which you can give in the Link app
  • A one-time-use card number for the approved purchase, to enter at checkout
  • Your Link account details, saved shipping addresses and spending limits
  • Transactions, balances and account details from accounts you share, for financial insights

Requirements

A Link account. Agent payments are open to consumers in the US and Canada; financial insights to the US only, and they also need a Stripe account registered for Financial Connections. You log in once with link-cli auth login: it shows a web address and a short phrase to confirm in your Link account. The connection uses a sign-in token for your Link account, not a Stripe API key.

Setup effort

One command plus a key — npx @stripe/link-cli --mcp, then supply credentials