add-link

Integrate Stripe Link CLI as an MCP server into NanoClaw agent containers.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ajensenwaud/nanoclaw-add-link --skill add-link-ajensenwaud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-link
Source: https://github.com/ajensenwaud/nanoclaw-add-link/tree/main
Command: npx skills add https://github.com/ajensenwaud/nanoclaw-add-link --skill add-link-ajensenwaud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stripe Link spend credentials are hard to integrate safely into agent workflows, because you need secure, one-time payment details while keeping the user in control of every transaction.

Core Features & Use Cases

  • Per-transaction approval via the Link mobile app: the agent requests spend credentials and the user approves or denies each purchase from their phone, preventing standing authority.
  • One-time-use payment credentials for merchants: approved spend requests return card or tokenized credentials that are valid for a single merchant + amount.
  • Machine Payments Protocol (HTTP 402 / MPP) support: for MPP-capable merchants, agents can complete checkouts programmatically using shared payment tokens.
  • Test mode for safe rollout: a test flag enables end-to-end verification without moving real money.

Quick Start

Use the add-link skill to wire Link into a NanoClaw agent group, then run link-cli auth login on the host and ask the agent to “Issue me a test-mode card for $1 at example.com” to verify the full approval flow.

Frequently Asked Questions about add-link

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Stripe Link payments into an AI agent workflow?

You can integrate Stripe Link payments by wiring the Link CLI as an MCP server into NanoClaw agent containers, exposing specific tools like spend-request_create, and guiding the user through link-cli auth login for device-flow authentication.

How does per-transaction approval work for agent-driven purchases?

Per-transaction approval requires the agent to request spend credentials, which the user then approves or denies individually via the Link mobile app, preventing any standing payment authority for the agent.

Can AI agents handle HTTP 402 Machine Payments Protocol checkouts?

Yes, agents can complete HTTP 402 Machine Payments Protocol checkouts programmatically using shared payment tokens when transacting with MPP-capable merchants through the exposed mpp_pay tool.

What is needed to configure agent containers for one-time payment credentials?

Configuring one-time credentials requires installing @stripe/link-cli, allowlisting mcp__link-cli__* tools, and mounting the ~/.config/link-cli-nodejs directory with read-write permissions inside the agent container.

Does Stripe Link MCP integration support testing without moving real money?

Yes, the integration supports a test mode flag that enables end-to-end verification of the agent payment flow without moving real money, allowing safe rollout before live deployment.

What are the limitations of using one-time spend credentials for agents?

The limitation of one-time spend credentials is that approved payment details are valid only for a single merchant and amount, requiring fresh user approval via the Link mobile app for every new transaction.