ClawPay
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ClawPay Buy me a blue t-shirt on automationexercise.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ClawPay
AI Shopping Agent — connects your AI to Lithic virtual cards, Stripe, and PayPal.
Production mode by default. Real transactions, real money. Set LITHIC_ENVIRONMENT=sandbox for testing.
⚖️ Legal Notice
ClawPay is a SOFTWARE CONNECTOR ONLY. We do NOT:
Handle, hold, or transmit your funds
Act as a money transmitter or payment processor
Have access to your money at any time
Money flows directly: YOU ↔ Lithic / Stripe / PayPal. ClawPay only connects APIs and automates browser forms.
You are responsible for compliance with payment provider terms and applicable laws. See DISCLAIMER.md for full legal terms.
Related MCP server: Shatale MCP Server
Quick Start
npm install -g @xodn348/clawpay
npx playwright install chromium
export LITHIC_API_KEY=your_production_key
clawpay installThen ask your AI: "Buy me a blue t-shirt on automationexercise.com"
How It Works
Tell your AI what to buy and where
ClawPay navigates the store and shows you a summary
You confirm — no auto-purchase ever
A Lithic single-use virtual card is created and used for checkout
Card self-destructs. PAN/CVV never touch disk or logs.
MCP Tools
Tool | Description |
| Configure Lithic virtual card API |
| AI shopping with single-use virtual card |
| Configure Stripe payment method |
| Charge via Stripe |
| Stripe account balance |
| Recent Stripe payments |
| Issue Stripe refund |
| Configure PayPal |
| Send money via PayPal |
Environment Variables
Variable | Required | Default | Description |
| Yes (shopping) | — | Lithic API key |
| No |
|
|
| Yes (Stripe) | — | Stripe secret key |
| Yes (PayPal) | — | PayPal client ID |
| Yes (PayPal) | — | PayPal client secret |
| No |
|
|
Guardrails
Default limits: $100/transaction, $500/day, USD only.
Override in ~/.clawpay/config.json:
{
"guardrails": {
"maxAmountPerTransactionCents": 10000,
"maxDailySpendCents": 50000,
"allowedCurrencies": ["usd"]
}
}Client Setup
Claude Code:
claude mcp add -s user clawpay -e LITHIC_API_KEY=your_key -- clawpayopencode.json / Claude Desktop / Cursor:
{
"mcp": {
"clawpay": {
"type": "local",
"command": ["clawpay"],
"environment": { "LITHIC_API_KEY": "your_key" }
}
}
}Security
PAN/CVV exist in memory only during checkout — never logged, never stored
Stripe card data handled by PCI-compliant Stripe Checkout
All actions logged to
~/.clawpay/audit.log(no sensitive data)Guardrails block excessive spending before it reaches the API
For vulnerabilities: SECURITY.md
License
Apache 2.0 — LICENSE. Full legal terms: DISCLAIMER.md.
Available Tools
9 toolsbrowse_and_buyA
Browse an online store, add items to cart, and complete purchase using a Lithic virtual card. Requires Playwright installed.
Inputs: store_url (required), product_query (required).
get_balanceB
Get Stripe account balance.
Inputs: no named parameters.
list_transactionsC
List recent payment transactions.
Inputs: limit.
payC
Create and confirm a payment in cents.
Inputs: amount (required), currency (required), description (required).
refundB
Refund a payment intent.
Inputs: payment_intent_id (required).
send_paypalB
Send money via PayPal Payouts to an email address or phone number.
Inputs: amount (required), recipientEmail, recipientPhone, currency, +1 more.
setup_lithicA
Set up Lithic virtual card API for AI shopping. Reads LITHIC_API_KEY from environment.
Inputs: no named parameters.
setup_paymentB
Set up Stripe payment method for ClawPay.
Inputs: no named parameters.
setup_paypalA
Link PayPal account using Client ID and Client Secret. Reads credentials from PAYPAL_CLIENT_ID and PAYPAL_CLIENT_SECRET environment variables or config file.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Most tools have distinct purposes (shopping, Stripe payments, PayPal payouts, setup), though 'pay' and 'send_paypal' could be confused without reading descriptions. Overall clear boundaries.
Naming convention is inconsistent: mix of single verbs ('pay', 'refund'), verb_verb ('browse_and_buy'), and verb_noun patterns. No consistent structure.
9 tools cover multiple payment workflows and setup, which is appropriate for the domain. Not overly numerous or sparse.
Covers core actions (pay, refund, send) but missing some operations like PayPal refund, Stripe payment cancellation, or detailed payment retrieval beyond listing.
Maintenance
Related MCP Connectors
Payment infrastructure for AI agents: spending rules, approval flows, single-use virtual cards.
Payment identity intelligence for AI agents.
Stripe payments for AI agents. Create links, verify, manage customers.
Prepaid virtual cards for AI agents: one-time cards, spend caps, human approvals.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically purchase physical and virtual goods from platforms like Amazon and Shopify using stablecoins, without the need for virtual debit cards or browser automation.1ISC

Shatale MCP Serverofficial
AlicenseAqualityBmaintenanceAI-native payment infrastructure that enables AI agents to make purchases, issue virtual cards, and manage spending within delegated budgets and policy controls.71,355 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to make payments by securely storing encrypted card details and enforcing user-defined policies, allowing agents to fill checkout forms on any site.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, price, and purchase SaaS products, developer tools, and MCP servers with live Stripe checkout, affiliate program, and AgentTrust verification.MIT