Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Perly Pay
Overview
Description from the maker (original English)
Sell for crypto from your editor: products, payment links, invoices and test payments.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
- You need to fill in: PERLY_PAY_SECRET_KEY, PERLY_PAY_WEBHOOK_SECRET
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
PERLY_PAY_SECRET_KEY,PERLY_PAY_API,PERLY_PAY_WEBHOOK_SECRET
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pay": {
"command": "npx",
"args": [
"-y",
"perly-pay-mcp"
],
"env": {
"PERLY_PAY_SECRET_KEY": "your-value",
"PERLY_PAY_API": "your-value",
"PERLY_PAY_WEBHOOK_SECRET": "your-value"
}
}
}
}Run this in your terminal
claude mcp add pay --env PERLY_PAY_SECRET_KEY=your-value --env PERLY_PAY_API=your-value --env PERLY_PAY_WEBHOOK_SECRET=your-value -- npx -y perly-pay-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pay": {
"command": "npx",
"args": [
"-y",
"perly-pay-mcp"
],
"env": {
"PERLY_PAY_SECRET_KEY": "your-value",
"PERLY_PAY_API": "your-value",
"PERLY_PAY_WEBHOOK_SECRET": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"pay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"perly-pay-mcp"
],
"env": {
"PERLY_PAY_SECRET_KEY": "your-value",
"PERLY_PAY_API": "your-value",
"PERLY_PAY_WEBHOOK_SECRET": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Your key from Dashboard → Developers: sk_test_… while you build.
PERLY_PAY_APIenvOptional. Default https://pay.perly.io.- Optional whsec_…, the default for verify_webhook_signature.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain perly.io (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1749 servers in this category
- Published to the registry more recently than 84% of the other 1749 servers in this category
- Basic checks equal to or better than 100% of the other 1749 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Perly Pay safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: PERLY_PAY_SECRET_KEY, PERLY_PAY_WEBHOOK_SECRET
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 4 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
perly-pay-mcp
Sell your work for crypto from your AI coding assistant. perly-pay-mcp is a local MCP server for Perly Pay: your assistant can create products, prices, payment links and invoices, pay them in test mode, read payments and receipts, and check a buyer's access. Bitcoin, USDC and USDT land straight in your own wallet; Perly Pay never holds them. It costs 2.5¢ a payment, never more than 0.5% of it, and a month of up to 21 payments is free.
It runs on your machine over stdio and talks only to Perly Pay's public API with your key. There is no server of ours in between.
Set up
Get a test key in Perly Pay: Dashboard → Developers → API keys (sk_test_…).
Claude Code
claude mcp add perly-pay --env PERLY_PAY_SECRET_KEY=sk_test_… -- npx -y perly-pay-mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
"mcpServers": { "perly-pay": { "command": "npx", "args": ["-y", "perly-pay-mcp"], "env": { "PERLY_PAY_SECRET_KEY": "sk_test_…" } } } }
Codex: ~/.codex/config.toml
[mcp_servers.perly-pay]
command = "npx" args = ["-y", "perly-pay-mcp"] env = { PERLY_PAY_SECRET_KEY = "sk_test_…" }
Keep the key out of git: a config file in a project is often committed. Node 20 or newer.
| Variable | |
|---|---|
PERLY_PAY_SECRET_KEY | sk_test_… while you build. sk_live_… reads only (see below). |
PERLY_PAY_API | Default https://pay.perly.io. A perly.io host or this machine; plain http only for localhost. |
PERLY_PAY_ALLOW_ANY_API | 1 sends your key to any other https host in PERLY_PAY_API, for a copy you run yourself. |
PERLY_PAY_WEBHOOK_SECRET | Optional whsec_…, the default for verify_webhook_signature. |
Try it
Sell a one-hour consultation for $49 with a payment link, then pay it in test mode and show me the payment.
The assistant calls create_product, create_price, create_payment_link, simulate_payment and list_payments.
Tools
| Area | Tools |
|---|---|
| Products and prices | create_product, list_products, update_product, create_price, list_prices, update_price |
| Payment links | create_payment_link, list_payment_links, update_payment_link |
| Invoices and checkout | create_invoice, list_invoices, retrieve_invoice, cancel_invoice, create_checkout_session, retrieve_checkout_session |
| Customers | create_customer, list_customers, retrieve_customer |
| Subscriptions (renewed by invoice) | create_subscription, list_subscriptions, retrieve_subscription |
| Access and credits | check_entitlement, list_entitlements, consume_entitlement_credits, list_credit_usage |
| Money in, read only | list_payments, retrieve_payment, list_receipts, retrieve_receipt, list_events |
| Refunds | create_refund, list_refunds |
| Webhooks | create_webhook_endpoint, list_webhook_endpoints, delete_webhook_endpoint |
| Test mode | simulate_payment: pays an invoice, or buys from a payment link and pays that |
| On your machine | verify_webhook_signature checks a Perly-Signature; pay_links gives the dashboard pages only you can use: plan, wallet, go live, two-factor, keys |
The tools are generated from Perly Pay's OpenAPI document, so their arguments are the API's own.
What it will not do
- With a live key, it only reads. Every tool that writes is refused: creating invoices, checkout sessions, products, prices, customers, payment links and subscriptions, cancelling, editing, refunds, credit spending, simulated payments and webhook endpoints. It says why, and you do it in the dashboard or in your app's own code. Lists and lookups work as in test. Why: text a buyer typed can reach the assistant, and nothing the server receives proves that you, not the model, approved a live change (
confirm: trueis written by the model; a client's approval prompt and an MCP elicitation answer both come back through the client). So the server never writes with a live key. - Wallets, API keys, billing, live mode and two-factor have no tool at all. You set them in the dashboard;
pay_linksgives the pages. - What cannot be undone (cancelling an invoice, opening a refund, deleting a webhook endpoint) waits for
confirm: true, which the assistant should only send after asking you. - Your secret key is never repeated in an answer or a log.
- Buyers' license keys never reach the assistant: an event that carries one comes back without its
key; they stay in the dashboard. - Text others wrote is marked as data. Customer names, emails, descriptions and metadata can come from buyers, or from anyone who opens a payment link; every API answer ends with a note telling the assistant not to follow them. Still read what a tool is about to change before you approve it.
Docs: https://pay.perly.io/docs/mcp. API reference: https://pay.perly.io/docs/api. MIT licence.