How do I install Perly Pay?

Perly Pay is a local plugin. Install it using npm package: perly-pay-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Perly Pay safe to use?

Yes. Perly Pay passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Perly Pay need?

Perly Pay requires the following credentials or environment variables: PERLY_PAY_SECRET_KEY, PERLY_PAY_API, PERLY_PAY_WEBHOOK_SECRET. You can find setup instructions on the server detail page.

What AI apps work with Perly Pay?

Perly Pay uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Perly Pay MCP Server

by Volodymyrslipak

Developer ToolsLow Risk10.0MCP RegistryLocal

Free

Server data from the Official MCP Registry

Sell for crypto from your editor: products, payment links, invoices and test payments.

About

Sell for crypto from your editor: products, payment links, invoices and test payments.

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

4 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Your key from Dashboard → Developers: sk_test_… while you build.Required

Environment variable: PERLY_PAY_SECRET_KEY

Optional. Default https://pay.perly.io.Optional

Environment variable: PERLY_PAY_API

Optional whsec_…, the default for verify_webhook_signature.Required

Environment variable: PERLY_PAY_WEBHOOK_SECRET

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-perly-pay-mcp": {
      "env": {
        "PERLY_PAY_API": "your-perly-pay-api-here",
        "PERLY_PAY_SECRET_KEY": "your-perly-pay-secret-key-here",
        "PERLY_PAY_WEBHOOK_SECRET": "your-perly-pay-webhook-secret-here"
      },
      "args": [
        "-y",
        "perly-pay-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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: true is 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_links gives 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.

Reviews

No reviews yet

Be the first to review this server!

4.8

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.

Stars

208

Installs